MCUBOOT FLASH overflow on nrf52840 dongle

[nik_mitros]

Hello everyone,

i encounter a problem on building my application that uses BLE and a I2C ssensor. If I build only the application without a Bootloader there is no problem. But when i added the MCUBOOT bootloader the build crush due to FLASH overflow. The ERROR I get:

Here is my prj.conf file:

#CONFIG_SECURE_BOOT=y
CONFIG_BOOTLOADER_MCUBOOT=y
CONFIG_GPIO=y
CONFIG_SERIAL=n
CONFIG_NRFX_TWIM=y
CONFIG_NRFX_TWIM0=y
CONFIG_NRFX_TWIM1=y
#CONFIG_NRFX_SPIM=y
#CONFIG_NRFX_SPIM1=y
CONFIG_UART_CONSOLE=n
CONFIG_STDOUT_CONSOLE=y
CONFIG_PRINTK=y
CONFIG_USE_SEGGER_RTT=y
CONFIG_RTT_CONSOLE=y
CONFIG_NEWLIB_LIBC_FLOAT_PRINTF=y
CONFIG_NEWLIB_LIBC=y
CONFIG_SYS_CLOCK_TICKS_PER_SEC=1000
CONFIG_TIMING_FUNCTIONS=y
CONFIG_SYS_POWER_MANAGEMENT=y
CONFIG_LOG=n
CONFIG_MCUBOOT_UTIL_LOG_LEVEL_WRN=n

CONFIG_BT=y
CONFIG_BT_DEBUG_LOG=y
CONFIG_BT_MAX_CONN=4
CONFIG_BT_MAX_PAIRED=4
CONFIG_BT_SMP=y
CONFIG_BT_L2CAP_TX_BUF_COUNT=5
CONFIG_BT_PERIPHERAL=y
CONFIG_BT_DEVICE_NAME="Smart_Wristband"
CONFIG_BT_DEVICE_APPEARANCE=833
CONFIG_BT_CONN_TX_MAX=12
CONFIG_BT_LL_SOFTDEVICE_DEFAULT=y
CONFIG_HEAP_MEM_POOL_SIZE=2048
CONFIG_SYSTEM_WORKQUEUE_STACK_SIZE=2048
CONFIG_NRFX_TIMER1=y
CONFIG_BT_USER_DATA_LEN_UPDATE=y
CONFIG_BT_CTLR_TX_BUFFER_SIZE=251
CONFIG_BT_CTLR_DATA_LENGTH_MAX=251
CONFIG_BT_L2CAP_TX_MTU=247
CONFIG_BT_L2CAP_RX_MTU=247

[Håkon Alseth]

Hi,

 

i encounter a problem on building my application that uses BLE and a I2C ssensor. If I build only the application without a Bootloader there is no problem. But when i added the MCUBOOT bootloader the build crush due to FLASH overflow. The ERROR I get:

You are running out of space. Is there any functionality that you don't need? For instance using newlib and printing floats?

CONFIG_NEWLIB_LIBC_FLOAT_PRINTF=y
CONFIG_NEWLIB_LIBC=y

 

Kind regards,

Håkon

[nik_mitros]

Hello Hakon,

I dont think thats the problrem. I just tried to run the simplest blinky example with MCUBOOT and the same error appeared. The only thing I added to the prj.conf is CONFIG_BOOTLOADER_MCUBOOT=y.

I am guessing is some problem that has to do with the devicetree and the flash mapping of the nrf52840 donlge? Because when I run my application with MCUBOOT on nrf52840 DK everything works fine.

Have you tried to run the blinky example with MCUBOOT on nrf52840 dongle?

Regards,

Nikos.

[Håkon Alseth]

Hi Nikos,

 

Sorry for missing the board detail. By default, it uses the nRF5 bootloader, so mcuboot would be the second stage bootloader at this point, which isn't a great starting point:

https://devzone.nordicsemi.com/f/nordic-q-a/77252/nrf52840dongle_nrf52840-config_bootloader_mcuboot-y-partition-to-small

 

Kind regards,

Håkon