[SOLVED] J-Link commander cannot connect to i.MX6UL target

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

  • [SOLVED] J-Link commander cannot connect to i.MX6UL target

    Niklas,

    I bought J-Link edu several days ago and am now trying to
    bring up it with i.MX6Ul board. But until today I always get message:
    Cannot connect to target.

    What I did:
    -----------------------------------------------------------------------------------
    - according to the link wiki.segger.com/IMX6UL-EVK,
    I removed and assambled the mentioned resistors on i.MX6UL board
    - according to the link wiki.segger.com/IMX_Series_Devices,
    I set the device to MCIMX6G1

    What I get:
    -----------------------------------------------------------------------------------
    SEGGER J-Link Commander V6.22d (Compiled Dec 14 2017 18:33:22)
    DLL version V6.22d, compiled Dec 14 2017 18:32:44

    Connecting to J-Link via USB...O.K.
    Firmware: J-Link V10 compiled Dec 12 2017 16:37:47
    Hardware version: V10.10
    S/N: 260106884
    License(s): FlashBP, GDB
    OEM: SEGGER-EDU
    VTref = 3.303V

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

    Connecting to target via JTAG
    Could not measure total IR len. TDO is constant high.
    TotalIRLen = 13, IRPrint = 0x0101

    **************************
    WARNING: At least one of the connected devices is not JTAG compliant (IEEE Std 1
    149.1, 7.1.1.d, IR-cells). (NumDevices = 3, NumBitsSet = 2)
    **************************
    JTAG chain detection found 3 devices:
    #0 Id: 0x5BA00477, IRLen: 04, CoreSight JTAG-DP
    #1 Id: 0x00000001, IRLen: 05, Unknown device
    #2 Id: 0x0891D01D, IRLen: 04, JTAG-DP
    Scanning AP map to find all available APs
    AP[2]: Stopped AP scan as end of AP map seems to be reached
    AP[0]: AHB-AP (IDR: 0x74770001)
    AP[1]: APB-AP (IDR: 0x44770002)
    Iterating through AP map to find AHB-AP to use
    AP[0]: Skipped. Not an APB-AP
    AP[1]: APB-AP found
    Invalid ROM table component ID 0x2F0F0F02 @ 0x20001EF0 (expected 0xB105100D). Tr
    ying again at alternative offset.
    Invalid ROM table component ID 0x2F0F0F02 @ 0x60000FF0 (expected 0xB105100D). Tr
    ying again at alternative offset.
    TotalIRLen = 13, IRPrint = 0x0101
    **************************
    WARNING: At least one of the connected devices is not JTAG compliant (IEEE Std 1
    149.1, 7.1.1.d, IR-cells). (NumDevices = 3, NumBitsSet = 2)
    **************************
    JTAG chain detection found 3 devices:
    #0 Id: 0x5BA00477, IRLen: 04, CoreSight JTAG-DP
    #1 Id: 0x00000001, IRLen: 05, Unknown device
    #2 Id: 0x0891D01D, IRLen: 04, JTAG-DP
    ****** Error: Cortex-A/R-JTAG (connect): Could not determine address of core deb
    ug registers. Incorrect CoreSight ROM table in device?
    TotalIRLen = 13, IRPrint = 0x0101
    **************************
    WARNING: At least one of the connected devices is not JTAG compliant (IEEE Std 1
    149.1, 7.1.1.d, IR-cells). (NumDevices = 3, NumBitsSet = 2)
    **************************
    JTAG chain detection found 3 devices:
    #0 Id: 0x5BA00477, IRLen: 04, CoreSight JTAG-DP
    #1 Id: 0x00000001, IRLen: 05, Unknown device
    #2 Id: 0x0891D01D, IRLen: 04, JTAG-DP
    TotalIRLen = 13, IRPrint = 0x0101
    **************************
    WARNING: At least one of the connected devices is not JTAG compliant (IEEE Std 1
    149.1, 7.1.1.d, IR-cells). (NumDevices = 3, NumBitsSet = 2)
    **************************
    JTAG chain detection found 3 devices:
    #0 Id: 0x5BA00477, IRLen: 04, CoreSight JTAG-DP
    #1 Id: 0x00000001, IRLen: 05, Unknown device
    #2 Id: 0x0891D01D, IRLen: 04, JTAG-DP
    Cannot connect to target.
    J-Link>

    -----------------------------------------------------------------------------------
    I read this thread (segger2.com/index.php?page=Thread&threadID=3187),
    such issue should already be resolved sind Jan. 2017. So would you please help me to fix this issue?
    - which mistake I did?
    - How can I resolve it?
    thank you very much in the advance

    anton
  • Hello Anton,

    Thank you for your inquiry.

    Could you update your J-Link software package to the latest version?
    According to the release notes this issue has been fixed since V6.22e:

    DLL: Connecting to NXP i.MX6UL and i.MX6ULL series devices failed. Introduced with V6.22. Fixed.


    Best regards,
    Nino
    Please read the forum rules before posting.

    Keep in mind, this is *not* a support forum.
    Our engineers will try to answer your questions between their projects if possible but this can be delayed by longer periods of time.
    Should you be entitled to support you can contact us via our support system: segger.com/ticket/

    Or you can contact us via e-mail.
  • FYI: No need to use the beta version (V6.23a) but the latest release will also do (V6.22e) as it has been fixed there.

    However, glad to hear that you are up and running.


    Best regards
    Alex
    Please read the forum rules before posting.

    Keep in mind, this is *not* a support forum.
    Our engineers will try to answer your questions between their projects if possible but this can be delayed by longer periods of time.
    Should you be entitled to support you can contact us via our support system: segger.com/ticket/

    Or you can contact us via e-mail.