This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts

nrfjprog program fail in JlinkARM.dll

Hi I'm using the Jlink to program nRF52832_XXAA, by using nRF command V9.0.0 nrfjprog I success in erase , but I can't program correctly,I tried Jlink version 5.12g and 6.10i in JlinkARM.dll version. Both can not work.

When I'm using the nRFgo Studio, also show the message: JlinkARM.dll can't find or use. Can anyone help? Thanks a lot

nrfjprog -s 600103256 -e --log
nrfjprog verion 9.0.0
--------------------------------------------------------------------------------
FUNCTION: open_dll.
FUNCTION: open_dll.
FUNCTION: enum_emu_snr.
FUNCTION: enum_emu_snr.
FUNCTION: enum_emu_snr.
FUNCTION: enum_emu_snr.
FUNCTION: connect_to_emu_with_snr.
FUNCTION: connect_to_emu_with_snr.
FUNCTION: connect_to_emu_without_snr.
FUNCTION: enum_emu_snr.
Device "NRF52832_XXAA" selected.
FUNCTION: read_device_version.
FUNCTION: read_device_version.
Found SWD-DP with ID 0x2BA01477
AP-IDR: 0x24770011, Type: AHB-AP
Found Cortex-M4 r0p1, Little endian.
FPUnit: 6 code (BP) slots and 2 literal slots
CoreSight components:
ROMTbl 0 @ E00FF000
ROMTbl 0 [0]: FFF0F000, CID: B105E00D, PID: 000BB00C SCS
ROMTbl 0 [1]: FFF02000, CID: B105E00D, PID: 003BB002 DWT
ROMTbl 0 [2]: FFF03000, CID: B105E00D, PID: 002BB003 FPB
ROMTbl 0 [3]: FFF01000, CID: B105E00D, PID: 003BB001 ITM
ROMTbl 0 [4]: FFF41000, CID: B105900D, PID: 000BB9A1 TPIU
ROMTbl 0 [5]: FFF42000, CID: B105900D, PID: 000BB925 ETM
FUNCTION: read_region_0_size_and_source.
FUNCTION: read_region_0_size_and_source.
FUNCTION: disable_bprot.
FUNCTION: disable_bprot.
FUNCTION: erase_all.
FUNCTION: erase_all.
FUNCTION: sys_reset.
FUNCTION: sys_reset.
FUNCTION: close_dll.
FUNCTION: close_dll.


nrfjprog -s 600103256 --program keyringForTest_v1.hex --log
nrfjprog verion 9.0.0
--------------------------------------------------------------------------------
FUNCTION: open_dll.
FUNCTION: open_dll.
FUNCTION: enum_emu_snr.
FUNCTION: enum_emu_snr.
FUNCTION: enum_emu_snr.
FUNCTION: enum_emu_snr.
FUNCTION: connect_to_emu_with_snr.
FUNCTION: connect_to_emu_with_snr.
FUNCTION: connect_to_emu_without_snr.
FUNCTION: enum_emu_snr.
Device "NRF52832_XXAA" selected.
FUNCTION: read_device_version.
FUNCTION: read_device_version.
Found SWD-DP with ID 0x2BA01477
AP-IDR: 0x24770011, Type: AHB-AP
Found Cortex-M4 r0p1, Little endian.
FPUnit: 6 code (BP) slots and 2 literal slots
CoreSight components:
ROMTbl 0 @ E00FF000
ROMTbl 0 [0]: FFF0F000, CID: B105E00D, PID: 000BB00C SCS
ROMTbl 0 [1]: FFF02000, CID: B105E00D, PID: 003BB002 DWT
ROMTbl 0 [2]: FFF03000, CID: B105E00D, PID: 002BB003 FPB
ROMTbl 0 [3]: FFF01000, CID: B105E00D, PID: 003BB001 ITM
ROMTbl 0 [4]: FFF41000, CID: B105900D, PID: 000BB9A1 TPIU
ROMTbl 0 [5]: FFF42000, CID: B105900D, PID: 000BB925 ETM
FUNCTION: readback_status.
FUNCTION: readback_status.
JLinkARM.dll CORESIGHT_WriteAPDPReg returned error -1.
JLinkARM.dll CORESIGHT_WriteAPDPReg returned error -102.
FUNCTION: close_dll.
FUNCTION: close_dll.
Parents
  • Right, sheesh, this was hard to track down.

    GPIO P0.21 (/RESET!) was going via an LED to VCC.

    In the makefiles (like most peoples) this is defined CONFIG_GPIO_AS_PINRESET for C and ASM for Bootloader AND Application

    This was causing it to get stuck in a state that I couldn't then access it as I configured that pin as an output to drive LED.

    Disconnected and left floating and no problem getting in with the debugger.

    Making the change to makefiles that should resolve.

Reply
  • Right, sheesh, this was hard to track down.

    GPIO P0.21 (/RESET!) was going via an LED to VCC.

    In the makefiles (like most peoples) this is defined CONFIG_GPIO_AS_PINRESET for C and ASM for Bootloader AND Application

    This was causing it to get stuck in a state that I couldn't then access it as I configured that pin as an output to drive LED.

    Disconnected and left floating and no problem getting in with the debugger.

    Making the change to makefiles that should resolve.

Children
No Data
Related