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

[Edvin]

Hello,

I believe the image was not uploaded successfully. Can you please try to upload it again?

Also, after flashing the device using nrf Connect for Desktop -> Programmer. Can you try to read it back and save the file to a .hex file(s)? Is it possible to upload both what you are trying to program and what you are reading back, so I can compare the two?

Question: Is it flashed successfully if you use e.g. west flash -d build (build being your build folder)? Or does it fail/get stuck in the bootloader in that case as well?

Best regards,

Edvin

[AiswaryaV]

Hi Edvin,

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