[Coco] DW3 WireBug mode

[Boisy Pitre]

I actually got as far as to create a wirebug component in NitrOS-9.

See wbug.asm in the NitrOS-9 repository under level1/modules.

By issuing the calldbg command (level1/cmds/calldbg.asm), one can get a CoCo running NitrOS-9 Level 1into debug mode, whereupon a server could take it over and send commands.

As per the comments in wbug.asm, it works under Level 1, but I never got back to making it work under Level 2, where it would reside as a kernel extension (KrnP3).

I have no time to devote to CoCo stuff right now, so I cannot complete the work, but it would also need a server component. Aaron, I think you could readily code this up in DW4.

On Jul 3, 2013, at 11:26 AM, Robert Hermanek wrote:

> I was reading the DW3 protocol specification, and was interested in the wirebug functions.  In general, coco always initiates transactions, like read/write sector.  It appears the general method of using wirebug is 1) coco sends command to server indicating it is now in wirebug mode, and then sits in wait state 2) server can send multiple commands to coco, which can read/write both registers and memory, 3) when done, the server needs to send a command to coco to end wirebug and resume execution.
> 
> That sounds fine, question is:  I'm an HDBDOS user, how do I place my coco3 in wirebug mode?  Is there an EXEC &H(addr) statement to accomplish this?
> 
> Thanks
> 
> -RobertH
> 
> --
> Coco mailing list
> Coco at maltedmedia.com
> http://five.pairlist.net/mailman/listinfo/coco