52840 SDK v17.1 Linker Errors Building DFU Bootloader

RE: 52840 SDK v17.1 Linker Errors Building DFU Bootloader

davidb — Tue, 20 Sep 2022 22:07:39 GMT

Issue is solved now with correct linker settings.

RE: 52840 SDK v17.1 Linker Errors Building DFU Bootloader

Einar Thorsrud — Tue, 20 Sep 2022 06:34:54 GMT

Hi,

[quote user="davidb"]

#define NRF_LOG_ENABLED 1

Changed to 1 from 0 to enable logging. Also would then not compile until I added nrf_log_default_backends.c to project.

[/quote]

Yes, that is expected. For most example bootloader projects, there is a corresponding "_debug" project. The main addition here is logging. And for that reason, it also has more memory reserved (and a lower start address). The normal projects (without the "_debug" suffix) does not include the logger dependencies, nor is there room for the logger.

[quote user="davidb"]

I built the project as you did and it builds with no errors. FLASH1 is 99.9% used. Not much room left for adding anything.

RAM is only 14% used.

Any suggestions on how to safely change FLASH1 layout to make space for my apps?

[/quote]

The way this is shown in SES gives the wrong impression. This means that the bootloader uses almost everything of the allocated flash, but that is not the same as all the flash. See the screenshot from my previous post where i highlighted the linker configuration for the flash memory. In that case, the bootloader start address is 0xF8000, and everything there can be used for other things (like SoftDevice, application and persistent storage). See memory layout in the bootloader documentation for a better overview.

Regarding RAM the bootloader and application does not run at the same time, so the RAM usage of the bootloader does not have any impact on what is available for the application (it can overlap).

RE: 52840 SDK v17.1 Linker Errors Building DFU Bootloader

davidb — Mon, 19 Sep 2022 17:58:36 GMT

I built the project as you did and it builds with no errors. FLASH1 is 99.9% used. Not much room left for adding anything.

RAM is only 14% used.

Any suggestions on how to safely change FLASH1 layout to make space for my apps?

RE: 52840 SDK v17.1 Linker Errors Building DFU Bootloader

davidb — Mon, 19 Sep 2022 16:09:41 GMT

I had to make two changes to sdk_config.h:

// <i> Choose memory allocator used by nrf_crypto. Default is alloca if possible or nrf_malloc otherwise. If 'User macros' are selected, the user has to create 'nrf_crypto_allocator.h' file that contains NRF_CRYPTO_ALLOC, NRF_CRYPTO_FREE, and NRF_CRYPTO_ALLOC_ON_STACK.
// <0=> Default
// <1=> User macros
// <2=> On stack (alloca)
// <3=> C dynamic memory (malloc)
// <4=> SDK Memory Manager (nrf_malloc)

#ifndef NRF_CRYPTO_ALLOCATOR
#define NRF_CRYPTO_ALLOCATOR 2

I chose 2 (On stack). The example file has 1 (User macros) defined which cause a compile fail.

#define NRF_LOG_ENABLED 1

Changed to 1 from 0 to enable logging. Also would then not compile until I added nrf_log_default_backends.c to project.

These changes don't appear to add significant flash space.

RE: 52840 SDK v17.1 Linker Errors Building DFU Bootloader

Einar Thorsrud — Mon, 19 Sep 2022 06:57:34 GMT

Hi,

These linker warnings indicate that the bootloader is too large to fit in the assigned memory region. When I test, I get the same issue as you if I for instance reduce the size of the region (increase the start address and reduce the size) in the linker configuration or change the optimization. That is a bit odd though, as this example project builds fine when I test. Did you do any changes? If so, which?

So in short, this should not happen out of the box, but is expected in case of size changes. The question then is if the size change is wanted, and if so, you need to adjust the start address and size which you do here:

If this is not intentional though, I would first try to figure out why the size is larger than expected.

RE: 52840 SDK v17.1 Linker Errors Building DFU Bootloader

