After DFU application is not Booting

[Hardik Pokar]

Hello , 

I am trying DFU over BLE.I am using SDK 14.0.2 .

i Flashed Bootloader Code and Softdevice 5.0.0 .then Device is Starting Advertised as DfuTarg and As Mention in Documentation I done Update Through nRF Connect Mobile App.

After complete dfu Process Device is not Booting Application. I Tried with Different Different Application but Result is Same.

Below Step i am Following : 

- Compiled BootLoader Successfully with Correct Public Key inclusion.

- Download s132_5.0.0 Softdevice and Used s132_nrf52_5.0.0_softdevice.hex as it is .

- using Mergehex i merged bootloader.hex s132_nrf52_5.0.0_softdevice.hex -o Boot_Soft.hex

- I Erased Chip and Programmed with Boot_Soft.hex .Device Start Advertising DfuTarg Name .

- i Create Application Pkg using nrfutil 

  nrfutil pkg generate --hw-version 52 --sd-req 0x9D --application-version 2 --application application.hex --key-file privatehp.key application_dfu.zip

- I connect Mobile with DfuTarg and Using DFU option i uploaded application_dfu.zip package Successfully but after Completing Device is not booting Actual Application . LED 3 on Board Glowing Continuously.

Can you please Help me out from This .. Thanks !!!!!!!!!!

  

[Vidar Berg]

Hello,

Are you testing this on a Nordic dev kit, or a custom board? If you are testing on a custom board, please debug the bootloader and check if the nrf_dfu_button_enter_check() in nrf_dfu.c::nrf_dfu_enter_check() is returning true. The bootloader will enter DFU mode if this functiion return true. Maybe the button configuration is wrong for your board.

Also, have you verified that the application runs ok if you only flash the Softdevice and application with the debugger?

[Hardik Pokar]

Dear Vidar Berg,

Thanks For Response !!

I am Using Dev Kit. 

I verified that With Softdevice and Application my Application is not Working Properly.

And Also With Mergehex i am not able to merge hex Files. 

D:\NRF_SDK\DFU\BLE_OTA>

mergehex -m application.hex s132_nrf52_5.0.0_softdevice.hex -o Output.hex

Parsing input files.
Merging file "application.hex" into output.
Merging file "s132_nrf52_5.0.0_softdevice.hex" into output.
Overlapping segments detected at address 0.ERROR: The hex files cannot be merged since there are conflicts.

It's Giving Error Like this.

Can you Guide me what will be the Issue or how to Resolve this.

I tried with nrfjprog : 

nrfjprog -f NRF52 --program softdevice.bin application.hex --chiperase

Output Is not Proper.

Thanks !!

[Vidar Berg]

Hi,

The memory layout you posted is probably for a newer version of the s132. s132 v5.0.0 goes up to address 0x23000 as shown in the image I posted (you can also find the Softdevice size from the Softdevice release notes)

Hardik Pokar said:

In my application I am not using BLE Related Task , That is just Simple Example like UART and all. so For that also i have to give 0x23000 Location while Building ? 

It must start at 0x23000 if you are going to program it toghether with the s132 v5.

[Hardik Pokar]

Dear Vidar,

I tried below Scenario : 

Merge bootloader.hex softdevice.hex and app.hex we flashed through J-LINK then also Application not Booting ? 

I gave Bootloader_setting.hex also but Result is same . 

Thanks !!!!!

[Vidar Berg]

Does the application run ok now if you program it along with the Softdevice without the bootloader?

[Hardik Pokar]

Yes, Vidar.

Softdevice + Application is working Fine .
 

I have to Flash Bootloader_setttings.hex Also First Time ?

Thanks !!!

[Vidar Berg]

Yes, the Bootloader_setttings.hex  is needed to inform the bootloader that a valid application is present. It will stay in DFU mode otherwise.

[Hardik Pokar]

Thanks Vidar !!

I got it . Thanks !!