| ??? 02/24/11 21:30 Read: times |
#181311 - updater and libraries Responding to: ???'s previous message |
Maarten Brock said:
This is not true! If your updater is part of your application it will share code (libraries) with it. When the application is updated the shared code (and overlayed data) is no longer at the same address and your updater will probably crash. It really is important to create a separate project for your bootloader. It must at least contain the first page at 0x0000, the rest may live in bank2. Your application can use page 1 and up upto 64k.
Maarten I realized that I could not use any library functions, or indeed any of my other functions and interrupt handlers that exist in the main application. So the updater uses absolutely no library calls and interrupts are disabled. The only arithmetic used is for the 1k XDATA-space buffer pointer, and that isn't implemented as a call of any sort. The serial port handler is polled. The main application won't be larger than the 32k common page. -a |
| Topic | Author | Date |
| Odd use of code banking | 01/01/70 00:00 | |
| I don't know about Keil's... | 01/01/70 00:00 | |
| Seperate Program? | 01/01/70 00:00 | |
| separate program | 01/01/70 00:00 | |
| Often special lock bits for boot regions | 01/01/70 00:00 | |
| linker magic | 01/01/70 00:00 | |
| RTFM | 01/01/70 00:00 | |
| You are not good to go | 01/01/70 00:00 | |
| updater and libraries | 01/01/70 00:00 | |
| which is why | 01/01/70 00:00 | |
| Please Reconsider | 01/01/70 00:00 | |
| the golden rule | 01/01/70 00:00 | |
| re: Reconsider | 01/01/70 00:00 | |
If needed... | 01/01/70 00:00 |