Jump to content


Debugging with a skunkboard

2 replies to this topic

#1 swapd0 OFFLINE  



  • 324 posts

Posted Wed May 9, 2018 6:19 AM

Why when I call skunkCONSOLEWRITE some times I don't get the string on the PC?


I've tried to put a skunkNOP at the beginning of the code, and also before and after the skunkCONSOLEWRITE but I still have some missing strings.


By the way I'm using vbcc with jaglib. 


Boot version 02.00.05, Serial 2043


Maybe I need to update the skunkboard bios.

Edited by swapd0, Wed May 9, 2018 6:36 AM.

#2 Tursi OFFLINE  



  • 5,353 posts
  • HarmlessLion
  • Location:BUR

Posted Tue May 15, 2018 1:08 AM

The BIOS isn't involved in the Skunklib functions - all the involved code lives in JCP and Skunklib.s

In general all it does is operate using the same two buffers that are used for file transfers. I never hit it very hard but I never had any problems with lost data - if you write too quickly it's supposed to block, but we've seen bugs in that code before.

#3 LinkoVitch OFFLINE  


    River Patroller

  • 2,580 posts
  • Location:Manchester UK

Posted Wed May 16, 2018 2:14 AM

At the start of my debug code library I use I have an init function that just does:

bsr             skunkRESET
bsr             skunkNOP
bsr             skunkNOP

Before attempting to do any console writes, has always (IIRC) been reliable for me.


need to remember to enable console on jcp or you end up with a Jag sat waiting for the console :D



0 user(s) are browsing this forum

0 members, 0 guests, 0 anonymous users