davidb — Fri, 16 Sep 2022 22:42:46 GMT

Some debug output:

Generating linker script ‘secure_bootloader_ble_s140_pca10056.ld’
Linking secure_bootloader_ble_s140_pca10056.elf
.text is too large to fit in FLASH1 memory segment
.text is larger than specified size
.crypto_data is too large to fit in FLASH1 memory segment
.dfu_trans is too large to fit in FLASH1 memory segment
.svc_data is too large to fit in FLASH1 memory segment
.log_const_data is too large to fit in FLASH1 memory segment
.nrf_balloc is too large to fit in FLASH1 memory segment
.sdh_ble_observers is too large to fit in FLASH1 memory segment
.sdh_req_observers is too large to fit in FLASH1 memory segment
.sdh_state_observers is too large to fit in FLASH1 memory segment
.sdh_stack_observers is too large to fit in FLASH1 memory segment
.sdh_soc_observers is too large to fit in FLASH1 memory segment
.fs_data is too large to fit in FLASH1 memory segment
.rodata is too large to fit in FLASH1 memory segment
.rodata is larger than specified size
.data is too large to fit in FLASH1 memory segment
section .tdata overlaps absolute placed section .mbr_params_page
section .mbr_params_page VMA [00000000000fe000,00000000000fefff] overlaps section .text VMA [00000000000f83b8,0000000000104127]
Build failed

FLASH1 size seems way too small. I have not added any of my own code to this project. This is just the code that came with the example. Config file attached.

devzone.nordicsemi.com/.../1452.sdk_5F00_config.h

RE: 52840 SDK v17.1 Linker Errors Building DFU Bootloader

davidb — Fri, 16 Sep 2022 21:13:06 GMT

I have done as you suggested - started a new bootloader project based on secure_bootloader_ble_s140_pca10056 Segger IDE solution. I built it but it fails due to linker errors:

