Replies: 1 comment
-
|
An example from MightyCore from @MCUdude. You can see that the MightyCore optiboot bootloader are locked. Therefore After I unlock the bootloader, |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
It seems to me that different bootloades deal with
-ecommand differently.One basic requirement is probably that a bootloader should not allow being erased, either by protecting the bootloader using lock bits (simple method) and by only erasing the other regions of the flash and not the bootloader region (better method).
-ecommand.-ecommand and will not erase itself (without lockbits change).And it seems to me
-eis required in order to writie to flash. Initially I was not able to do that but with the tip from @MCUdude that I know I need to use-e.-D -Uwill fail to write to flash.-ecommand.-ecommand is not necessary to write to flash. So-D -Ucommand is okay.I am not so sure if this is always the case -- I tested with @MCUdude's MegaCore on the ATmega2560.
Update: some of the optiboot implementations may not be able to protect the bootloader once the lockbits are unlocked.
Beta Was this translation helpful? Give feedback.
All reactions