I would think that adding the #define portTICK_TYPE_IS_ATOMIC 1 in the port’s macro.h for the cases where the tick type IS being defined to be a type that the processor will access atomically (single instruction Read/Write) should be safe. My guess is this port just predates that capability, so doesn’t advertise that fact.
richard-damon
(Richard Damon)
5
Related topics
| Topic | Replies | Views | Activity | |
|---|---|---|---|---|
| xTaskGetTickCount on 32bit is inefficient | 6 | 301 | May 28, 2009 | |
| xTaskGetTickCount during ISR | 1 | 192 | April 28, 2007 | |
| xTaskGetTickCount in tasks.c/h | 4 | 219 | December 11, 2007 | |
| portTickType xTaskGetTickCount( void ) | 1 | 158 | August 15, 2008 | |
| How to call xTaskGetTickCount(); from isr? | 7 | 279 | May 23, 2008 |