After DFU application is not Booting

RE: After DFU application is not Booting

Hardik Pokar — Wed, 20 Jan 2021 09:39:58 GMT

Thanks Vidar !!

I got it . Thanks !!

RE: After DFU application is not Booting

Vidar Berg — Wed, 20 Jan 2021 09:37:38 GMT

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

RE: After DFU application is not Booting

Hardik Pokar — Wed, 20 Jan 2021 09:10:47 GMT

Yes, Vidar.

Softdevice + Application is working Fine .

I have to Flash Bootloader_setttings.hex Also First Time ?

Thanks !!!

RE: After DFU application is not Booting

Vidar Berg — Wed, 20 Jan 2021 08:01:18 GMT

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

RE: After DFU application is not Booting

Hardik Pokar — Tue, 19 Jan 2021 12:06:27 GMT

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 !!!!!

RE: After DFU application is not Booting

Vidar Berg — Tue, 19 Jan 2021 12:02:28 GMT

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)

[quote userid="97392" url="~/f/nordic-q-a/70557/after-dfu-application-is-not-booting/289975#289975"]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 ? [/quote]

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

RE: After DFU application is not Booting

Hardik Pokar — Tue, 19 Jan 2021 10:53:25 GMT

Dear Vidar ,

I am Refering This memory mapping , Is this Correct for SDK 14.2.0 / s132 5.0.0 , Mapping as Below:

If this is not correct can you please give me Correct Mapping ?

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 ?

Bootloader_settings.hex file need to flash for First time ?

Thanks !!!

RE: After DFU application is not Booting

Vidar Berg — Tue, 19 Jan 2021 10:28:31 GMT

Hi,

It looks like the application.hex has been linked with the wrong start address in flash based on the error you are getting from mergehex. Please go over the linker settings and make sure the start address have been set to 0x23000 like in the other SDK BLE examples.

Memory layout configuration settings if you're using the Segger embedded studio IDE

RE: After DFU application is not Booting

Hardik Pokar — Mon, 18 Jan 2021 13:43:24 GMT

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 !!

RE: After DFU application is not Booting

Vidar Berg — Mon, 18 Jan 2021 10:49:20 GMT

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?