• State Resolved
  • Locked Locked
  • Replies 5 replies
  • Subscribers 54 subscribers
  • Views 1271 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

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.

CCS/TM4C1290NCPDT: TI-RTOS crashes when debugging with Segger J-Link

Nick W
Intellectual 280 points
Part Number: TM4C1290NCPDT
Other Parts Discussed in Thread: SEGGER

Tool/software: Code Composer Studio

Several of us in the TivaC forum are having trouble getting the TI-RTOS demos to work using a Segger J-Link. 

Please see this thread: e2e.ti.com/.../2379267

Basically, when using an XDS100v2 or the Stelaris ICDI, we are able to program and debug successfully, but with the J-Link, TI-RTOS crashes immediately after trying to start the first task with console output along the lines of this:

DFSR = 0x00000001
MMAR = 0xe000ed34
BFAR = 0xe000ed38
AFSR = 0x00000000
Terminating execution...

It was suggested to post on this forum since they haven't had much luck replicating the problem over in the other forum.

Can anyone shed some light on this or suggest a fix?

Thanks,

Nick

  • 0
    TI__Guru**** 161615 points
    Nick,

    I will try to setup the same environment to reproduce the problem. We may need to loop in the Segger team.

    I noticed that your CCS looks quite a bit different (icons, text...). What did you change?

    Regards,
    John
  • 0 in reply to JohnS
    Intellectual 280 points
    The icons and flat style are from the DevStyle eclipse plug-in.
  • 0 in reply to Nick W
    TI__Guru**** 161615 points
    Thanks. I hadn't see those flat icons before. I have used Themes but they don't usually change icons.

    I have setup CCSv7.2 on Windows, the 17.9 STS compiler that is used by the project and the same version of TI-RTOS. The onboard ICDI is working fine, as is an external XDS110. I can't get my JLink to connect at all, I may have an issue with my Segger software. I will loop in someone else with a working JLink.
  • 0
    TI__Guru**** 169894 points

    Nick,

    I found the same scenario as you, but I noticed the code is inheriting some pre-initialized hardware that corrupts its normal execution - in other words, the code requires the device to come from a clean reset to execute properly. 

    Please check the video below. When I first attempt to load code it fails with some error. I then disconnect the core, perform a HW reset (off screen) on the board and reconnect - the program is running normally. 

    I then close the debug session and retry. The error you mentioned is shown. I then disconnect --> HW Reset --> Reconnect and the code is fine. 

    After that I enable the option "Reset the target on a program load or restart" and subsequent code reloads work fine. 

    The differences between the Debug Probes may be due to the way this reset is handled. 

    Hope this helps,

    Rafael

  • 0 in reply to desouza
    Intellectual 280 points
    That did the trick! Thank you so much, I was pulling my hair out.