You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
configGENERATE_RUN_TIME_STATS + configUSE_STATS_FORMATTING_FUNCTIONS + INCLUDE_xTaskGetIdleTaskHandle must all be enabled for these functions to be available. However there is no obvious way to enable INCLUDE_xTaskGetIdleTaskHandle
The text was updated successfully, but these errors were encountered:
github-actionsbot
changed the title
uxTaskGetSystemState example in latest docs with IDF 5.1.2 does not compile
uxTaskGetSystemState example in latest docs with IDF 5.1.2 does not compile (IDFGH-11707)
Dec 16, 2023
configRUN_TIME_COUNTER_TYPE was only introduced recently, so the new example won't work as is with an older version of IDF. In general, try the examples bundled with the version of IDF you are using.
(Github also labels the most recent stable release as "Latest" on the release page, the Readthedocs docs URL for the latest stable release is https://docs.espressif.com/projects/esp-idf/en/stable/ — which at the time of writing points to 5.1.2 docs.)
Answers checklist.
General issue report
https://docs.espressif.com/projects/esp-idf/en/latest/esp32/api-reference/system/freertos_idf.html#_CPPv420uxTaskGetSystemStatePC12TaskStatus_tK11UBaseType_tPC27configRUN_TIME_COUNTER_TYPE
Code given in the above link results in a compile error even when
configUSE_TRACE_FACILITY
is enablederror: unknown type name 'configRUN_TIME_COUNTER_TYPE'
Adding
configGENERATE_RUN_TIME_STATS
does not change the compile error eitherAccording to https://docs.espressif.com/projects/esp-idf/en/latest/esp32/api-reference/system/freertos_idf.html#_CPPv427ulTaskGetIdleRunTimeCounterv
configGENERATE_RUN_TIME_STATS
+configUSE_STATS_FORMATTING_FUNCTIONS
+INCLUDE_xTaskGetIdleTaskHandle
must all be enabled for these functions to be available. However there is no obvious way to enableINCLUDE_xTaskGetIdleTaskHandle
The text was updated successfully, but these errors were encountered: