Hello,
can anybody give me a clue how not to rewrite a booloader area with an user application?
Is there any pragma directive to reserve the bootloader area?
Thanks and regards, Meereck
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi Dan,
are you saying the bootloader will never rewrite the area where it resides, even if the user application hex file contains something which would overwrite the bootloader?
Thanks!
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hello,
can anybody give me a clue how not to rewrite a booloader area with an user application?
Is there any pragma directive to reserve the bootloader area?
Thanks and regards, Meereck
Hi,meereck
In 16-bit PIC,
Regardless of the compiler,
GOTO instruction to $ 0000, the jump destination address in the $ 0002 is written.
Special compilation options should not be necessary.
Bootloader Host to replace the jump destination address to the start address of the bootloader.
User program restrictions:
User Program size < (Max Flash size - Bootloader size)
Best regards,
Dan
Hi Dan,
are you saying the bootloader will never rewrite the area where it resides, even if the user application hex file contains something which would overwrite the bootloader?
Thanks!
Hi,meereck
Yes.
If the user program overlaps with the bootloader area,
The host does not perform the writing, it will return an error message.
It must have "piccodes.ini" for its.
Best regards,
Dan