ty140 at hotmail.com
Thu Nov 29 20:02:54 EST 2007
I have little experience with MESS and its utilities, hence my need to fill a (perceived) void with hardware. Although what I'm describing could be used for debugging ROM paks / software, it can also be used to debug hardware.
I envision a unit which holds HALT* low until the user allows a single pulse of appropriate width to allow one clock cycle to be executed on the 6809. Address and data buses would be latched to show you what was seen last by the 6809 before it is HALTed again immediately.
As you stated, I fully agree that the MESS debugger would be much more appropriate for debugging software -- I hope nobody is burning their software to an EEPROM and trying to debug it on a CoCo. :)
> Date: Fri, 30 Nov 2007 09:56:45 +1100> From: msmcdoug at iinet.net.au> To: coco at maltedmedia.com> Subject: Re: [Coco] Hello!> > Ty S wrote:> > > I'm new to this mailing list and wanted to send a proper "hello" to> > everyone here. > > Welcome!> > > I have a few small ideas for my CoCo3, including an EEPROM> > programmer and a single-step hardware debugging unit. Would anyone be> > interested in such things? > > Just wondering whether the hardware debugging unit hasn't been rendered > completely obsolete by software emulation? I've certainly found it much more > convenient and productive to use MESS for my Coco software development, > which of course includes an in-built debugger.> > Regards,> > -- > | Mark McDougall | "Electrical Engineers do it> | <http://members.iinet.net.au/~msmcdoug> | with less resistance!"> > --> Coco mailing list> Coco at maltedmedia.com> http://five.pairlist.net/mailman/listinfo/coco
Share life as it happens with the new Windows Live.Download today it's FREE!
More information about the Coco