User`s manual

112 digi.com Debugging with Dynamic C
6.5.2.3 Other Things to Try
Get out of your cubicle. It is a well-known fact that there are times when simply walking over to a co-
worker and explaining your problem can result in a solution. Probably because it is a form of data gather-
ing. The more data you gather (up to a point), the more you know, and the more you know, the more your
chances of figuring out the problem increase.
Stay in your cubicle. Log on and get involved in one of the online communities. There is a great Yahoo E-
group dedicated to Rabbit and Dynamic C. Although Rabbit engineers will answer questions there, it is
mostly the members of this group that solve problems for each other. To join this group go to:
http://tech.groups.yahoo.com/group/rabbit-semi/
Another good online source of information and help is the Rabbit bulletin board. Go to:
http://forums.digi.com/support/forum/index
If you are having trouble figuring out what is happening, remember to analyze the bug under various con-
ditions. For example, run the program without the programming cable attached. Change the baud rate.
Change the processor speed. Do bug symptoms change? If they do, you have more clues.
6.6 Reference to Other Debugging Information
There are many good references available. Here are a few of them:
• Debugging Embedded Microprocessor Systems, Stuart Ball
• Writing Solid Code, by Steve Macquire
• Websites: google, search on debugging software
At the time of this writing the following links provided some good information:
• http://www.embeddedstar.com/technicalpapers/content/d/embedded1494.html
• “They Write the Right Stuff” by Charles Fishman
http://www.fastcompany.com/magazine/06/writestuff.html