DFU: Settings to compile secure_bootloader_ble_s140_pca10056.hex

Question

What are the memory settings in the SES compiler to compile secure_bootloader_ble_s140_pca10056 
 When I try to merge: 
 mergehex --merge s140_nrf52_7.2.0_softdevice.hex target_application.hex secure_bootloader_ble_s140_pca10056.hex --output temp_merg.hex 
 I get the failed message: 
 Parsing input files. Merging file "s140_nrf52_7.2.0_softdevice.hex" into output. Merging file "target_application.hex" into output. Merging file "secure_bootloader_ble_s140_pca10056.hex" into output. Overlapping segments detected at address 159744.ERROR: The hex files cannot be merged since there are conflicts. 
 Do I need to change any of the memory settings for the Linker? 
 Memory Segments, or Section Placement Macros? 
 In SES, The secure_bootloader_ble_s140_pca10056 project indicates it inherits from project in Common configuration 
 "FLASH_PH_START=0x0; 
 FLASH_PH_SIZE=0x100000; 
 RAM_PH_START=0x20000000; 
 RAM_PH_SIZE=0x40000; 
 FLASH_START=0xf8000; 
 FLASH_SIZE=0x6000; 
 RAM_START=0x20005978; 
 RAM_SIZE=0x3a688" 
 I got it to work some time ago with nRF5_SDK_17.0.2_d674dde, but now I use nRF5_SDK_17.1.0_ddde560 with no luck 
 Any help appreciated

Renix · Accepted Answer

Karl, 
 I did look at the release notes for the nRF5 SDK v17.1.0. 
 It mentions that 
 mergehex.exe, which can produce a corrupted hex file.
The issue has been fixed in the SES section-placement file (flash_placement.xml)
by setting the memory section size attribute to 4. I use SES V5.62, so that should be OK. I use the latest mergehex version: 10.14.0 What should the Section Placement Macros for the secure_bootloader_ble_s140_pca10056 be? It is not clear if the placement causes the problem, or if mergehex still corrupts the hex file because of misalignment. Any help appreciated

Renix · Answer

I have the mergehex working. 
 The issue was, I had to change Linker ->Memory Segments: 
 FLASH1 RX 0x0 0x100000;RAM1 RWX 0x20000000 0x40000;mbr_params_page RX 0x000FE000 0x1000;bootloader_settings_page RX 0x000FF000 0x1000;uicr_bootloader_start_address RX 0x10001014 0x4;uicr_mbr_params_page RX 0x10001018 0x4 
 The only uncertainty still is that one can use FLASH RX 0x0 0x100000; or FLASH1 RX 0x0 0x100000; 
 Both work?

DFU: Settings to compile secure_bootloader_ble_s140_pca10056.hex

Top Replies