??? 10/28/04 02:51 Read: times |
#79919 - RE: Time = Money Responding to: ???'s previous message |
Kasper,
I've survived many projects without having fancy debugging tools. Whilst it is nice and can save you many hours, it is not a necessity. For many of us 'old timers' debugging consisted of looking at leds flashing! If you got your code wrong, you had to fix the bug and re-enter it via toggle switches on the front panel. Nowadays we've got PCs with simulators and a serial port. If you write in 'C' just putting printf's at critical locations can tell you a lot. The old flashing led is also a favourite - have the led turn or off at critical points in your code. As I've said before - don't put the bugs in your code and you won't need to de-bug them! This means you need to think carefully about the construction of your code, start of with something basic that flashes a led, then add features step by step. When something doesn't work, backtrack and fix it. When you get stuck, try a simulator. You're doing a school project - the intention is for you to demonstrate what you've learned and what you can do with that knowlege. |
Topic | Author | Date |
ADUC842 Debugger | 01/01/70 00:00 | |
RE: ADUC842 Debugger | 01/01/70 00:00 | |
RE: ADUC842 Debugger | 01/01/70 00:00 | |
RE: ADUC842 Debugger | 01/01/70 00:00 | |
RE: ADUC842 Debugger | 01/01/70 00:00 | |
RE: ADUC842 Debugger | 01/01/70 00:00 | |
RE: ADUC842 Debugger | 01/01/70 00:00 | |
RE: ADUC842 Debugger | 01/01/70 00:00 | |
RE: ADUC842 Debugger | 01/01/70 00:00 | |
RE: ADUC842 Debugger | 01/01/70 00:00 | |
RE: ADUC842 Debugger | 01/01/70 00:00 | |
RE: ADUC842 Debugger | 01/01/70 00:00 | |
RE: ADUC842 Debugger | 01/01/70 00:00 | |
RE: ADUC842 Debugger | 01/01/70 00:00 | |
RE: ADUC842 Debugger | 01/01/70 00:00 | |
RE: ADUC842 Debugger | 01/01/70 00:00 | |
Time = Money | 01/01/70 00:00 | |
RE: Time = Money![]() | 01/01/70 00:00 |