jrfarmer wrote on Thursday, November 14, 2013:
Richard, thanks for the reply.
does the ulTotalRunTime variable still hold the value of the total amount of time passed since the system booted (in whatever resolution the run time stats counter is using).
Yes, the ulTotalRunTime still holds the amount of time passed. The change is to allow this
32-bit ulTotalRunTime value to be updated from a 16-bit counter by treating ulTotalRunTime as an accumulator.
I did also make a suggestion to add an API to reset the stats (including the ulTotalRunTime). If the plug-ins can’t handle a reset of these statistics, they can just never call that API, but it could be handy to the rest of us.
preferable to keep port specifics (such as the number of bits in the timer) outside of the core kernel code.
Absolutely agree. This is why I suggest using a macro to enable the 16-bit support. This macro can be defined by the user in their FreeRTOSConfig.h file.
I haven’t explained that very well I know but hopefully it makes some kind of sense.
I’m very familiar with Cortex-M and its 24-bit SysTick clock, but I really did not follow this explanation. Is this functionality you describe included in one of the demo projects? I’d like to know more about it.