[SOLVED] J-Link LITE can't connect to ADSP-CM408F EZ-KIT Lite

This site uses cookies. By continuing to browse this site, you are agreeing to our Cookie Policy.

  • [SOLVED] J-Link LITE can't connect to ADSP-CM408F EZ-KIT Lite

    Hello, my name is Zdravko,
    Lately i purchased ADSP-CM408F EZ-KIT Lite with J-Link LITE v8.2. After i plugged J-Link for first time, it asked me for firmware update.
    Here is the information after the firmware update:
    Firmware: J-Link ARM Lite V8 compiled Oct 29 2014 09:03:16
    Hardware: V8.00

    So, i started IAR Embedded Workbench and tried to debug and download to the processor with JTAG/SWD, but i always get these errors:

    *** SWD interface
    - Connecting via USB to J-Link device 0
    - Target interface speed: 2000 kHz (Fixed)
    - VTarget = 3.371V
    - ERROR: DAP error while reading AIRCR / CPUID register
    - ERROR: Failed to connect.
    Could not establish a connection to target.

    *** JTAG interface
    - Connecting via USB to J-Link device 0
    - Target interface speed: 2000 kHz (Fixed)
    - VTarget = 3.371V
    - ERROR: Bad JTAG communication: Write to IR: Expected 0x1, got 0x0 (TAP Command : 10) @ Off 0x5.
    Error while identifying Cortex-M device. Wrong AHB ID. Expected 0x04770001, found 0x00000000
    CM40x/CM41x connect: Can not find TAPC (IRLen mismatch)
    - ERROR: Failed to connect.
    Could not establish a connection to target.

    The processor on the kit is ADSP-CM408CSWZ-AF, the nearest model that i find in J-Link' s configuration settings is ADSP-CM408BSWZ-AF.
    The processor is ok and running with it's demo program, i checked the cable it's ok too. I downloaded the newest software from your site and i get the same error.
    Is it possible, if J-Link was with some special firmware for this kit and after it updated itself to the newest version it can't work ... or is some other problem?

    The post was edited 5 times, last by zdravko_bg ().

  • Hi,

    could you please give J-Link Commander a try?
    J-Link commander is part of the J-Link software package, which is available free of charge here .

    • Start J-Link Commander (jlink.exe)
    • Type "connect" in order to start a debug session
    • Type in the target device name if asked (Or type "?" for a target selection Dialog)
    • Choose the correct target interface (JTAG/SWD/etc..)
    • Use a valid speed (Default: 4000kHz, try 100-500 if default does not work)
    • [JTAG only]JTAG conf can be default(most of the times)
    • You should now be successfully connected.
    If anything fails, could you please post a screenshot of the complete session?

    Best regards,
    Niklas
    Would you like to be added to the J-Link software update notification list, so you get informed automatically when a new version becomes available?
    Just write me a PM or in case you want to subscribe to it yourself, please use this link: Link
    Notification for J-Link, J-Link Debugger, SystemView & J-Scope: Link
    Notification for Embedded Studio: Link
  • Thank you Niklas, i tried the commander but it still won't connect.

    Now i opened "UM08001_JLink.pdf" user guide and i see that the hardware of J-Link LITE v8.2 doesn't support Cortex-M4 core?
    Here is printscreen of the page:

    [img]http://i326.photobucket.com/albums/k426/koravei/UM08001_JLink_zps9u2nkxkm.png[/img]

    Please tell me if this is the reason for the problem, maybe i need board with upper hardware version?

    The post was edited 2 times, last by zdravko_bg ().

  • Hi,

    the table refers to the J-Link EDU / BASE / PLUS models.
    There is no respective table for the J-Link lite, as J-Link lite may only used with the eval board it ships with and therefore does not need a "generic" feature set.


    If it does not work with J-Link Commander, could you please provide a screenshot like mentioned in my previous post?
    Could you please also provide us with a J-Link logfile?

    Log output can be enabled like as follows:
    • Open a connection to J-Link, e.g start J-Link Commander
    • In J-Link Control Panel: (Click the J-Link symbol located in the notification / tray area in order to open J-Link Control panel)
    • Open the tab "Settings"
    • Next to the field "Log file" check "Override" and click "..." in order to choose a log file path.

    This is also described in UM8001 Chapter 5 "Working with J-Link and J-Trace", Section 5.7 "J-Link control panel" .

    Best regards,
    Niklas
    Would you like to be added to the J-Link software update notification list, so you get informed automatically when a new version becomes available?
    Just write me a PM or in case you want to subscribe to it yourself, please use this link: Link
    Notification for J-Link, J-Link Debugger, SystemView & J-Scope: Link
    Notification for Embedded Studio: Link
  • Here are the log files:

    JTAG: jlink_JTAG.txt
    SWD: jlink_SWD.txt

    Here is screenshot from session with JTAG:
    SEGGER J-Link Commander V6.12a (Compiled Dec 2 2016 16:44:55)
    DLL version V6.12a, compiled Dec 2 2016 16:44:26

    Connecting to J-Link via USB...O.K.
    Firmware: J-Link ARM Lite V8 compiled Oct 29 2014 09:03:16
    Hardware version: V8.00
    S/N: 228209475
    License(s): GDB
    VTref = 3.371V


    Type "connect" to establish a target connection, '?' for help
    J-Link>connect
    Please specify device / core. <Default>: ADSP-CM408BSWZ-AF
    Type '?' for selection dialog
    Device>?
    Please specify target interface:
    J) JTAG (Default)
    S) SWD
    TIF>jtag
    Device position in JTAG chain (IRPre,DRPre) <Default>: -1,-1 => Auto-detect
    JTAGConf>
    Specify target interface speed [kHz]. <Default>: 4000 kHz
    Speed>
    Device "ADSP-CM408BSWZ-AF" selected.


    TotalIRLen = 5, IRPrint = 0x01
    TotalIRLen = 9, IRPrint = 0x0011
    AP-IDR: 0x24770011, Type: AHB-AP
    Start searching for Cortex-M ROM table with ROMTable[0] @ 0xE00FF000.
    ROMTable[1]: Cortex-M ROM table found.
    TotalIRLen = ?, IRPrint = 0x..000000000000000000000000
    CM40x (connect): Device seems to be confused... performing recovery sequence.
    TotalIRLen = ?, IRPrint = 0x..000000000000000000000000

    ****** Error: Bad JTAG communication: Write to IR: Expected 0x1, got 0x0 (TAP Co
    mmand : 10) @ Off 0x5.
    Error while identifying Cortex-M device. Wrong AHB ID. Expected 0x04770001, foun
    d 0x00000000
    CM40x/CM41x connect: Can not find TAPC (IRLen mismatch)
    TotalIRLen = ?, IRPrint = 0x..000000000000000000000000
    CM40x (connect): Device seems to be confused... performing recovery sequence.
    TotalIRLen = ?, IRPrint = 0x..000000000000000000000000
    TotalIRLen = ?, IRPrint = 0x..000000000000000000000000
    CM40x (connect): Device seems to be confused... performing recovery sequence.
    TotalIRLen = ?, IRPrint = 0x..000000000000000000000000

    ****** Error: CM40x/CM41x connect: Can not find TAPC (IRLen mismatch)
    x0 (TAP Command : 10) @ Off 0x5.
    Error while identifying Cortex-M device. Wrong AHB ID. Expected 0x04770001, foun
    d 0x00000000
    CM40x/CM41x connect: Can not find TAPC (IRLen mismatch)
    Cannot connect to target.
    J-Link>

    Here is session with SWD:

    SEGGER J-Link Commander V6.12a (Compiled Dec 2 2016 16:44:55)
    DLL version V6.12a, compiled Dec 2 2016 16:44:26

    Connecting to J-Link via USB...O.K.
    Firmware: J-Link ARM Lite V8 compiled Oct 29 2014 09:03:16
    Hardware version: V8.00
    S/N: 228209475
    License(s): GDB
    VTref = 3.371V


    Type "connect" to establish a target connection, '?' for help
    J-Link>connect
    Please specify device / core. <Default>: ADSP-CM408BSWZ-AF
    Type '?' for selection dialog
    Device>?
    Please specify target interface:
    J) JTAG (Default)
    S) SWD
    TIF>swd
    Specify target interface speed [kHz]. <Default>: 4000 kHz
    Speed>
    Device "ADSP-CM408BSWZ-AF" selected.


    Found SWD-DP with ID 0x2BA01477
    AP-IDR: 0x24770011, Type: AHB-AP

    ****** Error: DAP error while reading AIRCR / CPUID register
    Cannot connect to target.
    J-Link>

    The post was edited 2 times, last by zdravko_bg ().

  • I found the problem, it's Analog Devices fault X( The CM408F Rev H chips have updated security features that can lock out the JTAG!

    Everyone who owns these Rev H chips needs ADSP-CM40x Enablement Package (Rev. 2.1.0) which can be downloaded from here:

    analog.com/en/design-center/ev…Z.html#eb-relatedsoftware

    Everything now works like a charm, sorry for your inconvenience.

    The post was edited 3 times, last by zdravko_bg ().

  • Hi,

    good to hear that you are up and running!

    Best regards,
    Niklas
    Would you like to be added to the J-Link software update notification list, so you get informed automatically when a new version becomes available?
    Just write me a PM or in case you want to subscribe to it yourself, please use this link: Link
    Notification for J-Link, J-Link Debugger, SystemView & J-Scope: Link
    Notification for Embedded Studio: Link