[ABANDONED] NXP iMX7 Solo jtag problem

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

  • [ABANDONED] NXP iMX7 Solo jtag problem

    Hi,

    Trying to connect to a board with a NXP iMX7 solo CPU using a j-link. In commander I write "connect" and choose unspecified Cortex-A7. The log is as follows (CPU cannot be halted):

    T1F4C 010:340 SEGGER J-Link V6.20f Log File (0004ms, 0023ms total)
    T1F4C 010:340 DLL Compiled: Oct 13 2017 17:18:41 (0004ms, 0023ms total)
    T1F4C 010:340 Logging started @ 2017-10-16 16:26 (0004ms, 0023ms total)
    T1F4C 013:204 JLINK_Api_MRU_GetList()C:\Program Files (x86)\SEGGER\JLink_V620f\JLinkDevices.xml evaluated successfully.
    T1F4C 030:483 JLINK_DEVICE_GetInfo(DeviceIndex = 4) returns 0 (0000ms, 0024ms total)
    T1F4C 030:484 JLINK_DEVICE_GetIndex(sDeviceName = Cortex-A7) returns 4 (0000ms, 0024ms total)
    T1F4C 030:484 JLINK_DEVICE_GetInfo(DeviceIndex = 4) returns 0 (0000ms, 0024ms total)
    T1F4C 033:364 JLINK_ConfigJTAG(IRPre = -1, DRPre = -1) (0002ms, 0026ms total)
    T1F4C 036:028 JLINK_ExecCommand("device=Cortex-A7", ...). Device "CORTEX-A7" selected. returns 0x00 (0003ms, 0029ms total)
    T1F4C 036:032 JLINK_SetSpeed(100) (0000ms, 0030ms total)
    T1F4C 036:032 JLINK_EnableLog(...) (0000ms, 0030ms total)
    T1F4C 036:032 JLINK_GetEmuCaps() returns 0xB9FF7BBF (0000ms, 0030ms total)
    T1F4C 036:032 JLINK_TIF_GetAvailable(...) (0000ms, 0030ms total)
    T1F4C 036:032 JLINK_TIF_Select(JLINKARM_TIF_JTAG) returns 0x00 (0001ms, 0031ms total)
    T1F4C 036:033 JLINK_Connect() >0x2F8 JTAG>TotalIRLen = 4, IRPrint = 0x01 >0x30 JTAG> >0x30 JTAG>JTAG chain detection found 1 devices: #0 Id: 0x5BA00477, IRLen: 04, CoreSight JTAG-DP >0x30 JTAG> >0x40 JTAG> >0x30 JTAG> >0x30 JTAG> >0x40 JTAG> >0x40 JTAG> >0x40 JTAG>ARM AP[0]: 0x64770001, AHB-AP >0x40 JTAG> >0x40 JTAG> >0x40 JTAG>ARM AP[1]: 0x44770002, APB-AP >0x78 JTAG> >0x40 JTAG> >0x40 JTAG> >0x40 JTAG> >0x40 JTAG> >0x30 JTAG> >0x30 JTAG> >0x30 JTAG> >0x30 JTAG> >0x30 JTAG> >0x30 JTAG> >0x40 JTAG>
    >0x40 JTAG> >0x30 JTAG> >0x30 JTAG> >0x40 JTAG> >0x40 JTAG> >0x40 JTAG> >0x30 JTAG> >0x30 JTAG> >0x30 JTAG> >0x30 JTAG> >0x30 JTAG> >0x30 JTAG> >0x40 JTAG> >0x40 JTAG> >0x30 JTAG> >0x30 JTAG> >0x30 JTAG> >0x30 JTAG> >0x30 JTAG> >0x30 JTAG> >0x30 JTAG> >0x30 JTAG> >0x30 JTAG> >0x30 JTAG>ROMTbl[0][0]: CompAddr: 80040000 CID: B105100D, PID:00-00080000 ROM Table >0x40 JTAG> >0x40 JTAG> >0x30 JTAG> >0x30 JTAG> >0x30 JTAG> >0x30 JTAG> >0x30 JTAG> >0x30 JTAG> >0x40 JTAG> >0x40 JTAG> >0x30 JTAG> >0x30 JTAG>
    >0x40 JTAG> >0x40 JTAG> >0x40 JTAG> >0x30 JTAG> >0x30 JTAG> >0x30 JTAG> >0x30 JTAG> >0x30 JTAG> >0x30 JTAG> >0x40 JTAG> >0x40 JTAG> >0x30 JTAG> >0x30 JTAG> >0x30 JTAG> >0x30 JTAG> >0x30 JTAG> >0x30 JTAG> >0x30 JTAG> >0x30 JTAG> >0x30 JTAG> >0x30 JTAG>ROMTbl[1][0]: CompAddr: 80041000 CID: B105900D, PID:04-002BB908 CSTF >0x40 JTAG> >0x40 JTAG> >0x30 JTAG> >0x30 JTAG> >0x40 JTAG> >0x40 JTAG> >0x40 JTAG> >0x30 JTAG> >0x30 JTAG> >0x30 JTAG> >0x30 JTAG> >0x30 JTAG> >0x30 JTAG> >0x40 JTAG> >0x40 JTAG>
    >0x30 JTAG> >0x30 JTAG> >0x30 JTAG> >0x30 JTAG> >0x30 JTAG> >0x30 JTAG> >0x30 JTAG> >0x30 JTAG> >0x30 JTAG> >0x30 JTAG>ROMTbl[1][1]: CompAddr: 80060000 CID: B105100D, PID:04-000BB4A7 ROM Table >0x40 JTAG> >0x40 JTAG> >0x30 JTAG> >0x30 JTAG> >0x30 JTAG> >0x30 JTAG> >0x30 JTAG> >0x30 JTAG> >0x40 JTAG> >0x40 JTAG> >0x30 JTAG> >0x30 JTAG> >0x40 JTAG> >0x40 JTAG> >0x40 JTAG> >0x30 JTAG> >0x30 JTAG> >0x30 JTAG> >0x30 JTAG> >0x30 JTAG> >0x30 JTAG> >0x40 JTAG> >0x40 JTAG> >0x30 JTAG> >0x30 JTAG> >0x30 JTAG>
    >0x30 JTAG> >0x30 JTAG> >0x30 JTAG> >0x30 JTAG> >0x30 JTAG> >0x30 JTAG> >0x30 JTAG>ROMTbl[2][0]: CompAddr: 80070000 CID: B105900D, PID:04-005BBC07 Cortex-A7 >0x40 JTAG> >0x40 JTAG> >0x30 JTAG> >0x30 JTAG> >0x40 JTAG>Found Cortex-A7 r0p56 code breakpoints, 4 data breakpointsDebug architecture ARMv7.1 >0x40 JTAG> >0x40 JTAG> >0x30 JTAG> >0x30 JTAG> >0x30 JTAG> >0x40 JTAG> >0x30 JTAG> >0x78 JTAG> >0x40 JTAG> >0x30 JTAG> >0x30 JTAG> >0x40 JTAG> >0x40 JTAG> >0x40 JTAG> >0x30 JTAG> >0x30 JTAG> >0x30 JTAG>
    >0x30 JTAG> >0x30 JTAG> >0x30 JTAG> >0x30 JTAG> >0x30 JTAG> >0x30 JTAG> >0x30 JTAG> >0x30 JTAG> >0x30 JTAG> >0x30 JTAG> >0x30 JTAG> >0x30 JTAG> >0x30 JTAG> >0x30 JTAG> >0x30 JTAG> >0x30 JTAG> >0x30 JTAG> >0x30 JTAG> >0x30 JTAG> >0x30 JTAG> >0x30 JTAG> >0x30 JTAG> >0x30 JTAG> >0x30 JTAG> >0x30 JTAG> >0x30 JTAG> >0x30 JTAG> >0x30 JTAG> >0x30 JTAG> >0x30 JTAG> >0x30 JTAG> >0x30 JTAG> >0x30 JTAG> >0x30 JTAG> >0x30 JTAG> >0x30 JTAG> >0x30 JTAG> >0x30 JTAG> >0x30 JTAG> >0x30 JTAG> >0x30 JTAG> >0x30 JTAG>
    >0x30 JTAG> >0x30 JTAG> >0x30 JTAG> >0x30 JTAG> >0x30 JTAG> >0x30 JTAG> >0x30 JTAG> >0x30 JTAG> >0x30 JTAG> >0x30 JTAG> >0x30 JTAG> >0x30 JTAG> >0x30 JTAG> >0x30 JTAG> >0x30 JTAG> >0x30 JTAG> >0x30 JTAG> >0x30 JTAG> >0x30 JTAG> >0x30 JTAG>
    ***** Error: Cortex-A/R (connect): Failed to temporarily halting CPU for reading CP15 registers. >0x2F8 JTAG>TotalIRLen = 4, IRPrint = 0x01 >0x30 JTAG> >0x30 JTAG>JTAG chain detection found 1 devices: #0 Id: 0x5BA00477, IRLen: 04, CoreSight JTAG-DP
    returns 0xFFFFFEFB (3250ms, 3281ms total)
    T1F4C 039:284 JLINK_GetIdData(...) >0x2F8 JTAG>TotalIRLen = 4, IRPrint = 0x01 >0x30 JTAG> >0x30 JTAG>JTAG chain detection found 1 devices: #0 Id: 0x5BA00477, IRLen: 04, CoreSight JTAG-DP >0x2F8 JTAG>TotalIRLen = 4, IRPrint = 0x01 >0x30 JTAG> >0x30 JTAG>JTAG chain detection found 1 devices: #0 Id: 0x5BA00477, IRLen: 04, CoreSight JTAG-DP (0089ms, 3370ms total)
    T1F4C 065:995 JLINK_IsOpen() returns 0x01 (0000ms, 3370ms total)
    T1F4C 066:010 JLINK_Close() (0011ms, 3381ms total)
    T1F4C 066:010 (0011ms, 3381ms total)
    T1F4C 066:010 Closed (0011ms, 3381ms total)
  • Hi,


    are you using an eval board or custom hardware?
    Which iMX7S device are you using? (e.g. MCIMX7S3, MCIMX7S5,....)

    Best regards,
    Niklas
    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.