| ??? 04/16/08 17:04 Read: times |
#153524 - Sounds like ... Responding to: ???'s previous message |
... a watchdog problem.
The watchdog timer is on by default, and every bit of code that is executed between program start and WDT disable, increases the chance that the WDT will time out before the disable code is reached. Since, as you say, main() is never reached, you can be pretty sure that the startup code is the culprit. Initialising those arrays will easily take enough time to let the WDT bark. The solution is to modify the startup code, so that WDT disable is the first thing it does. Rob. |
| Topic | Author | Date |
| SDCC XRAM Problem | 01/01/70 00:00 | |
| Sounds like ... | 01/01/70 00:00 | |
| I *think* I have that covered... | 01/01/70 00:00 | |
| it is NOT | 01/01/70 00:00 | |
| Assembly | 01/01/70 00:00 | |
| I'll try anything once | 01/01/70 00:00 | |
| OK, here is a way | 01/01/70 00:00 | |
| ANSI C | 01/01/70 00:00 | |
| SDCC startup | 01/01/70 00:00 | |
| unsigned char _sdcc_external_startup(void) | 01/01/70 00:00 | |
| holy cow | 01/01/70 00:00 | |
| The problem is obvious ... | 01/01/70 00:00 | |
| I'm not that bombastic, but agree in principle wit | 01/01/70 00:00 | |
| When someone is familiar with it as you are ... | 01/01/70 00:00 | |
| show me one from this year | 01/01/70 00:00 | |
| You have taken my comment wrong. | 01/01/70 00:00 | |
| My Guess Is That... | 01/01/70 00:00 | |
not always ... | 01/01/70 00:00 | |
| obscure? | 01/01/70 00:00 |