Failed to download firmware in Segger Embedded Studio

[kokheng]

Hi,

I have an error to download firmware in nRF52840-DK, from output console show it failed at verification on address 0x00000000. 

I try to compile the light switch example from "\examples\light_switch\client\" folder into two nRF52840-DK boards but somehow only one board success, Can you help me to figure out what happens?

Thanks 

Output Console

Preparing target for download
Executing script TargetInterface.resetAndStop()
Reset: Halt core after reset via DEMCR.VC_CORERESET.
Reset: Reset device via AIRCR.SYSRESETREQ.
Downloading ‘s140_nrf52_6.1.0_softdevice.hex’ to J-Link
Programming 2.5 KB of addresses 00000000 — 00000a17
Programming 147.6 KB of addresses 00001000 — 00025e7b
J-Link: Flash download: Bank 0 @ 0x00000000: 1 range affected (155648 bytes)
J-Link: Flash download: Total time needed: 2.345s (Prepare: 0.048s, Compare: 0.018s, Erase: 0.000s, Program: 2.267s, Verify: 0.003s, Restore: 0.008s)
Verification failed @ address 0x00000000

[kokheng]

when I use the nRF Connect v2.6.1  - Programmer app, it will always be hanged when I flash the s140_nrf52_6.1.0_softdevice.hex.

Is this indicate that the board flash got a problem?

 

[Bjørn Kvaale]

Can you please try to download the light switch example via Segger Embedded Studios? First erase the board (either via nRF Programmer app) or via nrfjprog. Then, compile the example in SES. Next, press Target -> Connect J-Link. Then, press Target -> Download <project name>, where project name could be ble_app_blinky_pca10040_s132 or light switch_pca10040... for example. Does that work?

[Bjørn Kvaale]

2) I did not mean that you should cut the solder bridge. I was just wondering if you did or not. If you did, you would have needed to attach a jumper to P22.

What you can do is try to flash the interface mcu to the nRF52 DK one more time. Turn off the DK & turn it back on while pressing the IF BOOT/RESET button. You should then see the DK appear as a BOOTLOADER drive. Drag & drop the downloaded Interface MCU FW to the malfunctioning DK. Power cycle the board one more time & try to program by via Segger again.

[kokheng]

1) manage to place the bin file (i.e. J-Link OB-SAM3U128-V2-NordicSemi 170724.bin) to the DK. 

2) Power cycle the board again

3) Program the DK via Segger, but it requires firmware Update 

      

4) After I press No button, it failed to connect J link.

5) Thus, I repeat the step from 1 to 3, and then press Yes button to run the J-Link V6.40 Firmware update

6) After executing the firmware update, it will go to flash the example code into flash and then same flash error come again.

Please let me know if my step is not correct or bin file download is not the latest version. Thanks

[Bjørn Kvaale]

You chose the correct interface MCU FW. It was also correct to update the J-Link FW. Could you try an nrfjprog --recover command on the faulty board & then try to program the board again via SES? Does this work?

P.S. If you add the nrfjprog command to the system path (i.e. Environment variables), you won't need to be in the nrfjprog folder to execute the command.

& just so I understand correctly. Programming the softdevice & the light switch example worked via nrfjprog on both boards, correct? Seems like it from the command line log you provided.

[kokheng]

1) using nrfjprog --recover then program again via SES ---> this method doesn't work. 

2) and yes, both boards are able to program using nrfjprog command but the faulty board didnt pass the flash verification. 

Can I make the conclusion that the faulty board unable to recover by Nordic tools and require to send for hardware inspection by element14?

When compare flash memory found some hex value is not the same.  

[Bjørn Kvaale]

Yes, I believe we can conclude that this could be a faulty board. Ask element14 to check the HW.