• State TI Thinks Resolved
  • Locked Locked
  • Replies 2 replies
  • Answers 1 answer
  • Subscribers 31 subscribers
  • Views 232 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.

MSPM0G3507-Q1: MCAL: When using the MCAL library of MSPM0G3507, user find that he can not access and set the breakpoint in some providied code functions

Sal Ye
Mastermind 18915 points
Part Number: MSPM0G3507-Q1
Other Parts Discussed in Thread: MSPM0G3507

Tool/software:

Hi experts,

There is the cusomter who are evaluating the MCAL for MSPM0G3507, below is the issues they find in debug mode. [They use the default EB config and do the library test.]

Software environment: CCS 12.6 / mspm0_sdk_1_30_00_03 / MCAL version 0.1.2.0 / ti-cgt-armllvm_2.1.3.LTS and ti-cgt-armllvm_3.2.1.LTS / optimization level : 0

Phenomenon:

When debugging G3507 CAN-FD, it was found that some functions defined in Can_Mcan.c could not be stepped into or breakpointed, for example: Can_mcanProcessISR, Can_mcanReadRxFIFO and Can_mcanProcessTx. [Customer defined their own test project].

These functions were not included in the static library, and with given source code in the software library. Even if the inline keyword was added to these functions, they still could not be stepped into or breakpointed.

If you use __BKPT(0); to set breakpoints in these functions, the source code window of CCS will become like this when it is paused:

Even if customer set the breakpoint in the Disassembly window, it shows the same.

This is not user-friendly. Is this expected? If not, is there any solution?

  • 0
    TI__Prodigy 10 points

    Hey Sal,

    I have seen the above issue with the compiler version: ti-cgt-armllvm_2.1.3.LTS

    Using the latest compiler versions: ti-cgt-armllvm_3.2.2.LTS or ti-cgt-armllvm_3.2.1.LTS
    I don't see the above issue.
    I am able to debug the functions defined in Can_Mcan.c.


    Can you try to build the MCAL example as it is with the above mentioned compiler version and try at your end?

    Do let us know if the above helps.

    Thanks!

  • 0 in reply to Akshat Aggarwal
    Prodigy 10 points

    Hi Akshat,

    In our project, even with the latest version of the compiler, the problem still occurs. However, once the optimization level of the project was changed to s, some of the functions in Can_Mcan.c could be debugged.