• State Verified Answer
  • Replies 12 replies
  • Answers 1 answer
  • Subscribers 75 subscribers
  • Views 3000 views
  • Users 0 members are here
Attachments (0)
Nordic Case Info
  • Case ID: 268740
Options
This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts

Error programming external nRF52 with Dev Kit: Could not fetch memory size of target devkit: Error: Error occured when get library info. Errorcode: CouldNotOpenDevice (0x4) Lowlevel error: Unknown value (ffffff24)

Noelle

I'm trying to program an nRF52 on a custom PCB using the nRF52-DK and am getting an error when connecting with nRF Connect v3.6.1.

I made the following connections from the P0.19 "Debug Out" header of my nRF52-DK to my PCB according to the guidelines.

DK Debug Out Custom PCB
VTG 3.3V

GND_DETECT

GND

 GND
SWDIO SWDIO
SWDCLK SWDCLK
SWO P0.18/TRACEDATA[0]/SWO
RESET RESET

The device appears in the list of available connections in nRF Connect as PCA10040 through a serial port, but gives the following error when selected:

Could not fetch memory size of target devkit: Error: Error occured when get library info. Errorcode: CouldNotOpenDevice (0x4) Lowlevel error: Unknown value (ffffff24)

I've confirmed power on the PCB is 3.3V and checked the programming header connections, so I'm not sure what could be the issue. Thanks in advance for any help.

Parents
  • 0

    Hi,

     

    I've confirmed power on the PCB is 3.3V and checked the programming header connections, so I'm not sure what could be the issue. Thanks in advance for any help.

    Try powering your external board from the nRF52-DK. This will ensure that the voltage is equal on both your custom board and the DK, as the DK does not have level shifters for debug out.

     

    What I usually do is that I program blinky on my DK, and then connect my external board and do a "nrfjprog -e".

    If the operation succeeds and DK stops blinking, I'm targeting the wrong device.

     

    Kind regards,

    Håkon 

  • 0 in reply to Håkon Alseth

    Hi,

    J-Link Commander is also unable to connect.

    Connecting to J-Link via USB...O.K.
    Firmware: J-Link V11 compiled Nov 12 2020 10:07:08
    Hardware version: V11.00
    S/N: 261011556
    License(s): FlashBP, GDB
    OEM: SEGGER-EDU
    VTref=3.303V

    Connecting to target via SWD
    InitTarget() start
    InitTarget() end
    Found SW-DP with ID 0x2BA01477
    Failed to power up DAP

    I've switched to a full J-Link programmer/debugger, so the 3.3V logic level should not be an issue.

    I am not sure what else to try at this point. Do you have any other suggestions?

    Noelle

Reply
  • 0 in reply to Håkon Alseth

    Hi,

    J-Link Commander is also unable to connect.

    Connecting to J-Link via USB...O.K.
    Firmware: J-Link V11 compiled Nov 12 2020 10:07:08
    Hardware version: V11.00
    S/N: 261011556
    License(s): FlashBP, GDB
    OEM: SEGGER-EDU
    VTref=3.303V

    Connecting to target via SWD
    InitTarget() start
    InitTarget() end
    Found SW-DP with ID 0x2BA01477
    Failed to power up DAP

    I've switched to a full J-Link programmer/debugger, so the 3.3V logic level should not be an issue.

    I am not sure what else to try at this point. Do you have any other suggestions?

    Noelle

Children
Related
Terms of service