This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

  • TI Thinks Resolved

CCS/CCSTUDIO-TM4X: Another "CORTEX_M4_0: Error: Stat [ JLINKARM_IsHalted() call ] failed!" problem

Expert 2315 points

Replies: 18

Views: 2473

Part Number: CCSTUDIO-TM4X

Tool/software: Code Composer Studio

I have a similar problem as described in the thread at https://e2e.ti.com/support/development_tools/code_composer_studio/f/81/t/618900. That thread seems to be locked now, without any resolution being provided. I was wondering if anything was discovered regarding this issue.

I am running CCS 8.0.0.00016, using a Segger j-link plus. I am using the TI DK-TM4C129X dev kit.

Thanks,

Dave

  • Guru 144380 points

    In reply to Dave Hohl:

    Dave,  

    Between the start and end of the debug session, did you follow the procedure that throws the error? If so, the log should have much more information. We will need the help of Segger to try and identify what may be happening in your case.

    Just for reference, the log I captured follows attached. Line 95 is the one where the error is thrown.

    Regards,

    Rafael

    jlink_TM4C1294.rar


    When posting, click on the link Insert Code, Attach Files and more... to attach images, files or use nice formatting.

    If my reply answers your question please click on the green button "This resolved my issue".

  • In reply to desouza:

    I set the breakpoint and tried repeating many times, but I was not able to reproduce the error any more. My code has changed quite a bit since the initial report, so that might be affecting it. But problem with the RTOS-related code (reported in the related thread) is still occurring. It's just that I am not getting the J-Link error any longer when I try to run after the breakpoint.

    Regards,

    Dave
  • Guru 144380 points

    In reply to Dave Hohl:

    Dave,

    The issue in the related thread (mentioned in your first post) seems to be related to PLL changes and not RTOS changes. Perhaps I am missing yet another thread you posted?

    Regards,
    Rafael

    When posting, click on the link Insert Code, Attach Files and more... to attach images, files or use nice formatting.

    If my reply answers your question please click on the green button "This resolved my issue".

  • Guru 144380 points

    In reply to desouza:

    Dave,

    The lack of updates make me believe you got past the RTOS error you mentioned above. I will then close this thread but please feel free to reopen it if the issues are still happening.

    Regards,
    Rafael

    When posting, click on the link Insert Code, Attach Files and more... to attach images, files or use nice formatting.

    If my reply answers your question please click on the green button "This resolved my issue".

  • In reply to desouza:

    The post I linked to was seeing the problem when trying to set the PLL, but I was getting a similar error message when running after manually changing a register value while halted in RTOS code. There were two Segger-related issues -- not setting the CONTROL register correctly (detailed in a separate post) and the J-Link error message after manually changing the register. So far Segger has not responded to either issue as far as I can tell.
  • Guru 144380 points

    In reply to Dave Hohl:

    Dave,

    Thank you for reporting back; before I replied here I brought your threads again to their attention by directly writing to their support e-mail.

    I will monitor their responses and report back.

    I apologize for the inconvenience,
    Rafael

    When posting, click on the link Insert Code, Attach Files and more... to attach images, files or use nice formatting.

    If my reply answers your question please click on the green button "This resolved my issue".

  • Guru 144380 points

    In reply to desouza:

    Dave,

    I received a note from Segger that they were severely backed up but have your inquiries on their backlog.

    Also, they confirmed it is preferred to contact them directly so they have better monitoring capabilities.

    Regards,
    Rafael

    When posting, click on the link Insert Code, Attach Files and more... to attach images, files or use nice formatting.

    If my reply answers your question please click on the green button "This resolved my issue".

  • In reply to desouza:

    Thanks for the update, Rafael.

This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.