- Notifications
You must be signed in to change notification settings - Fork 8.1k
Open
Labels
area: FlashbugThe issue is a bug, or the PR is fixing a bugThe issue is a bug, or the PR is fixing a bugplatform: STM32ST Micro STM32ST Micro STM32priority: lowLow impact/importance bugLow impact/importance bug
Description
Describe the bug
The mcu-boot partition has a size of 256KB but the following slot0-partition already starts at offset partition@10000 - only 64KB.
Snippet from stm32n6570_dk_common.dtsi
partitions { compatible = "fixed-partitions"; #address-cells = <1>; #size-cells = <1>; /* * Following flash partition is dedicated to the use of bootloader */ boot_partition: partition@0 { label = "mcuboot"; reg = <0x00000000 DT_SIZE_K(256)>; }; slot0_partition: partition@10000 { label = "image-0"; reg = <0x10000 DT_SIZE_K(1536)>; }; slot1_partition: partition@210000 { label = "image-1"; reg = <0x210000 DT_SIZE_K(1536)>; }; storage_partition: partition@410000 { label = "storage"; reg = <0x410000 DT_SIZE_K(64)>; }; }; As soon as the bootloader exceeds 64KB in size, after flashing the STM DFU interface comes up instead of running mcu-boot.
Regression
- This is a regression.
Steps to reproduce
No response
Relevant log output
Impact
Functional Limitation – Some features not working as expected, but system usable.
Environment
No response
Additional Context
No response
Metadata
Metadata
Assignees
Labels
area: FlashbugThe issue is a bug, or the PR is fixing a bugThe issue is a bug, or the PR is fixing a bugplatform: STM32ST Micro STM32ST Micro STM32priority: lowLow impact/importance bugLow impact/importance bug