sir,
help me in firmware updateing using j-link in nRF52840 .i have tried using both j-link and nRfgo studio. in nRFgo studio i could not find the nRF52 development dongle.
help me in updating firware
sir,
help me in firmware updateing using j-link in nRF52840 .i have tried using both j-link and nRfgo studio. in nRFgo studio i could not find the nRF52 development dongle.
help me in updating firware
Hi Sharon,
Is it a custom board that is using our nRF52840? have you ever been successful in flashing the program into this chip? If not, then the biggest suspect now could be something wrong with your schematics design or soldering.
If the chip was detectable before and is not anymore, then it is possible that you might have bricked the chip with you application trying to make the chip go to system off too early.
To give you more assistance, we need to know more about your board and what tests you did on that board that resulted in its failure (if it was working before)
Hi sir,
yes it is a custom board..yes i have flashed using Raspberry pi3.. but Im doing with segger j-link now also tried with nRFgo studio..with j-link i am not able to connect to target..
Yes sir we are testing on custom board.
We have flashed blinky.hex file using openocd software running on Raspberry Pi3 , it works fine as per the code. Which means that the schematic we are using is correct.
We are trying to flash the module with same hex file through segger J-link EDU to the same target device nRF52840 but we are unable to connect the target.
and now we are using J-Link command prompt not nRFgo Studio.
please follow the instructions in this post to see if you can use nordic DK (if you have any) to try to connect to your custom board. If you are not able to communicate then its most likely something wrong on your custom board, then follow HĂĄkon's recommendations to try to fix this. I am not aware of any problem on Nordic side for JTAG
Sir,
There was an issue with my target device nRF52840.
We were not able to connect the target device nRF52840 while updating firmware with segger j-link, we are able to connect the target now. What are further steps if you can guide me..
If you really want to use JLink.exe rather than nrfGo, then please download this script and run the documented commands.
Hello Sir,
Thanks for help.
The problem got solved
Steps are attached in nrf52840.txt file.
.
UPDATING FIRMWARE IN nRF52840 USING J-LINK COMMAND PROMPT. Steps are: 1.Connect J-Link to the PC. 2.Connect target system (nRF52840) to J-Link 3.Start J-Link Commander. Type the following commands: J-Link> loadbin <PathToBinFile>, <programmingaddress> J-Link>loadbin D:\Exe\ble_app.hex, 0x0 Halting CPU for downloading file. Downloading file [D:\Exe\ble_app.hex]... J-Link: Flash download: Bank 0 @ 0x00000000: 1 range affected (20480 bytes) J-Link: Flash download: Total time needed: 0.811s (Prepare: 0.038s, Compare: 0.105s, Erase: 0.423s, Program: 0.218s, Verify: 0.000s, Restore: 0.024s) O.K. J-Link> progamming address is: 0x0 link for reference : https://www.segger.com/products/debug-probes/j-link/technology/flash-download/
Hello Sir,
Thanks for help.
The problem got solved
Steps are attached in nrf52840.txt file.
.
UPDATING FIRMWARE IN nRF52840 USING J-LINK COMMAND PROMPT. Steps are: 1.Connect J-Link to the PC. 2.Connect target system (nRF52840) to J-Link 3.Start J-Link Commander. Type the following commands: J-Link> loadbin <PathToBinFile>, <programmingaddress> J-Link>loadbin D:\Exe\ble_app.hex, 0x0 Halting CPU for downloading file. Downloading file [D:\Exe\ble_app.hex]... J-Link: Flash download: Bank 0 @ 0x00000000: 1 range affected (20480 bytes) J-Link: Flash download: Total time needed: 0.811s (Prepare: 0.038s, Compare: 0.105s, Erase: 0.423s, Program: 0.218s, Verify: 0.000s, Restore: 0.024s) O.K. J-Link> progamming address is: 0x0 link for reference : https://www.segger.com/products/debug-probes/j-link/technology/flash-download/