Unable to step debug C code generated using MATLAB 2019a embedded coder on F28379D launchpad

Question

Varun Betha 2022-2-7

0
链接

此问题的直接链接

https://ww2.mathworks.cn/matlabcentral/answers/1644760-unable-to-step-debug-c-code-generated-using-matlab-2019a-embedded-coder-on-f28379d-launchpad

回答： Asim 2023-11-17

I have generated C code using MATLAB Simulink Embedded coder to be used with Texas Instruments F28379D launchpad. I am able to generate the C code, open, edit and build using the CCS IDE v9.3.

Though the code runs as per the logic written in the interrupt service routine, if I introduce any breakpoint in the interrupt service routine and try to run it in the debug mode, it does not reach there.

Please let me know of any suggestions to solve this.

0 个评论
显示 -2更早的评论隐藏 -2更早的评论

请先登录，再进行评论。

请先登录，再回答此问题。

Answer 1

Asim 2023-11-17

0
链接

此回答的直接链接

https://ww2.mathworks.cn/matlabcentral/answers/1644760-unable-to-step-debug-c-code-generated-using-matlab-2019a-embedded-coder-on-f28379d-launchpad#answer_1354912

Hello Varun,

I understand that you're having difficulties with debugging your generated C code from MATLAB Simulink Embedded Coder on the Texas Instruments F28379D LaunchPad using CCS IDE v9.3. Specifically, breakpoints within the interrupt service routine (ISR) aren't being hit in debug mode.

Here are a few suggestions you might find helpful:

Clear the Interrupt Source: Before setting the breakpoint, ensure that the source of the interrupt has been cleared. Depending on whether the interrupt is level- or edge-triggered, it can affect whether the ISR is called continually or only once.
Check Interrupt Priority and Nesting Settings: Ensure that the priority of your interrupt is not set too low, and that interrupt nesting is enabled. If the interrupt priority is low, or if interrupt nesting is disabled, the ISR might not be executed when another higher-priority interrupt occurs.

I hope these instructions help you.

Best Regards,

Asim Asrar