nRF51 devkit - how to restore the original Atmel JLink firmware

Question

I programmed an nRF51 devkit for wireshark/nrfsniffing, but now need to restore the original or updated Atmel firmware on nrf51 dev kit for programming BLE chips. Where do I find the JLink files and instructions? 
 Currently the nRF Connect for Desktop Programmer finds the board and displays nRF51 DK, but no mem layout or family. Opening a hex file does nothing but throw JLink errors:

10:35:41.679 
 Using nrfutil-device version: 2.0.3

10:35:41.679 
 Using nrf-device-lib version: 0.17.3

10:35:41.679 
 Using nrfjprog DLL version: 10.23.1

10:35:41.679 
 Using JLink version: JLink_V7.80c

10:35:41.679 
 Installed JLink version does not match the expected version (JLink_V7.88j)

10:35:41.807 
 Getting serialport options from persistent store D200BCKB.pc-nrfconnect-programmer

10:35:44.114 
 Getting serialport options from persistent store 000681344811.pc-nrfconnect-programmer

10:35:44.457 
 Getting serialport options from persistent store 000681344811.pc-nrfconnect-programmer

10:36:38.588 
 Error: Failed with exit code 1. Failed to device info one or more devices: * 681344811: [jlink] JLINKARM_DLL_ERROR, code: Nrfjlink. Message: Operation device-info failed, [jlink] JLINKARM_DLL_ERROR.

10:36:38.589 
 Using nrfutil device to communicate with target via JLink

10:36:40.312 
 Reading readback protection status for Application core

10:36:40.313 
 Failed to reading readback protection status for application core core. Error: [object Object], message: Batch task protection-get failed, [jlink] JLINKARM_DLL_ERROR

10:36:40.556 
 Error: Failed with exit code 1. One or more batch tasks failed: - [jlink] JLINKARM_DLL_ERROR, code: Nrfjlink. Message: Batch task protection-get failed, [jlink] JLINKARM_DLL_ERROR.

10:59:30.491 
 Parsing HEX file: M:\Wald\BLE\UART_Flex_FWCode\customService2\pca10028\s130\arm5_no_packs\_build\BLE_ForeWarm_V0_4_7.hex

10:59:30.501 
 File was last modified at 12/13/2023, 3:29:25 PM

10:59:30.517 
 Update files regions according to Application core

10:59:30.517 
 Parse memory regions for file

Einar Thorsrud · Accepted Answer

Hi, 
 Steve said: I would be happy to just ignore the INVALID_DEVICE err., but when the BLE device is programmed this way, it advertises, but cannot connect to our App. Nor can Nordic nRF Connect - which throws log Error 133 (0x85): GATT ERROR. Again the J-Link is my prime suspect. 
 You are able to program the device, and it advertises, so I do not see why there is any reason to suspect an issue with the J-Link? 
 Steve said: this time with Error 8: GATT CONN TIMEOUT. This change in response tells me either the J-Link firmware was corrupted, 
 This indicate an issue in the nRF or peer device, somethign causing Bluetooth problems. Not an issue with the J-Link. As you get this, you are even able to debug, so the debugger seems to work fine. 
 Steve said: I think I might also have something else wrong now... the DK on board BLE has different pin configurations than what this firmware expects for my custom PCB. I'll get back to you. 
 This seems to be closer to the issue. It will be interesting to hear what you learn from your debugging. 
 Steve said: Why doesn't the Programmer have a Verify function? Glaring omission! 
 I agreee. I suggest you use nrfjprog for that (and for other programming tasks as well if you are fine with command line tools). It has more features. Note that from nRF Command Line tools version 10.23.4 we no longer test on nRF51, so you should stick with 10.23.2. 
 Steve said: I still get the INVALID_DEVICE error but apparently it can be ignored. 
 Yes. There are some issues with thenRF51 compatibility in the programmer app as it is no longer being tested on the nRF51 DK and will not support the nRF51 going forward.

Steve · Answer

Einar, 
 I am not using mbed. I can program and read back, but always the INVALID_DEVICE error shows up. 
 I would be happy to just ignore the INVALID_DEVICE err., but when the BLE device is programmed this way, it advertises, but cannot connect to our App. Nor can Nordic nRF Connect - which throws log Error 133 (0x85): GATT ERROR. Again the J-Link is my prime suspect. 
 The SEGGER J-Link Configuration V6.34b shows this emulator connected via USB: 
 
 Product: J-Link OB-SAM3U128-V2-NordicSem V1.00 
 S/N: 681344811 (matches the label on the DK Atmel cover) 
 USB Id: same as S/N 
 Host Firmware: 2018 Jul 12 11:44 
 Emulator Firmware: 2022 Sep 21 09:5* (New) 
 
 After replacing firmware, above list remains the same except : 
 
 Emulator Firmware: 2018 Jul12 11:44 
 
 I still get the INVALID_DEVICE error, BUT now the device can connect with nRF Connect, but only briefly before it disconnects, this time with Error 8: GATT CONN TIMEOUT. This change in response tells me either the J-Link firmware was corrupted, or the old Host and new Emulator Firmware are incompatible. PLEASE CHECK the instructions for installing Wireshark and nRF Sniffer for problems with the J-Link changes!!! 
 I think I might also have something else wrong now... the DK on board BLE has different pin configurations than what this firmware expects for my custom PCB. I'll get back to you. 
 Why doesn't the Programmer have a Verify function? Glaring omission! 
 Alright, I did have problems on my end too. With the right firmware and the right App, the Programmer can load the firmware and it will run properly. I still get the INVALID_DEVICE error but apparently it can be ignored.

nRF51 devkit - how to restore the original Atmel JLink firmware

Top Replies