Region name in nRF Connect Programmer v3.3.2

RE: Region name in nRF Connect Programmer v3.3.2

Joe — Wed, 22 Apr 2020 17:43:41 GMT

Hi,

The address is the same for all three versions, and the bootloader is working. Perhaps some magic number has not been updated in the software. Please close this case.

RE: Region name in nRF Connect Programmer v3.3.2

Simonr — Fri, 17 Apr 2020 08:35:43 GMT

Hi Joe

Please check what the bootloader start address is set to in the 15.3 version. Is it the same as in the 15.0 and 16.0 versions of the project? Either way, the bootloader should work as intended even though it is recognized as Application by the Programmer in nRFConnect.

Best regards,

Simon

RE: Region name in nRF Connect Programmer v3.3.2

Joe — Thu, 16 Apr 2020 17:39:10 GMT

Hi,

I have rebuilt the dfu secure bootloader under ble_s132_pca10040 for SDK 15.0, 15.3 and 16.0. When I drag the hex file for 15.0 and 16.0 to the File memory layout window in the Programmer, the region name will display as "Bootloader". When I drag the hex file for 15.3, it will show up as "Application". Maybe there is some signature missing in the 15.3?

RE: Region name in nRF Connect Programmer v3.3.2

Simonr — Thu, 16 Apr 2020 09:21:07 GMT

All of this is open source, and you can see the algorithm/logic on our GitHub.

A short recap of how the various regions are detected:

Best regards,

Simon