-
Notifications
You must be signed in to change notification settings - Fork 7.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
FreeRTOS Runtime Counter support. (IDFGH-12057) #13120
Comments
Hello @ammaree , Thank you for noticing this, we are going to look into this and fix it |
@o-marshmallow In components/freertos/esp_additions/freertos_tasks_c_additions.h:
in components/freertos/FreeRTOS-Kernel/portable/xtensa/include/freertos/portmacro.h:
Have tested this fix over last week on many different hardware platforms, works 100% Maybe possible to get the fix through ASAP... |
+99 for fixing this, only requires the 2 lines above to restore proper functioning. Please |
Hi @ammaree! |
Answers checklist.
IDF version.
v5.3-dev-1922-g5454d37d49
Espressif SoC revision.
All ESP32 I believe
Operating System used.
macOS
How did you build your project?
VS Code IDE
If you are using Windows, please specify command line type.
None
Development Kit.
N/A
Power Supply used.
USB
What is the expected behavior?
Valid useable runtime information being returned.
What is the actual behavior?
Runtime counter support is inconsistent and largely invalid.
Steps to reproduce.
https://vscode.dev/github/espressif/esp-idf/blob/master/components/freertos/esp_additions/freertos_tasks_c_additions.h#L488
Should be using 'configRUN_TIME_COUNTER_TYPE' to support both u32_t and u64_t
https://vscode.dev/github/espressif/esp-idf/blob/master/components/freertos/FreeRTOS-Kernel/portable/xtensa/include/freertos/portmacro.h#L521-L522
We are using a 32 bit data source (with 12.5nSec resolution here) so the value will wrap every minute?
https://vscode.dev/github/espressif/esp-idf/blob/master/components/freertos/FreeRTOS-Kernel/portable/xtensa/include/freertos/portmacro.h#L523
We are using an int64_t data source (already not ideal, u64_t preferred) and then casting it to a uint32_t?
It is quite possible that there are more locations where configRUN_TIME_COUNTER_TYPE is not used, or where the source data is not valid.
Debug Logs.
No response
More Information.
No response
The text was updated successfully, but these errors were encountered: