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

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

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

    Hello,

    I just started i.MX6ULL development using J-Link PLUS Compact and IMX6ULLEVK board.
    But I cannot connect to target.

    According to the link https://wiki.segger.com/IMX6ULL-EVK,

    I removed the mentioned resistors on IMX6ULLEVK board.
    J-link commander runs on Windows10 64bit.

    The commander's log :
    ----------------------------------------------------------------------------------------------
    SEGGER J-Link Commander V6.30d (Compiled Feb 16 2018 13:30:47)
    DLL version V6.30d, compiled Feb 16 2018 13:30:32

    Connecting to J-Link via USB...O.K.
    Firmware: J-Link V10 compiled Feb 16 2018 13:03:54
    Hardware version: V10.10
    S/N: 850100110
    License(s): RDI, FlashBP, FlashDL, JFlash, GDB
    VTref = 3.322V


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


    Connecting to target via JTAG
    TotalIRLen = 13, IRPrint = 0x0101

    **************************
    WARNING: At least one of the connected devices is not JTAG compliant (IEEE Std 1149.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: 0x088C101D, 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). Trying again at alternative offset.
    Invalid ROM table component ID 0x2F0F0F02 @ 0x60000FF0 (expected 0xB105100D). Trying again at alternative offset.
    TotalIRLen = 13, IRPrint = 0x0101

    **************************
    WARNING: At least one of the connected devices is not JTAG compliant (IEEE Std 1149.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: 0x088C101D, IRLen: 04, JTAG-DP

    ****** Error: Cortex-A/R-JTAG (connect): Could not determine address of core debug 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 1149.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: 0x088C101D, IRLen: 04, JTAG-DP
    TotalIRLen = 13, IRPrint = 0x0101

    **************************
    WARNING: At least one of the connected devices is not JTAG compliant (IEEE Std 1149.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: 0x088C101D, IRLen: 04, JTAG-DP
    Cannot connect to target.
    J-Link>

    ----------------------------------------------------------------------------------------------------------------------------
    I've read the similar thread.
    [SOLVED] J-Link commander cannot connect to i.MX6UL target
    I'm using newer version software package, but encountered similar phenomenon.

    Would you please advice me the solution.
    Thank you very much in advance.

    Keishi

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

  • Hello Keishi,

    Thank you for your inquiry.

    You need to specify the exact device name.
    Currently you are trying to connect to a generic Cortex-A7 device which will not work.
    When Commander asks you for the device name you can either type "?" to get a list of supported devices or write it directly.
    The correct device names for imx devices can be found here: wiki.segger.com/IMX_Series_Devices

    Best regards,
    Nino
    Please read the forum rules before posting: Forum Rules

    Keep in mind, this is not a support forum. Its main purpose is user to user interaction.
    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.
  • Hello Keishi,

    Great to hear that you are up and running again.
    We will consider this case as closed now.

    Best regards,
    Nino
    Please read the forum rules before posting: Forum Rules

    Keep in mind, this is not a support forum. Its main purpose is user to user interaction.
    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.