FreeRTOS Support Archive
The FreeRTOS support forum is used to obtain active support directly from Real
Time Engineers Ltd. In return for using our top quality software and services for
free, we request you play fair and do your bit to help others too! Sign up
to receive notifications of new support topics then help where you can.
This is a read only archive of threads posted to the FreeRTOS support forum.
The archive is updated every week, so will not always contain the very latest posts.
Use these archive pages to search previous posts. Use the Live FreeRTOS Forum
link to reply to a post, or start a new support thread.
[FreeRTOS Home] [Live FreeRTOS Forum] [FAQ] [Archive Top] [January 2012 Threads] Run-time stats and interruptsPosted by Matthew Kendall on January 30, 2012 I am using FreeRTOS on an NXP LPC1769. I have enabled run-time stats as detailed in the manual. I can successfully get stats for all my tasks.
It seems to me that time spent in interrupts is counted towards the task that happens to be interrupted. Is there a straightforward way to get time spent in interrupts listed separately in the stats? I would like to confirm that my interrupt-driven I/O (buffered serial ports) is not consuming excessive CPU time.
RE: Run-time stats and interruptsPosted by Richard Damon on January 30, 2012 The limitation is that, in general, FreeRTOS doesn't know when an interrupt occurs. If there is one interrupt in particular that you are interested in, you can add code at the beginning of it to read the high speed timer, and then read it again at the end, take the difference and accumulate it. Note that the end point may need to be just before the interrupt routine reactivates the new task if that operation doesn't return to the ISR. (I am not familiar with this port and how it handles this operation).
This won't affect the stats from the run-time stats, but will give you a measure of those interrupts so instrumented.
Copyright (C) Amazon Web Services, Inc. or its affiliates. All rights reserved.
|