Rebuilding ‘secure_bootloader_ble_s140_pca10056’ from solution ‘secure_bootloader_ble_s140_pca10056’ in configuration ‘Release’
Assembling ‘thumb_crt0.s’
Compiling ‘nrf_log_frontend.c’
Compiling ‘nrf_log_str_formatter.c’
Compiling ‘app_error_weak.c’
Compiling ‘app_scheduler.c’
Compiling ‘app_util_platform.c’
Compiling ‘crc32.c’
Compiling ‘mem_manager.c’
Compiling ‘nrf_assert.c’
Compiling ‘nrf_atfifo.c’
Compiling ‘nrf_atomic.c’
Compiling ‘nrf_balloc.c’
Compiling ‘nrf_fprintf.c’
Compiling ‘nrf_fprintf_format.c’
Compiling ‘nrf_fstorage.c’
Compiling ‘nrf_fstorage_nvmc.c’
Compiling ‘nrf_fstorage_sd.c’
Compiling ‘nrf_memobj.c’
Compiling ‘nrf_queue.c’
Compiling ‘nrf_ringbuf.c’
Compiling ‘nrf_section_iter.c’
Compiling ‘nrf_strerror.c’
Compiling ‘pb_common.c’
Compiling ‘pb_decode.c’
Compiling ‘cc310_bl_backend_ecc.c’
Compiling ‘cc310_bl_backend_ecdsa.c’
Compiling ‘cc310_bl_backend_hash.c’
Compiling ‘cc310_bl_backend_init.c’
Compiling ‘cc310_bl_backend_shared.c’
Compiling ‘boards.c’
Compiling ‘nrf_sdh.c’
Compiling ‘nrf_sdh_ble.c’
Compiling ‘nrf_sdh_soc.c’
Compiling ‘nrf_nvmc.c’
Compiling ‘nrfx_atomic.c’
Compiling ‘nrf_crypto_ecc.c’
Compiling ‘nrf_crypto_ecdsa.c’
Compiling ‘nrf_crypto_hash.c’
Compiling ‘nrf_crypto_init.c’
Compiling ‘nrf_crypto_shared.c’
Compiling ‘nrf_dfu_svci.c’
Compiling ‘nrf_dfu_svci_handler.c’
Compiling ‘nrf_svc_handler.c’
Compiling ‘ble_srv_common.c’
Compiling ‘nrf_bootloader.c’
Compiling ‘nrf_bootloader_app_start.c’
Compiling ‘nrf_bootloader_app_start_final.c’
Compiling ‘nrf_bootloader_dfu_timers.c’
Compiling ‘nrf_bootloader_fw_activation.c’
Compiling ‘nrf_bootloader_info.c’
Compiling ‘nrf_bootloader_wdt.c’
Assembling ‘ses_startup_nrf52840.s’
Assembling ‘ses_startup_nrf_common.s’
Compiling ‘system_nrf52840.c’
Compiling ‘dfu-cc.pb.c’
Compiling ‘nrf_dfu.c’
Compiling ‘nrf_dfu_ble.c’
Compiling ‘nrf_dfu_flash.c’
Compiling ‘nrf_dfu_handling_error.c’
Compiling ‘nrf_dfu_mbr.c’
Compiling ‘nrf_dfu_req_handler.c’
Compiling ‘nrf_dfu_settings.c’
Compiling ‘nrf_dfu_settings_svci.c’
Compiling ‘nrf_dfu_transport.c’
Compiling ‘nrf_dfu_utils.c’
Compiling ‘nrf_dfu_validation.c’
Compiling ‘nrf_dfu_ver_validation.c’
Compiling ‘oberon_backend_chacha_poly_aead.c’
Compiling ‘oberon_backend_ecc.c’
Compiling ‘oberon_backend_ecdh.c’
Compiling ‘oberon_backend_ecdsa.c’
Compiling ‘oberon_backend_hash.c’
Compiling ‘oberon_backend_hmac.c’
Compiling ‘dfu_public_key.c’
Compiling ‘main.c’
Generating linker script ‘secure_bootloader_ble_s140_pca10056.ld’
Linking secure_bootloader_ble_s140_pca10056.elf
.text is larger than specified size
.rodata is too large to fit in FLASH1 memory segment
.rodata is larger than specified size
.data is too large to fit in FLASH1 memory segment
section .tdata overlaps absolute placed section .mbr_params_page
section .mbr_params_page VMA [00000000000fe000,00000000000fefff] overlaps section .text VMA [00000000000f83b8,00000000000fea2f]
section .crypto_data VMA [00000000000fea30,00000000000fea37] overlaps section .mbr_params_page VMA [00000000000fe000,00000000000fefff]
section .bootloader_settings_page VMA [00000000000ff000,00000000000fffff] overlaps section .rodata VMA [00000000000feb28,00000000001005ab]
Output/Release/Obj/secure_bootloader_ble_s140_pca10056/main.o: in function `main':
undefined reference to `nrf_log_default_backends_init'
Build failed

RE: 52840 SDK v17.1 Linker Errors Building DFU Bootloader

davidb — Fri, 16 Sep 2022 16:10:36 GMT

I started from a previous projects segger solution file which was based on an older sdk version. We use sdk v17.1 now so getting this to compile is not easy.

How can I start a project with an example bootloader like pca10056_s140_ble while usig segger? The platform is based on an82540.

RE: 52840 SDK v17.1 Linker Errors Building DFU Bootloader

Einar Thorsrud — Fri, 16 Sep 2022 13:13:49 GMT

Hi,

It seems like you are missing some important files (nRFInitialize for instance is in the startup file, so that would be ses_startup_nrf52840.s if using the nRF52840 and Segger Embedded STudio ). I suggest you refer to a bootloader example to see all the files that are needed (or even better, start your project by copying an example and modifying that, instead of starting from scratch if that is what you have done).