• State
  • Locked Locked
  • Replies 8 replies
  • Subscribers 31 subscribers
  • Views 346 views
  • Users 0 members are here
Support feedback
Options
Options
Related

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.

MSPM0L2228: Can no longer debug anything, call stack indicating 0xFFFFFFF8

Chris Tams
Prodigy 70 points
Part Number: MSPM0L2228

Tool/software:

I am using CCS 20.0.1 with the MSPM0L2228.

I upgraded from CCS Theia 1.5.1 to CCS 20.0.1 last week, and everything seemed to be working fine.

I did notice a firmware update of the XDS110 debug probe was done when I first ran CCS 20.0.1.

I have made some small code changes to my project, and now it is not possible to run that project, or any other I have ran over the previous two months.

Without altering any other project, they all result in the same problem, main is not reached, and the code ends up in the Default_Handler:

Reverting my recent changes back too, and still the same problem.

I have tried CCS Theia 1.5.1 again as well, and still the same problem.

I am at a bit of a loss as to what to try next, and just do not understand what has happened from working fine last week, no apparent changes since upgrading to CCS 20.0.1 and now cannot debug at all.

  • 0
    TI__Genius 14852 points

    Hi Chris,
    I recommend to do a DSSM Mass Erase and see if that fixes the issue.

    Best Regards,

    Diego Abad

  • 0 in reply to Diego Abad Sajamin
    Prodigy 70 points

    HI Diego,

    That does not work at all, and the same problem remains.

    This is the same on CCS 20.0.1 and CCS 1.5.1.

    Kind regards,

    Chris

  • 0 in reply to Chris Tams
    Prodigy 70 points

    Other things I have tried include:

    - Re-flashing the debug probe, with 3.0.0.32 and 30.0.0.33.

    - Re-installing Theia 1.5.1 and CCS 20.0.1

    - Trying SDK examples that were previously working.

    - Trying all branches from our own development that were known to be working and have not been altered in a few weeks.

  • 0 in reply to Chris Tams
    Prodigy 70 points

    I have just tried re-installing CCS Theia 1.5.1 after CCS 20.0.1, using CCS Theia, and debugging is working again!

    I was starting to suspect an issue with our board, but that is clearly not the case.

    Is there a known issue with debugging with CCS 20.0.1 and the XDS110 debug probe firmware 3.0.0.33?

    This has cost me a couple of days, and will be great to be able to move onto the later version of the tool chain to gain the improvements elsewhere in the IDE, and still be able to progress without hitting other blocking issues.

  • 0 in reply to Chris Tams
    TI__Genius 14852 points

    Hi Chris,
    Not that I'm aware of (I recently also installed the firmware in one launchpad, and it worked correctly). However, I'll let our team members know about this.
    Best Regards,
    Diego Abad

  • 0 in reply to Diego Abad Sajamin
    TI__Expert 4376 points

    Hi Chris,

    Checking with the SW dev team, this issue is not known.

    Could you confirm the steps you are going through in order to make the debugging work again ?

    1. Download CCS 20
    2. Download CCS 1.5.1
    3. Debug with 1.5.1 works again (but not with CCS 20)?

    Thank you.

    Best regards,

    Guillaume

  • 0 in reply to Guillaume Henri
    Prodigy 70 points

    Hi Guillaume,

    From a starting point of CCS Theia 1.5.1, and debug probe version 3.0.0.32, we have done the following:

    • Download and install CCS 20.0.1.
    • Build and attempt to debug with CCS 20.0.1, that flashed the debug probe to version 3.0.0.33.
    • Attempting a debug session, resulted in no code execution as previously shared, the stack trace always showing 0xFFFFFFF8.
    • Using CCS Theis 1.5.1 with debug probe version 3.0.0.33 still did not work.
    • Reverting the debug probe firmware to 3.0.0.32 still did not work.
    • Only a re-install of CCS Theia 1.5.1 used with debug probe firmware to 3.0.0.32 allowed us to debug again.

     

    Since then, debugging with CCS Theia 1.5.1 and debug probe firmware version 3.0.0.33 has been working too, suggesting the re-install changed something required to get it working.

     

    These steps were recently performed again with CCS 20.0.2 and debug probe version 3.0.0.35, and the same behaviour was observed in terms of not being able to start a debug session.

  • 0 in reply to Chris Tams
    TI__Genius 14852 points

    Hi Chris,
    We'll support this E2E internally.

    Best Regards,

    Diego Abad