??? 02/24/11 17:48 Read: times |
#181307 - You are not good to go Responding to: ???'s previous message |
Andy Peters said:
I will just send and program only the first bank (0x0000 to 0x7FFF), ignoring the data for the Bank 2 (starting at 0x8000 in my buffer).
This should be fine. The only code in Bank 2 is the firmware updater, and that doesn't need to be changed with the rest of the code. (And if it does, it needs to happen using JTAG.) Now as long as my application fits into the 32k bank 0, I'm good! 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 |
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 |