• State Not Answered
  • Locked Locked
  • Replies 16 replies
  • Subscribers 73 subscribers
  • Views 6906 views
  • Users 0 members are here
Attachments (0)
Nordic Case Info
  • Case ID: 118120
Options
This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

can't program bootloader code by nrfjprog tool

leif

Hi Nordic, we need to modify bootloader code base on your dfu example. Now We meet a problem that we can't program it by clicking icon "Load" on keil comile project. report error as below:

//-----------------------------------------------------------------------
Programing device.
ERROR: JLinkARM DLL reported an error. Try again. If error condition
ERROR: persists, run the same command again with argument --log, contact Nordic
ERROR: Semiconductor and provide the generated log.log file to them.
nrfjprog.exe --program "D:\project\SPW07A\Bootloader_Code\examples\dfu\bootloader\pca10040\dual_bank_ble_s132\arm5_no_packs\_build\nrf52832_xxaa_s132.HEX" -f NRF52  --chiperase --log
Parsing hex file.
Erasing code and UICR flash areas.
Applying system reset.
Checking that the area to write is not protected.
Programing device.
ERROR: JLinkARM DLL reported an error. Try again. If error condition
ERROR: persists, run the same command again with argument --log, contact Nordic
ERROR: Semiconductor and provide the generated log.log file to them.
-----------------------------------------------------------------------------------------------------//

according to error's hint, I add --log after --program "#H" -f NRF52 --chiperase --log and get the log text. pls refer the attached file.JLinkARM.log.txt but i can't find the reason. if we use the same project to program it on EVB PCA10040, it is ok. why ? Is the different between the EVB PCA10040 's JLINK and our JLINK cause the issue? how to fix it? Thanks.

  • 0 in reply to leif

    If you can program/erase/recover the nRF52 DK(PCA10040) via the J-LINK On-Board chip on the DK with nrfjprog, then there is nothing wrong with your nrfjprog setup. This suggests that there is an issue with your J-Link probe and I am trying to find out if its a genuine Segger Debug probe. If its not a genuine debug probe, then it could be that some of the commands work and some do not. Comparing the photo with the pictures on Segger webpage you can see that "j-link" is written in a different font than on the Segger webpage. Where did you buy the debug probe?

Related
Terms of service