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

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.

Parents
  • 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.

Reply
  • 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.

Children
No Data
Related