Hi Team,
Is there any timer interrupt available for the radar firmware?
I found a watchdog timer, but besides that, are there any other methods available for generating timer interrupt inside radar firmware?
Warm Regards,
Balaji Sridhar
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.
Hi Team,
Is there any timer interrupt available for the radar firmware?
I found a watchdog timer, but besides that, are there any other methods available for generating timer interrupt inside radar firmware?
Warm Regards,
Balaji Sridhar
Hi,
You can generate timers via the RTOS. There is additional information in the following thread which should help you get started.
https://e2e.ti.com/support/sensors-group/sensors/f/sensors-forum/799512/awr1843-timers-configuration-using-rti-and-bios
Best Regards,
Alec
Hi Alec,
Thanks for the suggestion.
we created the timer interrupt as per the TI-RTOS user guide.
However, after creating the timer interrupt, we are having issues with object detection.c
Attached is the image for your reference.
Without a timer, we are not facing this issue.
Could you assist us in identifying the cause of the issue and finding a solution?
Modification:
Error:
Hi,
What processing is being done in your service handler function? I suspect that you may be spending too much time in this function, and not completing the radar chirp processing in time.
Best Regards,
Alec
Hi Balaji,
If you run this same code a few times, does it consistently break in the same location? Or does the location change? This could indicate that the issue is related to the exact timing of when your timer is triggering.
Best Regards,
Alec
Hi Alec
It keeps failing in the same place.
By including the CLI write log statement inside the service routine, we were able to confirm that the functionality of the timer interrupt was working.
However, if you give the "sensorStart" command, it fails with the same problem.
We are unable to determine why creating a timer causing this error.
I've attached the image for your reference.
Warm Regards,
Balaji Sridhar
Hi,
Can you try turning off code optimization in CCS, and see if the error behavior is the same? This can be changed in the project settings.
Best Regards,
Alec
Hi Alec,
This issue was resolved by initializing the timer after the MmwDemo_DPC_ObjectDetection_dpmTask task creation.
However, the run time error occurs when the MmwDemo_stopSensor API is invoked inside the service routine.
Please find the attached image for your reference.
If we follow the call-back table as per the attached image, it was failing inside the rlDriverCmdInvoke function in rl_driver.c
Could you kindly assist us in troubleshooting and resolving this problem?
Warm Regards,
Balaji Sridhar
Hi,
Glad to hear you were able to resolve the initial issue. In regards to the stop sensor call, I would warn against calling this function from the ISR, as you may be spending too much time in this function, and not servicing some of the other tasks or interrupts needed to properly stop the sensor. I expect that if you call the stopSensor from a different context (by posting a semaphore in the ISR) you will likely resolve your issue.
Best Regards,
Alec