??? 12/07/04 14:21 Read: times |
#82700 - I can anticipate all kinds of situations Responding to: ???'s previous message |
I can think of a number of senarios there relocatable code may be just what is needed in a microcontroller system. One example would be a design where the FLASH blocks in a microcontroller are only erasable block by block. Sometimes one block is reserved for an "in application boot loader". There may however be the need to anticipate that the boot loader block needs to be re-programmed itself. If the code is written in a relocatable manner it could move itself to another FLASH block and jump to the moved block so that the original block can be erased and re-programmed.
Michael Karas |
Topic | Author | Date |
sjmp vs ajmp | 01/01/70 00:00 | |
as you said | 01/01/70 00:00 | |
Different jmps | 01/01/70 00:00 | |
re:AJMP, SJMP | 01/01/70 00:00 | |
AJMP is 2 bytes LJMP is 3 | 01/01/70 00:00 | |
LJMP was not the question | 01/01/70 00:00 | |
AJMP vs SJMP | 01/01/70 00:00 | |
Relocable. | 01/01/70 00:00 | |
relocatable | 01/01/70 00:00 | |
Re:Relocatable | 01/01/70 00:00 | |
relocatable - not in a 51 | 01/01/70 00:00 | |
Relocatable Code is Valid | 01/01/70 00:00 | |
Not JMPs, relocatable | 01/01/70 00:00 | |
I can anticipate all kinds of situations | 01/01/70 00:00 | |
If I can devise concepts others will too | 01/01/70 00:00 | |
"driver". | 01/01/70 00:00 | |
Re: driver | 01/01/70 00:00 | |
maybe... maybe not.![]() | 01/01/70 00:00 | |
16M derivatives... | 01/01/70 00:00 | |
SJMP is 2 bytes | 01/01/70 00:00 | |
Maybe he means additional bytes | 01/01/70 00:00 | |
yes. | 01/01/70 00:00 |