can't program bootloader code by nrfjprog tool

RE: can't program bootloader code by nrfjprog tool

bjorn-spockeli — Fri, 09 Dec 2016 12:00:17 GMT

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?

RE: can't program bootloader code by nrfjprog tool

leif — Fri, 09 Dec 2016 11:00:10 GMT

Our J-link use SWD interface to program or debug 52832 IC by using JFLASH. do you mean that my J-link not support using SWD infterface to program it if using your nrjfprog tool? why using nrjfprog erase and recover cmd that are ok?

RE: can't program bootloader code by nrfjprog tool

bjorn-spockeli — Fri, 09 Dec 2016 10:31:43 GMT

Is it a J-Link Base or a J-Link Plus? Judging by the markings on the case, it would appear that it only supports the JTAG interface and not SWD which is used by the nRF51.

RE: can't program bootloader code by nrfjprog tool

leif — Fri, 09 Dec 2016 10:02:24 GMT

Pls find the pictures about J-Link debug probe.IMG_20161209_175837.jpg

RE: can't program bootloader code by nrfjprog tool

bjorn-spockeli — Fri, 09 Dec 2016 09:29:31 GMT

Yes, a picture of the J-Link debug probe connected to you board.

RE: can't program bootloader code by nrfjprog tool

leif — Fri, 09 Dec 2016 00:50:38 GMT

sorry, i can't understand it. what debug probe picture do you need to check it? pictcure of really hardware with J-LINK connecting to my product?

RE: can't program bootloader code by nrfjprog tool

bjorn-spockeli — Thu, 08 Dec 2016 10:39:11 GMT

Can you post a picture of the debug probe as well? Looking at the JLinkARM.log.txt file I see that the firmware on the debug probe was compiled in 2018

Firmware: J-Link ARM V8 compiled Jan 31 2018 18:34:52

which does not make any sense.

RE: can't program bootloader code by nrfjprog tool

leif — Thu, 08 Dec 2016 01:55:33 GMT

pls find th attached picture about J-link debug probe.e

RE: can't program bootloader code by nrfjprog tool

leif — Thu, 08 Dec 2016 01:52:59 GMT

We can debug our board by our J-Link with port SWD and program our board by JFlash. We have developed my product successfully.it mean that my J-link debug probe is ok and why using nrfjprog erase cmd that is ok but using nrfjprog program cmd that failed on our board. Now in production stage, we want to use your nrfjprog cmd group to progarm mass production in factory efficiently .Another, how to upload the attached picture or schematic to your devzone site? I can't find the way.

RE: can't program bootloader code by nrfjprog tool

bjorn-spockeli — Wed, 07 Dec 2016 13:46:30 GMT

Well, if you're able to program the nRF52 DK(PCA10040) then this cannot be an issue with your J-Link driver setup. Which J-Link debug probe are you using(J-Link Pro, Ultra+, Plus or Base)? Could you also attach a picture or schematic showing how the debug probe is connected to your custom board?

RE: can't program bootloader code by nrfjprog tool

leif — Wed, 07 Dec 2016 09:42:28 GMT

On our board,it still failed. using cmd nrfjprog -f nrf52 --recover and nrfjprog -f nrf52 -e are ok. but using cmd nrfjprog -f --program .hex that failed and report above error info. if use the same cmd to progamm your EVB pca10040 that is ok. it report info as below:

D:\project\VOX02_OLED\code\examples\ble_peripheral\nrf5-ble-tutorial-service\pca 10040\s132\arm5_no_packs>nrfjprog --program merge_image.hex Parsing hex file. Reading flash area to program to guarantee it is erased. Checking that the area to write is not protected. Programing device.

D:\project\VOX02_OLED\code\examples\ble_peripheral\nrf5-ble-tutorial-service\pca 10040\s132\arm5_no_packs>pause. why is there the difference? Our Factory plan to use the cmd group to program mass production. But now , it was hold.

RE: can't program bootloader code by nrfjprog tool

bjorn-spockeli — Tue, 06 Dec 2016 11:46:46 GMT

Could you try to recover the chip, i.e.

nrfjprog -f nrf52 --recover

and then try to program it?

RE: can't program bootloader code by nrfjprog tool

leif — Tue, 06 Dec 2016 10:54:39 GMT

usee the cmd according to your info .first erase the chip that is ok. but program it that still fail and report the same error. the info is as below:

1.erase is ok: D:\project\VOX02_OLED\code\examples\ble_peripheral\nrf5-ble-tutorial-service\pca 10040\s132\arm5_no_packs>nrfjprog -f nrf52 -e Erasing code and UICR flash areas. Applying system reset.

2.then program failed: Parsing hex file. Reading flash area to program to guarantee it is erased. 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.

RE: can't program bootloader code by nrfjprog tool

bjorn-spockeli — Tue, 06 Dec 2016 09:23:40 GMT

Could you try to first erase the erase the chip

nrfjprog -f nrf52 -e

and then flash the SoftDevice and the bootloader using

nrfjprog -f --program <name of hex file>.hex

RE: can't program bootloader code by nrfjprog tool

leif — Tue, 06 Dec 2016 01:05:48 GMT

sorry for reponsing it delayly .we use SEGGER J-Flash V5.12g. but I try to switch lasted version (i.e V6.12)that still failed.

RE: can't program bootloader code by nrfjprog tool

bjorn-spockeli — Fri, 02 Dec 2016 12:45:11 GMT

Which JLINK programmer are you using?