| ??? 01/29/06 20:28 Read: times Msg Score: +1 +1 Good Answer/Helpful |
#108658 - Manageing code and debugging Responding to: ???'s previous message |
Stanley Lio said:
I found it is very very difficult to debug a assembler code longer then serval hundreds. How do you debug yours? Divide your code into independent functional modules and structure each as a subroutine. That way you only need to understand a smaller chunk at once. Debug in the same way. Write a simple test framework that will allow you to debug one, two or three related modules at a time. That way you have fewer bugs to find at a time and less places the bugs can be. Once you get groups of modules working you can build a new framework to put larger numbers of already debugged modules together. Lastly you build the framework for the whole application. We used to call this approach 'Phased Integration'. Ian |
| Topic | Author | Date |
| Servomotor head version III | 01/01/70 00:00 | |
| Nice Work | 01/01/70 00:00 | |
| Manageing code and debugging | 01/01/70 00:00 | |
| Divide into modules | 01/01/70 00:00 | |
| multi tasking | 01/01/70 00:00 | |
| IRRC routine are much longer | 01/01/70 00:00 | |
| No waiting for IR | 01/01/70 00:00 | |
| two mcu | 01/01/70 00:00 | |
| Maybe this will help you | 01/01/70 00:00 | |
| this is not IRQ save | 01/01/70 00:00 | |
| RS232 | 01/01/70 00:00 | |
| Design First | 01/01/70 00:00 | |
| Design | 01/01/70 00:00 | |
Pardon | 01/01/70 00:00 | |
| Well done! | 01/01/70 00:00 | |
| The "3.0" | 01/01/70 00:00 | |
| Smart! | 01/01/70 00:00 | |
| hardware | 01/01/70 00:00 | |
| Mainland China | 01/01/70 00:00 | |
| And Well done Kai! | 01/01/70 00:00 | |
| My experinece | 01/01/70 00:00 | |
| very impressive | 01/01/70 00:00 | |
| Program and Code Structure | 01/01/70 00:00 | |
| Spaghetti anyone ? | 01/01/70 00:00 | |
| manually interpret machine code? | 01/01/70 00:00 | |
| hand coded mechine language | 01/01/70 00:00 | |
| Keep up the good work | 01/01/70 00:00 |