| ??? 07/01/10 12:29 Read: times |
#177023 - not necessarily a good idea Responding to: ???'s previous message |
In there you will find that I discourage the use of two separate C programs
If you have boot and app as one program, the risk of a unsynch with the bootloader (which, by definition is non-replacable) is waaaay too large. My approach is that the app has a fixed location 'vector page' written in assembler which the bootloader access. This way you can maintain the bootloader as 'untouchable'. bootloader org 3 jb bootbit,bootEI0 ljmp appentry+3 bootEI0: ljmp isrEI0 app org apppage+3 ljmp isrEI0 org appage+6 ljmp isrTI0 Erik |
| Topic | Author | Date |
| IAP / Dual applications and interrupts | 01/01/70 00:00 | |
| Bootloaders Share Interrupts Like This | 01/01/70 00:00 | |
| not necessarily a good idea | 01/01/70 00:00 | |
| Hogworts..... | 01/01/70 00:00 | |
| interesting concept | 01/01/70 00:00 | |
| an added note | 01/01/70 00:00 | |
| Does the bootloader _have_ to use interrupts? | 01/01/70 00:00 | |
| Forwarding of interrupts. | 01/01/70 00:00 | |
| And for reliability... | 01/01/70 00:00 | |
| Special Hardware Features Also Show up | 01/01/70 00:00 | |
| emphasizing another factor | 01/01/70 00:00 | |
| Let me comment on that... | 01/01/70 00:00 | |
Yet another consideration with boot loader. | 01/01/70 00:00 |