-
-
Notifications
You must be signed in to change notification settings - Fork 1.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Reserve the correct (smaller) amount of flash for Optiboot on the Arduino Nano. #546
Conversation
Memory usage change @ 78910c4
Click for full report table
Click for full report CSV
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for taking the time to submit a pull request @mjoldfield.
We cannot accept this change because the fuses on the official Nano boards are configured for a 2 kB boot section instead of 0.5 kB.
So the current upload.maximum_size=30720
value is actually correct even though the Optiboot bootloader used on the boards would fit in a 0.5 kB boot section.
Related discussion:
- arduino/Arduino@1cf34c8#commitcomment-27651798
- Nano with Optiboot: maximum sketch size and fuses not updated #10
- wrong size and hfuse for Nano in boards.txt #308
- Arduino Nano wrong Optiboot bootloader size Arduino#7341
- Wrong boards.txt Parameters Arduino#7482
- More free flash area for Nano #26
- Nano with Optiboot has wrong upload.maximum_size Arduino#8310
- Wrong maximum_size for optiBoot Nano #98
Two variants of the Arduino Nano board are supported: one using an old
boot loader; the other the new, smaller, optiboot.
However, the flags which protect memory and the memory reserved for
the boot loader when linking haven't been updated for optiboot. This
PR fixes that.