| ??? 04/18/08 09:05 Read: times |
#153664 - obscure? Responding to: ???'s previous message |
How is this obscure? It's documented in the manual and mentioned many times on both the SDCC and SiLabs fora (or even here).
You can write the initialization in C as long as you remember that variables are not yet initialized when _sdcc_external_startup() is executed. Usually it only contains (many) writes to SFRs and maybe some loop counter variables. Or if you mean this watchdog issue is obscure, I again say it is documented in the datasheet and mentioned in the fora. You only need to be aware that initialization takes time and in this case more time than the watchdog allows by default. If you were to use any other compiler, all I know of would give you the same issue with a similar solution mentioned in the documentation. Maarten |
| 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 |