| ??? 07/07/08 15:34 Read: times |
#156486 - How do you test and debug code? Responding to: ???'s previous message |
How do you test and debug code?
You seriously need to get inside how your hardware and firmware work at the MCU level. Both of the things I suggested are pointers to things about the in direct relation to the 8051 architecture are likely causes of your corruption problem. Do not hide behind your C compiler and avoid digging into the underpinnings to determine what is wrong. If you do not have a robust debugging environment then stop now and get one in place. Michael Karas |
| Topic | Author | Date |
| Data Array getting corrupted after init | 01/01/70 00:00 | |
| OnePossibleIdea.... | 01/01/70 00:00 | |
| I did not do anything with the stack | 01/01/70 00:00 | |
| As Michael said.... | 01/01/70 00:00 | |
| How do you test and debug code? | 01/01/70 00:00 | |
| Keil is the only thing in place | 01/01/70 00:00 | |
| 'crap'?? | 01/01/70 00:00 | |
| Is this the book you refer? | 01/01/70 00:00 | |
| nope | 01/01/70 00:00 | |
| Erik | 01/01/70 00:00 | |
| So where is the code | 01/01/70 00:00 | |
| do NOT "put them" | 01/01/70 00:00 | |
| Focus | 01/01/70 00:00 | |
| Simulator | 01/01/70 00:00 | |
| So this is on a simulator? | 01/01/70 00:00 | |
| Post your duff code | 01/01/70 00:00 | |
| Finding Cause of Corruption | 01/01/70 00:00 | |
| Get the C right, then look at the target CPU | 01/01/70 00:00 | |
| Optimizing Compilers | 01/01/70 00:00 | |
| In my experience..... | 01/01/70 00:00 | |
| Keil C 51 Optimizations | 01/01/70 00:00 | |
| Use IAR then | 01/01/70 00:00 | |
| different approaches | 01/01/70 00:00 | |
| sometimes, depends | 01/01/70 00:00 | |
Thanks | 01/01/70 00:00 |