??? 12/23/05 17:39 Read: times |
#105836 - more suggestions Responding to: ???'s previous message |
Mahmood has listed the basic things everyone needs to do when working on microcontrollers. We all get to the point sometime when it "doesn't work." Our familiarity with our own work often makes it all the more difficult to see the problems in it. Sometimes you have to ask for help.
I would add to Mahmood's list when asking for such help: 1. What *exactly* doesn't work? 2. What is the code *supposed* to do? 3. What have you done to try to make it work? 4. What debug tools do you have available to you? (emulator, scope, simulator, logic probe, LED, etc.) 5. Show your code, and any errors and warnings your compiler and/or assembler might have given you. Answers to these questions at the start will prevent needless guessing and wasted time speculating on what the real problem might be, and allow more useful suggestions to be made. Dennis |
Topic | Author | Date |
My Code doesn't work question!!! | 01/01/70 00:00 | |
more suggestions | 01/01/70 00:00 | |
debugging | 01/01/70 00:00 | |
give ouputs at various points of code | 01/01/70 00:00 | |
Tell it to the Teddy bear! | 01/01/70 00:00 | |
To work scientifically | 01/01/70 00:00 | |
Genius or hardworker | 01/01/70 00:00 | |
Yes | 01/01/70 00:00 | |
Of course | 01/01/70 00:00 | |
Small steps vs large jumps | 01/01/70 00:00 | |
Eh ? | 01/01/70 00:00 | |
There is! | 01/01/70 00:00 | |
ACO | 01/01/70 00:00 | |
true, and![]() | 01/01/70 00:00 |