[ABANDONED] Repeated Debugging in CCS Fails

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

  • [ABANDONED] Repeated Debugging in CCS Fails

    Hi All,

    I'm connecting my JLINK to a CC3220SF LaunchXL. The board is configured to use SWD debugging. I have a very basic FreeRTOS application based on the demos from TI that exhibits the following behavior:

    1) Starting the debugger the first time works.
    2) Starting the debugger the second time fails with the following info in the logs.

    Below I have the output in Code Composer Studio, below that the JLINK logs. Manually resetting the before debugging causes the problem not to happen. If I get this error and I hit debug again it works. Any idea how to get around this?

    Source Code

    1. Cortex_M4_0: GEL Output:
    2. Memory Map Initialization Complete
    3. Cortex_M4_0: Error: Stat [ JLINKARM_IsHalted() call ] failed!
    4. Cortex_M4_0: Trouble Halting Target CPU: Halt failed!
    5. Cortex_M4_0: Error: Stat [ JLINKARM_IsHalted() call ] failed!
    6. Cortex_M4_0: Unable to determine target status after 20 attempts
    The JLink Logs are attached.
    Files
  • Hi,
    Thank you for your inquiry.
    Such an issue is not known to us.

    The J-Link DLL version the Code composer studio uses is fairly old.
    Could you please update it and try again?
    How is explained here:
    wiki.segger.com/Generic_IDE#Updating_the_J-Link_DLL

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