TMS320F28388D: Questions about MDEBUGSTOP and MDEBUGSTOP1

Ben Qin

Intellectual 2690 points

Part Number: TMS320F28388D

Hi Team,

There are two issues from the customer need your help:

There are two descriptions of the CLA debug breakpoint settings in the 388TRM document

MDEBUGSTOP1 clears the pipeline (flush)

MDEBUGSTOP is an older version of how breakpoints are set

But I see that the 388 routine does not use the new MDEBUGSTOP1 breakpoint setting method, but the MDEBUGSTOP is used instead

And changing to MDEBUGSTOP1 compilation will get an error

Question 1. How should the MDEBUGSTOP1 mentioned in 388TRM be used

以下是F2803x_DEV_USER_GUIDE.pdf的内容，问题也一并发达这个帖子里

Question 2. TBCTL is not an EALLOW-protected register, and why use __meallow and __medis for this example

Could you help check this case? Thanks.

Best Regards,

Ben

over 2 years ago

0 Veena Kamath over 2 years ago

TI__Mastermind 32565 points

MDEBUGSTOP1 is used by the CCS tool to insert breakpoints at run time. This cannot be inserted in the code

Ben Qin said:
Question 2. TBCTL is not an EALLOW-protected register, and why use __meallow and __medis for this example

We will check this issue and get it removed

Regards,

Veena

0 Ben Qin over 2 years ago in reply to Veena Kamath

TI__Intellectual 2690 points

Hi Veena,

Thanks for the help.

Veena Kamath said:
MDEBUGSTOP1 is used by the CCS tool to insert breakpoints at run time. This cannot be inserted in the code

Could you explain how it works?

How does CCS use MDEBUGSTOP1?

Is this MDEBUGSTOP1 a tool or something?

Or type 2 of CLA, when debugging, is so called

There is currently only a 379D LaunchPad on hand

I only debugged the CLA of 035 and 379

Thanks & Regards,

Ben

+1 Veena Kamath over 2 years ago in reply to Ben Qin

TI__Mastermind 32565 points

At run time, when you add a breakpoint, CCS replaces that instruction wit the MDEBUGSTOP1 instruction. I believe this feature is not present in Type1 CLA which is present in F2837x device.