boards/arm/samv7: remove unused options on defconfig #17340
+0
−6
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
fdcavalcanti
requested review from
jerpelea and
pkarashchenko
as code owners
github-actions
bot
added
Board: arm
Size: XS
Contributor
Author
|
If someone has this board to validate the changes it would be greatly appreciated. |
Contributor
I have only SAM[L21,R21,W25]. These V70/V71 looks far more expensive and I already bought some rPI boards so probably not going to buy them sorry :-(
I guess if there are no users with the boards, and the build is fixed, that is okay, will ask on the mailing list :-) |
Contributor
|
Hi, I still have one SAMV71-XULT borrowed from Elektroline.cz from GSoC. I suppose I could run some tests with it. |
Contributor
Author
Thank you very much @matiamic! |
pkarashchenko
requested changes
Nov 18, 2025
Contributor
|
@TimJTi told on the mailing list he has some spare boards with SAMv7 and can share for testing, big thank you Tim! I would be grateful to take one board for NXDART, anyone else needs one? :-) |
xiaoxiang781216
previously approved these changes
Nov 19, 2025
Contributor
I have found 1 x SAMV71-XULT and have emailed you 👍 |
Remove the unused Nuttshell and RAMTEST to free up some space on boot partition. Signed-off-by: Filipe Cavalcanti <[email protected]>
fdcavalcanti
force-pushed
the
bugfix/samv7-mcuboot-fix-flash-img
branch
from
39d3955 to
60c9b81
Compare
fdcavalcanti
changed the title
Contributor
Author
|
I have changed the defconfig. |
xiaoxiang781216
approved these changes
Nov 20, 2025
Contributor
|
michallenc
approved these changes
Nov 20, 2025
Contributor
michallenc
left a comment
michallenc
left a comment
There was a problem hiding this comment.
These changes should be ok based on what I use on custom SAMv71 boards.
Contributor
Contributor
|
Hi, I brought the changes from the changed defconfig to samv71-xult's defconfig. Compilation OK, execution gets stuck on But that behavior is the same for the build without the changes. And it makes sense as I am providing no firmware image. I tried to provide a valid image by following the steps in the |
Contributor
|
cederom
approved these changes
Nov 20, 2025
Contributor
cederom
left a comment
cederom
left a comment
There was a problem hiding this comment.
Big Thank You @fdcavalcanti Amazin Work!! :-)
Contributor
Author
|
@pkarashchenko could you please take a look? |
Contributor
|
Okay I just got the SAMv7 board from @TimJTi delivered! |
Contributor
|
Okay first steps working :-) Can flash with OpenOCD over the built-in Atmel debug probe (luckily its generic So far so good :-) Now into this mcuboot stuff :-) https://nuttx.apache.org/docs/latest/platforms/arm/samv7/boards/samv71-xult/index.html#mcuboot-loader |
Contributor
|
Contributor
|
Contributor
Hi, SAMv70 and SAMv71 MCUs should be basically the same (if the number of pins is the same, they ship it in 70, 100 and 144 pin variant if I recall), the difference will likely be just between UART pins routing. And peripherals on Xult vs QMTECH might be connected differently. SAMv7-Xult board has serial console on There are two MCUs on Xult board, one is SAM and other is the older 16 bit PIC from Atmel's series that works as a bootloader and programmer. |
Contributor
|
I will be able to look into this EOW (probably on Friday or Saturday). I'll provide my feedback |
xiaoxiang781216
approved these changes
Nov 27, 2025
Contributor
|
As an alternative to this I was experimenting with So basically update and extend MCUboot loader maximum size from 128K to 144K and reducing scratch area. What do you think? |
Contributor
|
@pkarashchenko it's a possibility, but I think we shouldn't give more space to the bootloader unless really necessary - and there are options we can disable without affecting its functionality. Reducing scratch size means more copying and erasing in that area, thus more flash wear. The current size 128 kB also has an advantage that we can fit the bootloader into first flash's sector. |
Contributor
Ok. Then we can disable some functionality. I tried to compile the current configuration with the current MCUboot hash and see that the result binary is close to 128K (uses 99.6% of allocated flash). Taking into consideration wear leveling is good, but what if the next MCUboot version will add some code and the resulting image will overflow the allocated size for 100bytes more? There are not many things to disable left. And having nsh for bootloader sometimes is useful. At least in my case I was adding some command to display version information or initiating OTA update by a command. SAMe70 512Kb flash variant is not very usable in terms of MCUboot and was here for demo purposes, so we can ever drop that configuration and keep only options with bigger flash. I'm just looking for some solution that is usable and scalable. The bigger flash SAMv7 options still have a sufficient scratch area. |
Contributor
Oh, I expected we would be around 60 kB with these changes and have a lot of reserved space. Ok then, that changes things and I suppose we can reserve more space for the bootloader. |
Contributor
|
I tried to add one more page (16Kb) for bootloader that should put us to the safe stop I hope. |
1 similar comment
Contributor
|
I tried to add one more page (16Kb) for bootloader that should put us to the safe stop I hope. |
jerpelea
approved these changes
Dec 1, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
8 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
Remove the unused Nuttshell and RAMTEST to free up some space on boot partition.
This should fix linker issues reported in nuttx-apps #3200.
Impact
Affects common linker script for
arm/samv7when using MCUBoot.Testing
Before changes:
After changes: