Post Go back to editing

ADuCM410 dev kit cannot connect over SWD or flash via J-Link

Category: Hardware
Product Number: ADUCM410

I am unable to connect to the 'EVAL-ADuCM410QSP1Z' through 'J-Link', so I cannot flash or debug the device. The debugger detects the board and target voltage, but it does not attach to the core. The same behaviour occurs with both my current firmware project and a previously known-good ADuCM410 example.

Setup / steps to reproduce:

1. Connect the 'EVAL-ADuCM410QSP1Z' to a PC over USB.
2. Open 'Keil uVision', 'J-Link Commander', or 'J-Flash Lite'.
3. Select device 'ADUCM410' and interface 'SWD'.
4. Attempt to connect, flash, or start a debug session.

Observed result:
- The debugger detects the 'SW-DP' and target voltage at about '3.3 V'.
- It then fails to attach to the core.
- Reported errors include:
- 'Could not find core in Coresight setup'
- 'Failed to power up DAP'
- Flashing and debugging are not possible.

Additional detail:
I also tried a previously known-good ADuCM410 example project, and the same issue occurs.

Question:
Is there a recommended recovery or mass-erase procedure for the 'EVAL-ADuCM410QSP1Z' in this situation?

  • Hi Rishi,

    Did you get this problem solved? I have the exact same problem on a similar chip (ADuCM430).
    I tried to run J-Link commands to halt/erase the chip, connecting the ~RESET pin to the ground, but it keeps failing.

    Here is a script I wrote just to test if I could erase the chip:

    @echo off
    setlocal

    set JLINK_EXE="C:\Program Files\SEGGER\JLink\JLink.exe"
    set SCRIPT=%TEMP%\jlink_retry.jlink

    REM Write the command script once
    (
    echo si SWD
    echo speed 4000
    echo device ADuCM430
    echo r
    echo h
    echo q
    ) > "%SCRIPT%"

    for /L %%i in (1,1,100) do (
    echo --- attempt %%i ---
    %JLINK_EXE% -CommanderScript "%SCRIPT%"
    )

    endlocal

  • I've been using a mIDAS Link to program and debug M410s.  I was recently given a regular segger J-link and it refuses to connect to the M410 with the same cable harness.  I was wondering if anyone else has had luck using the plain vanilla J-link (not the AD version).  I did see something on the net about the Segger version needing some lines re-routed so that something like power shows up on the right pin.  

    Has anybody else run into this and/or solved it?

Before You Switch


Switching languages will make ADI Explorer unavailable. Resume your session by switching back to English and reopening ADI Explorer.