Interrupt configuration fails.

Hi Movas,

Thank you for your inquiry.

To verify timer interrupts, you can use a counter variable inside the timer callback function. If the timer is configured to trigger an interrupt every 1 ms, the counter should increment exactly 1000 times in one second. If this is not meeting your expectations, please clarify your requirements—specifically, how you intend to measure the timer behavior within the software callback.

Waiting for your reply.

Best Regards,
Santhakumari.V

Hi Santhakumari,

I understand the points you’ve raised regarding the verification process. However, measuring the interrupt for every 1ms has proven to be challenging. I have attempted to use the time.h clock module for this purpose, but it has not yielded the desired results.

To clarify, from the board’s perspective, we are successfully able to verify the interrupt every 1 millisecond. However, we now need to confirm whether the configuration is correctly applied from the callback function side. The code you provided is intended for continuous PWM mode with periodic interrupts, but we require assistance in verifying the functionality from within the callback function.

Could you kindly assist us in confirming the proper configuration on the callback function side as well?

Regards,
Movas

Hi Movas,

Callback function is mainly used to notify the user that a process has completed, based on some interrupt.

To verify the status of the GP timer in your software, you can use the software timer feature in FreeRTOS. Please refer to the attached file for more details. Here, the RTOS software timer is configured to invoke the handler function every 1ms, which sets a boolean flag to true. The GP timer callback function then checks this flag to verify the accuracy of the 1ms interval. However, apart from this check, only with inbuild software timing functions or cycle-based functions using inside the GP timer callback may not provide accurate timing measurements.

Best Regards,
Santhakumari.V

timer_code.zip