RE: in the SDK 15.3,How to directly execute the application when the DFU function is added。MCU：nrF52832

RE: RE: in the SDK 15.3,How to directly execute the application when the DFU function is added。MCU：nrF52832

Ming — Wed, 30 Oct 2019 10:35:59 GMT

oh，UnbelievableI need to confirm. thank you so much

best wish.

RE: RE: in the SDK 15.3,How to directly execute the application when the DFU function is added。MCU：nrF52832

Vidar Berg — Wed, 30 Oct 2019 10:30:18 GMT

Hi,

It seems to work. I created the settings page and merged it with your hex files. You can see the debug log below.

devzone.nordicsemi.com/.../bl_5F00_sd_5F00_app_5F00_settings.hex

devzone.nordicsemi.com/.../3513.settings.hex

Can you try the merged hex and see if you get the same result?

RE: RE: in the SDK 15.3,How to directly execute the application when the DFU function is added。MCU：nrF52832

Ming — Wed, 30 Oct 2019 08:42:37 GMT

Of course, this is my pleasure.devzone.nordicsemi.com/.../8640.s132_5F00_nrf52_5F00_6.1.1_5F00_softdevice.hex devzone.nordicsemi.com/.../5123.nrf52832_5F00_xxaa_5F00_s132.hex devzone.nordicsemi.com/.../8750.nrf52832_5F00_xxaa.hex

RE: RE: in the SDK 15.3,How to directly execute the application when the DFU function is added。MCU：nrF52832

Vidar Berg — Wed, 30 Oct 2019 08:35:31 GMT

Hi,

Can you upload the .hex files you use so I can try it here? I can make the ticket private if you want.

RE: RE: in the SDK 15.3,How to directly execute the application when the DFU function is added。MCU：nrF52832

Ming — Wed, 30 Oct 2019 07:51:08 GMT

Thank you,but It doesn't seem to change anything.

PS E:\key> nrfutil settings generate --family NRF52 --application nrf52832_xxaa.hex --application-version 1 --bootloader-version 2 --bl-settings-version 1 bootloader_setting.hex                                                               
Generated Bootloader DFU settings .hex file and stored it in: bootloader_setting.hex

Bootloader DFU Settings:
* File:                 bootloader_setting.hex
* Family:               nRF52
* CRC:                  0x8ADC5471
* Settings Version:     0x00000001 (1)
* App Version:          0x00000001 (1)
* Bootloader Version:   0x00000002 (2)
* Bank Layout:          0x00000000
* Current Bank:         0x00000000
* Application Size:     0x00011814 (71700 bytes)
* Application CRC:      0xECCD8805
* Bank0 Bank Code:      0x00000001

PS E:\key> mergehex --merge nrf52832_xxaa_s132.hex bootloader_setting.hex --output output.hex
Parsing input hex files.
Merging files.
Storing merged file.
PS E:\key>

RE: RE: in the SDK 15.3,How to directly execute the application when the DFU function is added。MCU：nrF52832

Vidar Berg — Wed, 30 Oct 2019 07:16:01 GMT

Thank you. I see you've set the "--bootloader-settins-version" '1'. It should be '2' since you use SDK 15.3.0. Can you try to change it and see if it helps?

RE: RE: in the SDK 15.3,How to directly execute the application when the DFU function is added。MCU：nrF52832

Ming — Wed, 30 Oct 2019 05:43:14 GMT

of course,I learned from this blog，and I am doing this too.

When I downloaded all the hex (soft device, bootloader, application.hex) files, the device started broadcasting "DFUTarg".And I tried to update through DFU, it succeeded.

Then,

nrfutil settings generate --family NRF52 --application myapp.hex --application-version 0 --bootloader-version 0 --bl-settings-version 1 bootloader_setting.hex

After generating boot seting, I use nrf connect to download both softdevcie, boot, boot setting and app.When I found that there was no change, I combined the bootloader and setting into a file.But the result is the same after downloading.

These are the logs that the NRF connect prints when programming

