stm32: mcuboot: add support for mcuboot tests and samples #93862
Conversation
zephyrbot
added
area: Samples
zephyrbot
requested review from
asm5878,
benothmn-st,
d3zd3z,
de-nordic,
erwango,
etienne-lms,
FRASTM,
gautierg-st,
GeorgeCGV,
HoZHel,
kartben,
marwaiehm-st,
mathieuchopstm,
nashif and
nordicjm
djiatsaf-st
force-pushed
the
support_mcuboot_tests
branch
2 times, most recently
from
959b37f to
9b3a129
Compare
add boot and slots partitions for flash memory in dedicated mcu boards Signed-off-by: Fabrice DJIATSA <[email protected]>
Add STM32 supported boards for the test. Signed-off-by: Fabrice DJIATSA <[email protected]>
Add STM32 supported boards for the test. Signed-off-by: Fabrice DJIATSA <[email protected]>
Add STM32 supported boards for the test. Signed-off-by: Fabrice DJIATSA <[email protected]>
Since the addition of a new storage partition definition in the nucleo_f746zg dts, this node must be deleted before performing this test. Signed-off-by: Fabrice DJIATSA <[email protected]>
djiatsaf-st
force-pushed
the
support_mcuboot_tests
branch
from
9b3a129 to
920d124
Compare
|
| boot_partition: partition@0 { | ||
| label = "mcuboot"; | ||
| reg = <0x00000000 DT_SIZE_K(34)>; | ||
| reg = <0x00000000 DT_SIZE_K(64)>; |
There was a problem hiding this comment.
48KB is the minimum MCUboot partition size, Flash sectors are atmost 4KB on this SoC, so why give more to MCUboot?
Same for other Flash-constrainted SoCs with sub-32KB sector size.
There was a problem hiding this comment.
I just based it on how the nucleo_wba55cg was added, and also compared the sizes of the flash sectors/pages in the refman and adapted with the rest so that it worked on the tests.
If you have some references on the rules to follow, that would be welcome.
| /* Set 4KB of storage at the end of 128KB flash */ | ||
| storage_partition: partition@1f000 { | ||
| label = "storage"; | ||
| reg = <0x0001f000 DT_SIZE_K(4)>; | ||
| }; |
There was a problem hiding this comment.
don't know what the sector size is but for nvs this would need to be at least 3 sectors to be usable
| slot0_partition: partition@10000 { | ||
| label = "image-0"; | ||
| reg = <0x00010000 DT_SIZE_K(32)>; | ||
| }; | ||
|
|
||
| slot1_partition: partition@18000 { | ||
| label = "image-1"; | ||
| reg = <0x00018000 DT_SIZE_K(30)>; | ||
| }; |
| slot0_partition: partition@40000 { | ||
| label = "image-0"; | ||
| reg = <0x00040000 DT_SIZE_K(448)>; | ||
| }; | ||
|
|
||
| slot1_partition: partition@b0000 { | ||
| label = "image-1"; | ||
| reg = <0x000b0000 DT_SIZE_K(320)>; | ||
| }; |
There was a problem hiding this comment.
sizes are very different? If using different sizes then the extra sector should be in slot 1 and swap using offset should be used rather than swap using move
There was a problem hiding this comment.
Thank you for your feedback.
Before addressing the comments, if you could please provide some references on algorithm-based partition distribution or other useful resources, they would be very helpful.
| */ | ||
|
|
||
| /delete-node/ &storage_partition; | ||
| &flash0 { |
This PR adds support for testing MCUboot tests and samples. However, not all series are supported yet due to some limitations and hardware incapacity.
Related tests and samples :