rtel wrote on Tuesday, January 16, 2018:
I have no idea how the plug-in is implemented I’m afraid, but I’m going
to guess it is because configUSE_PORT_OPTIMISED_TASK_SELECTION
is set to 1. When that is the case the priorities are stored as a bit
map so a single assembly instruction can be used to find the highest
priority. That can make the variable that holds the value have an
extremely large value if it is read as an integer rather than as a
bitmap. configUSE_PORT_OPTIMISED_TASK_SELECTION is set to 0?