After Flashing via nrfConnect via desktop , application does not restart

[AiswaryaV]

Hello team,

I have the issue in some samples of nrf5340, after I successful erase and flash, the controller seem to be stuck at bootloader.

I observed the below image on nrfConnect Programmer app after flashing and reading back the firmware.

Can you please explain to me what this means as this does not seem to be usual?

In usual flashing the regions read from the controller is almost the same as the files flashed.

And why is the controller stuck at Bootloader

[Nishant Gaurav]

Hi aiswaraya,

can you please tell me, are you using dk board or custom board ( eg :- nrf5340dk ), Is your board designed for DCDC or LDO power mode. Are you flashing both the application core and network core images. What exact files are you flashing (e.g., merged.hex).

Thanks and regards

Nishant

[AiswaryaV]

HI Nishant,

I am using the merged.hex and merged_NET.hex.

I still need to check the power mode.

[Nishant Gaurav]

1. is it a dk baord or custom board.
2. Use west flash instead of manual hex flashing, as it handles multi-image flashing correctly.

   Using nrfutil manually (flash both cores separately):

   1. Flash the network core:
   nrfutil device program --firmware zephyr.hex --options chip_erase_mode=ERASE_ALL --core Network

       

   2. Flash the application core:

   nrfutil device program --firmware zephyr.hex --options chip_erase_mode=ERASE_ALL

       

   3. Reset the board:

   nrfutil device reset --reset-kind=RESET_PIN

       

[AiswaryaV]

Hi Nishant,

Thanks for the reply.

I use a custom board.

It was found that the external flash parts were different in the sample I flashed and I was not informed. Hence the SW was referring to the old external flash configuration. I hope to solve the issue after changing the external flash configuration.

BR,

Aiswarya

[Nishant Gaurav]

Hi,

thanks for your confirmation, let me know if it works.

thanks and regards

Nishant