RE: sdk 13.1 DFU (bootloader_secure_ble)

bjorn-spockeli — Fri, 14 Jul 2017 13:12:56 GMT

I have edited my answer.

RE: sdk 13.1 DFU (bootloader_secure_ble)

Linxi — Fri, 14 Jul 2017 00:30:31 GMT

Thanks for your support . Q1: What are the correct IROＭ and RAM settings for bootloader and applicationn project respectively, in Keil Target setting.

RE: sdk 13.1 DFU (bootloader_secure_ble)

bjorn-spockeli — Thu, 13 Jul 2017 14:31:06 GMT

Q1: The correct Keil memory settings for the Secure Bootloader project are

IROM1 Start: 0x78000     Size: 0x6000
IRAM1 Start: 0x20002060  Size: 0xDA70

The correct memory settings for the ble_ant_app_hrm example are

  IROM1 Start: 0x29000    Size: 0x57000
  IRAM1 Start: 0x20002560 Size: 0xDAA0

Q2: Yes, you only need to compile the bootloader against the headers of the S332 and add S332 to the compiler flags.

The reason to why the bootloader does not jump to the application is because it calculates the CRC of the application and compares it to the CRC stored on the bootloader settings flash page, if they match, then the bootloader jumps to the application. The bootloader settings page is default set to 0s unless a bootloader settings page is flashed to the device. You can create a bootloader settings page

nrfutil.exe settings generate --family NRF52 --application <name of application hex> --application-version 1 --bootloader-version 1 --bl-settings-version 1 bootloader_settings.hex

The resulting bootloader_settings.hex file should be merged with the bootloader hex file using mergehex and then flashed to the nRF52 together with the S332 SoftDevice and the application.