AWR2944: Regarding the timer interrupt issue on AWR2944

zhangshengbin

Part Number: AWR2944

Regarding the timer interrupt issue on AWR2944:

The RTI timer interrupts at 1ms, and when setting a breakpoint in the interrupt function and clearing the interrupt flag, the next timer interrupt fails to trigger properly.
Clearing bit 0 does not clear INT0, while other INTs are cleared.
When COS bit is set to 1, RTI continues running even during debug interruptions.

These issues have been observed across different versions of the SDK and MCAL. It's suspected that this may be due to a debug problem with XDS，but during normal production and use, there have also been occasional instances where the timer cannot function properly

Interrupt clearing is done step by step, and after that, the interrupt cannot be triggered again.

Please let me know if there is any additional information or assistance needed？

over 2 years ago

0 Saswat Kumar over 2 years ago

TI__Mastermind 35925 points

Hello zhangshengbin,

Are you observing this in the latest version of SDK 4.4.1.2?

Regards,
Saswat Kumar

0 zhangshengbin over 2 years ago in reply to Saswat Kumar

Prodigy 100 points

C:\ti\mmwave_mcuplus_sdk_04_04_01_02\mcu_plus_sdk_awr294x_09_00_00_15\examples\drivers\rti\rti_led_blink\awr294x-evm\r5fss0-0_nortos

SDK version 04040102

After hitting a breakpoint and then using the "Step Over" (F5) command followed by "Resume", the next interrupt fails to execute properly.

breakpoint ->Step Over ->Resume,Interrupt unable to enter

0 Saswat Kumar over 2 years ago in reply to zhangshengbin

TI__Mastermind 35925 points

Hello zhangshengbin,

Instead of stepping in, can you implement a counter in the interrupt handler to check whether you are observing the right value of count?
As you are debugging, it is possible there might be a drop in interrupt.
Counter is a better way to implement it and will help confirm if that is actually the case.

Regards,
Saswat Kumar

0 zhangshengbin over 2 years ago in reply to Saswat Kumar

Prodigy 100 points

I have tried using a counter for testing, and after the breakpoint stops, the counter will not continue to increase.

You can also use the software version of SDK to test, and I am using the demo described above.

0 Saswat Kumar over 2 years ago in reply to zhangshengbin

TI__Mastermind 35925 points

Hello zhangshengbin,

When you using the counter, can you not place a specific breakpoint, rather let it run and then halt the code and not via a breakpoint and check?

Regards,
Saswat Kumar

0 zhangshengbin over 2 years ago in reply to Saswat Kumar

Prodigy 100 points

Without the breakpoint , the counter will run normally. However, if an RTI interrupt occurs and the RTI interrupt is processing or during other interrupt processes (such as CAN reception interrupt), it will cause the RTI counter to no longer increase and os stop work.

0 Saswat Kumar over 2 years ago in reply to zhangshengbin

TI__Mastermind 35925 points

Hello zhangshengbin,

Is that behavior happening in your custom application?
Let me try your experiment which you are doing in the SDK on my end and get back to you with some update by end of this week.

Regards,
Saswat Kumar

0 Saswat Kumar over 2 years ago in reply to Saswat Kumar

TI__Mastermind 35925 points

Hello zhangshengbin,

I tried the same experiment, i set breakpoint at:

As you told I stepped over it, and then resumed.
It got stuck again and I did the same and I saw the led was turning on and then off again.
I tried another thing, where after it hit the breakpoint and I stepped over, I removed the breakpoint and ran it.
There also I saw the led blinking on and off.
I do not observe the behavior, that you have mentioned at all.

Regards,
Saswat Kumar

Sensors

Sensors forum

AWR2944: Regarding the timer interrupt issue on AWR2944