nrf52840dongle_nrf52840 CONFIG_BOOTLOADER_MCUBOOT=y partition to small

[ChrisRu]

Hi,

when I build the nrf52840dongle_nrf52840 target I r

Memory region         Used Size  Region Size  %age Used
          FLASH:       53236 B        48 KB    108.31%
           SRAM:         29 KB       256 KB     11.33%
       IDT_LIST:          88 B         2 KB      4.30

/opt/gnuarmemb/gcc-arm-none-eabi-9-2019-q4-major/bin/../lib/gcc/arm-none-eabi/9.2.1/../../../../arm-none-eabi/bin/ld:
zephyr/zephyr_prebuilt.elf section `text' will not fit in region `FLASH'

build target nrf52840dk_nrf52840 has no problem.

174/179] Linking C executable zephyr/zephyr_prebuilt.elf
Memory region         Used Size  Region Size  %age Used
          FLASH:       34876 B        48 KB     70.96%
           SRAM:       19392 B       256 KB      7.40%
       IDT_LIST:          88 B         2 KB      4.30%

I tried for the simple blinky application to double check it.

Run my development on  nRF Connect SDK 1.5.1

Any hints?

Chris

[Einar Thorsrud]

Hi,

The error here comes from trying to make the bootloader fit, not the application itself (for instance blinky). The nRF52840 dongle ships with a USB bootloader, so unless you use a external debugger with it it is not straight-forward to test it with MCUBoot (then you would adapt it to use multiple stages, both the nRF5 SDK USB bootloader and then MCUBoot). So in short the 840 dongle is not well suitable for this.

[ChrisRu]

Hi Einar,

Oh what you told me here make sense, and from the MCUBoot "documentation" the MCUBoot should be the 1st stage boot-loader and not queued up after the USB loader.

Thanks
Chris :wq