In SX Microcontrollers, SX/B Compiler and SX-Key Tool, Chong wrote:

One more note:

Inputs at I/O, DAV, ATN defined pins are from another SX28 that I've programmed to blast out signal according to a scheme which simulates a signal train I intend to monitor at just under 1Mb/s. I'm pretty sure that this is working right as I can confirm the output with my datalogger. 

I can confirm that the scanning SX28 is working right with the code I use for bug tracing enabled (commented "in") in the ISR as the outputs for the scanning SX28 are working right. I also get the right numbers outputted on the RB output pins when all of the bug tracing code is commented in because the datalogger catches the right outputs.

Does anyone else use similar tricks to trace bugs in regular running mode? I found that catching trace numbers to be a handy method in conjunction with a data logger. It doesn't affect timing too much and you can catch high speed effects like switch bounce or signal issues.

---------- End of Message ----------


You can view the post on-line at:
http://forums.parallax.com/forums/default.aspx?f=7&p=1&m=108128#m108132

Need assistance? Send an email to the Forum Administrator at forumadmin@parallax.com

The Parallax Forums are powered by dotNetBB Forums, copyright 2002-2006 (http://www.dotNetBB.com)