2019-10-30T05:39:44.987Z INFO Parsing HEX file:  E:\key\s132_nrf52_6.1.1_softdevice.hex
2019-10-30T05:39:44.987Z INFO File was last modified at  2018/11/2 下午2:39:16
2019-10-30T05:39:45.066Z INFO Data block: 0x00000000-0x00000B00 (0x00000B00  bytes long)
2019-10-30T05:39:45.067Z INFO Data block: 0x00001000-0x00025150 (0x00024150  bytes long)
2019-10-30T05:39:45.068Z INFO SoftDevice detected, id 0xB7 (S132 v6.1.1)
2019-10-30T05:39:45.089Z INFO Parsing HEX file:  E:\key\output.hex
2019-10-30T05:39:45.089Z INFO File was last modified at  2019/10/30 下午1:37:15
2019-10-30T05:39:45.102Z INFO Data block: 0x00000FF8-0x00001000 (0x00000008  bytes long)
2019-10-30T05:39:45.102Z INFO Data block: 0x00078000-0x0007DD0C (0x00005D0C  bytes long)
2019-10-30T05:39:45.102Z INFO Data block: 0x0007F000-0x0007F05C (0x0000005C  bytes long)
2019-10-30T05:39:45.104Z INFO SoftDevice detected, id 0xB7 (S132 v6.1.1)
2019-10-30T05:39:45.116Z INFO Parsing HEX file:  E:\key\nrf52832_xxaa.hex
2019-10-30T05:39:45.116Z INFO File was last modified at  2019/10/30 下午1:26:36
2019-10-30T05:39:45.147Z INFO Data block: 0x00026000-0x00037814 (0x00011814  bytes long)
2019-10-30T05:39:45.148Z INFO SoftDevice detected, id 0xB7 (S132 v6.1.1)
2019-10-30T05:39:56.760Z INFO Recovery procedure finished
2019-10-30T05:39:56.764Z INFO Using nrfjprog to communicate with target
2019-10-30T05:39:58.057Z INFO Using J-Link Software version 6.50
2019-10-30T05:40:00.749Z INFO Segger serial:  682973788
2019-10-30T05:40:00.749Z INFO Segger speed:  2000  kHz
2019-10-30T05:40:00.749Z INFO Segger version:  J-Link OB-SAM3U128-V2-NordicSemi compiled Jan  7 2019 14:07:15
2019-10-30T05:40:00.770Z INFO Probed: 682973788.
2019-10-30T05:40:00.771Z INFO Model: NRF52832_xxAA_REV2.
2019-10-30T05:40:00.771Z INFO RAM: 64KiB.
2019-10-30T05:40:00.771Z INFO Flash: 512KiB in pages of 4KiB.
2019-10-30T05:40:03.089Z INFO Reading device non-volatile memory. This may take a few seconds.
2019-10-30T05:40:03.330Z INFO SoftDevice detected, id 0xB7 (S132 v6.1.1)
2019-10-30T05:40:03.334Z INFO Writing procedure starts
2019-10-30T05:40:16.211Z INFO Write procedure finished
2019-10-30T05:40:16.212Z INFO Using nrfjprog to communicate with target
2019-10-30T05:40:17.373Z INFO Using J-Link Software version 6.50
2019-10-30T05:40:18.426Z INFO Segger serial:  682973788
2019-10-30T05:40:18.426Z INFO Segger speed:  2000  kHz
2019-10-30T05:40:18.426Z INFO Segger version:  J-Link OB-SAM3U128-V2-NordicSemi compiled Jan  7 2019 14:07:15
2019-10-30T05:40:18.447Z INFO Probed: 682973788.
2019-10-30T05:40:18.448Z INFO Model: NRF52832_xxAA_REV2.
2019-10-30T05:40:18.448Z INFO RAM: 64KiB.
2019-10-30T05:40:18.448Z INFO Flash: 512KiB in pages of 4KiB.
2019-10-30T05:40:19.648Z INFO Reading device non-volatile memory. This may take a few seconds.
2019-10-30T05:40:19.827Z INFO SoftDevice detected, id 0xB7 (S132 v6.1.1)

PS E:\key> nrfutil settings generate --family NRF52 --application nrf52832_xxaa.hex --application-version 0 --bootloader-version 0 --bl-settings-version 1 bootloader_setting.hex

Generated Bootloader DFU settings .hex file and stored it in: bootloader_setting.hex

Bootloader DFU Settings:
* File:                 bootloader_setting.hex
* Family:               nRF52
* CRC:                  0xE890C494
* Settings Version:     0x00000001 (1)
* App Version:          0x00000000 (0)
* Bootloader Version:   0x00000000 (0)
* Bank Layout:          0x00000000
* Current Bank:         0x00000000
* Application Size:     0x00011814 (71700 bytes)
* Application CRC:      0xECCD8805
* Bank0 Bank Code:      0x00000001

PS E:\key> mergehex --merge nrf52832_xxaa_s132.hex bootloader_setting.hex --output output.hex
Parsing input hex files.
Merging files.
Storing merged file.

RE: RE: in the SDK 15.3,How to directly execute the application when the DFU function is added。MCU：nrF52832

Vidar Berg — Tue, 29 Oct 2019 08:05:44 GMT

Can you show how you're generating and programming the settings page?

RE: RE: in the SDK 15.3,How to directly execute the application when the DFU function is added。MCU：nrF52832

Ming — Tue, 29 Oct 2019 01:17:43 GMT

Yes, I set it up according to this blog step, use nRF connect to load SD+APP+BL and then enter Dfutarg. Add bootloader setting is still like this.

RE: RE: in the SDK 15.3,How to directly execute the application when the DFU function is added。MCU：nrF52832

Vidar Berg — Mon, 28 Oct 2019 13:48:28 GMT

Hi,

Assume you're loading the app FW with the Debugger and not through DFU? In that case, have you tried to follow the steps outlined in appendix 1 of this blog post here: https://devzone.nordicsemi.com/nordic/nordic-blog/b/blog/posts/getting-started-with-nordics-secure-dfu-bootloader?