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.

OMAP L138 or CCS suddenly stops working

Part Number: OMAP-L138

Hi,

I am developing on the OMAP L138 LCDK evaluation board and all the code in use is bare metal C.

Until last week everything was working fine. But now after some short time the processor jumps to strange addresses.

In the disassembly I can see that at such addresses either IDLE or NOP is written and therefore the processor gets stuck.

My setup:

  • Windows 10
  • XDS200 Debug Probe
    • TMSEMU200-U
    • Blackhawk
  • OMAP-L138 DSP+ARM9 Development Kit (LCDK)

What I obtained is, that I can step through the code for approximately two functions.

In my "Set Direction" function the values passed to it are totally different to the ones I have passed.

The problems I am facing are similar to the one described in this post: https://e2e.ti.com/support/tools/code-composer-studio-group/ccs/f/code-composer-studio-forum/114816/ccs-4-2-xds100-suddenly-stop-working . I also tried the suggested solutions - however nothing works.

I am really desperate at the moment as I am really do not know what to do.