secure_bootloader_ble_s112_pca10040e SDK15.3 Keil

Question

Hello! 
 In SDK15.3 project "secure_bootloader_ble_s112_pca10040e" for Keil , write flash incorrect and not work. 
 In SDK15.2 this prodject work fine.

Please correct in the new version. 
 Best regards.

Turnaev · Accepted Answer

bjorn-spockeli , thanks for you help! 
 I checked, really if flashing the bootloader along with the software library, then everything works. This is a little inconvenient, since it is necessary to flash it with an external program. I made two * .bat files to simplify the firmware and start debugging, maybe someone else will come in handy. 
 bootloaderKeilFlashAndDebug.zip

bjorn-spockeli · Answer

I think I managed to reproduce it and that I know the cause. 
 In SDK v15.3.0 we have started storing the bootloader start address on the MBR params page in addition to the UICR register. This means that the compiled bootloader binary will write to the MBR section (starting at 0x00000000). This page already contains some data and unfortunately, the flash algorithm used by Keil requires the entire page to be erase prior to writing to it. 
 So when using Keil you will have to merge the bootloader hex with the S112 SoftDevice hex and then flash the merged hex file. If you're using Segger Embedded Studio, then this is not an issue as it does not require the page to be erased. 
 Best regards 
 Bjørn

secure_bootloader_ble_s112_pca10040e SDK15.3 Keil

Top Replies