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

"No idcode detected" error on PCA10056 V1.0.0

Hi,

During evaluation of both nRF52840 Dev Kit and Dongle somehow the Dev Kit bootloader was erased. We were able to flash MCU firmware, but now J-Link is not able to connect to the target device - reporting "No idcode detected". We tried both from Segger Studio on Mac, JLink Commander on Win10 and nrfjprog on both Windows and Mac.

"nrfjprog --recover" doesn't help.

It looks like nRF52840 bootloader was erased as well and now the target is not able to communicate with MCU/J-Link. Is there any way to fix it? For example, is it possible to install the target bootloader thru nRF52840 own USB?

Thanks,

Vitaly

  • Hi,

    Did you try to reflash the J-Link Interface MCU firmware? Hold the IF BOOT/RESET button while powering the board and drag the BIN file to the BOOTLOADER removable drive.

    Best regards,
    Jørgen

  • Hi,

    Yes, multiple times - both with "J-Link OB-SAM3U128-V2-NordicSemi 170724.bin" on the DK download page you mentioned and with newer one proposed by J-Link Tools - see J-Link commander output below:

    _____________________

    SEGGER J-Link Commander V6.40 (Compiled Oct 26 2018 15:06:29)
    DLL version V6.40, compiled Oct 26 2018 15:06:02
    Connecting to J-Link via USB...O.K.
    Firmware: J-Link OB-SAM3U128-V2-NordicSemi compiled Jul 12 2018 11:44:41
    Hardware version: V1.00
    S/N: 683029873
    VTref=3.300V

    Type "connect" to establish a target connection, '?' for help
    J-Link>connect
    Please specify device / core. <Default>: NRF52840_XXAA
    Type '?' for selection dialog Device>?
    Please specify target interface: J) JTAG (Default) S) SWD T) cJTAG
    TIF>S
    Specify target interface speed [kHz]. <Default>: 4000 kHz
    Speed>
    Device "NRF52840_XXAA" selected.
    Connecting to target via SWD
    Found SW-DP with ID 0x2BA01477
    Found SW-DP with ID 0x2BA01477
    Could not power-up debug power domain.
    Scanning AP map to find all available APs
    AP[0]: Stopped AP scan as end of AP map has been reached
    Iterating through AP map to find AHB-AP to use
    Found SW-DP with ID 0x2BA01477
    Found SW-DP with ID 0x2BA01477
    Scanning AP map to find all available APs
    AP[0]: Stopped AP scan as end of AP map seems to be reached
    Iterating through AP map to find AHB-AP to use

    ****** Error: Could not find core in Coresight setup
    Found SW-DP with ID 0x2BA01477
    Found SW-DP with ID 0x2BA01477
    Scanning AP map to find all available APs
    AP[0]: Stopped AP scan as end of AP map seems to be reached
    Iterating through AP map to find AHB-AP to use
    Found SW-DP with ID 0x2BA01477
    Found SW-DP with ID 0x2BA01477
    Scanning AP map to find all available APs
    AP[0]: Stopped AP scan as end of AP map seems to be reached
    Iterating through AP map to find AHB-AP to use
    Cannot connect to target.

    _____________________ 

    Thanks,

    Vitaly

  • Have you modified the DK in any way (for instance for current measurement)? What position are all the switches on the DK in?

  • As far as I know, no modifications. Developer burned some example intended for dongle.

    Switches:

    LiPo/VDD/USB - VDD

    nRF only/ default - default

    Are there any jumpers to check?

    Thanks!

  • Have you tried a different USB cable or flashing from another PC?

Related