[SOLVED] CCS/TMS570LS0714: Error: Stat [ JLINKARM_IsHalted() call ] failed!

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

  • [SOLVED] CCS/TMS570LS0714: Error: Stat [ JLINKARM_IsHalted() call ] failed!

    Hi!

    I have a custom board with a TMS570LS0714 that was put together for the first time. I'm trying to upload code to it using the J-Link EDU via Code Composer Studio's J-Link integration, but it seems there's a problem with the connection.

    Platform: Arch Linux x86_64
    Kernel: 4.14.13-1-ARCH
    Code Composer Studio: 7.4.0.00015
    Code Composer Studio J-Link Support: 6.20.9.0
    Segger product: J-Link EDU
    MCU: TMS570LS0714

    Output from Code Composer Studio's console (within the IDE)

    Source Code

    1. CortexR4: Error: Stat [ JLINKARM_IsHalted() call ] failed!
    2. CortexR4: Unable to determine target status after 20 attempts
    3. CortexR4: GEL Output: Memory Map Setup for Flash @ Address 0x0


    stdout from ~/ti/ccsv7/eclipse/ccstudio (lots of these)

    Source Code

    1. *** J-Link V6.20i Executing PCode ***
    2. Can not find ICE-Pick (IRLen mismatch). Expected 0x00000006, found: 0x00000280
    3. *** J-Link V6.20i Executing PCode ***
    7. *** J-Link V6.20i Executing PCode ***
    8. Can not find ICE-Pick (IDCODE mismatch). Expected 0xXXXXXX2F, found: 0x00000000
    9. *** J-Link V6.20i Executing PCode ***
    13. *** J-Link V6.20i Executing PCode ***
    14. Can not find ICE-Pick (IRLen mismatch). Expected 0x00000006, found: 0x00000280
    15. *** J-Link V6.20i Executing PCode ***
    19. *** J-Link V6.20i Executing PCode ***
    20. Can not find ICE-Pick (IDCODE mismatch). Expected 0xXXXXXX2F, found: 0x00000000
    21. *** J-Link V6.20i Executing PCode ***
    Display All


    Also tried connecting with the official standalone binaries.

    Output from JLinkExe

    Source Code

    1. $ ./JLink_Linux_V622e_x86_64/JLinkExe
    2. SEGGER J-Link Commander V6.22a (Compiled Nov 28 2017 17:57:05)
    3. DLL version V6.22a, compiled Nov 28 2017 17:57:00
    5. Connecting to J-Link via USB...O.K.
    6. Firmware: J-Link V9 compiled Dec 1 2017 14:40:21
    7. Hardware version: V9.30
    8. S/N: 269304666
    9. License(s): FlashBP, GDB
    10. OEM: SEGGER-EDU
    11. VTref = 0.000V
    13. ...
    15. J-Link>connect
    16. Please specify device / core. <Default>: TMS570LS0714
    17. Type '?' for selection dialog
    18. Device>TMS570LS0714
    19. Device "TMS570LS0714" selected.
    22. Connecting to target via JTAG
    23. Executing InitTarget()
    24. TotalIRLen = ?, IRPrint = 0x..000000000000000000000000
    25. 0x00000280
    26. J-Link script: ICEPick found, enabling Cortex-M3 core.
    27. Can not find ICE-Pick (IDCODE mismatch). Expected 0x0000002F, found: 0x00000000
    28. TMS570/RM4x (connect): Can not find Cortex-M3 (IDCODE mismatch)
    29. Executing InitTarget()
    30. TotalIRLen = ?, IRPrint = 0x..000000000000000000000000
    31. 0x00000280
    32. J-Link script: ICEPick found, enabling Cortex-M3 core.
    33. Can not find ICE-Pick (IDCODE mismatch). Expected 0x0000002F, found: 0xA0002108
    34. TMS570/RM4x (connect): Can not find Cortex-M3 (IDCODE mismatch)
    36. ****** Error: InitTarget(): PCode returned with error code -1
    38. Executing InitTarget()
    39. TotalIRLen = ?, IRPrint = 0x..000000000000000000000000
    40. 0x00000280
    41. J-Link script: ICEPick found, enabling Cortex-M3 core.
    42. Can not find ICE-Pick (IDCODE mismatch). Expected 0x0000002F, found: 0xA0002108
    43. TMS570/RM4x (connect): Can not find Cortex-M3 (IDCODE mismatch)
    44. Executing InitTarget()
    45. TotalIRLen = ?, IRPrint = 0x..000000000000000000000000
    46. 0x00000280
    47. J-Link script: ICEPick found, enabling Cortex-M3 core.
    48. Can not find ICE-Pick (IDCODE mismatch). Expected 0x0000002F, found: 0xA0002108
    49. TMS570/RM4x (connect): Can not find Cortex-M3 (IDCODE mismatch)
    51. ****** Error: InitTarget(): PCode returned with error code -1
    53. Cannot connect to target.
    Display All


    Any tips on what to check?

    We've also created a corresponding thread on TI's forum: e2e.ti.com/support/development…oser_studio/f/81/t/619076

    Thanks.

  • Hello,

    Thank you for your inquiry.
    Such an issue is not known to us.

    From the logs it reads: VTref = 0.000V

    This indicates that Pin 1 of the J-Link interface is not connected to the target voltage supply correctly.
    More information can be found here: wiki.segger.com/J-Link_cannot_…o_the_CPU#VTref_is_0.000V

    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.