Skip to content

Conversation

@gerekon
Copy link

@gerekon gerekon commented Mar 26, 2025

This PR prepares TraceRecorder to be integrated into ESP registry. That allows IDF users to use it by specify component name in the project manifest files. For details see https://docs.espressif.com/projects/esp-idf/en/stable/esp32/api-guides/tools/idf-component-manager.html.

Having this merged you can upload component to ESP registry whenever new version is released.
In order to be able to upload component you need to register your namespace in ESP Registry. This PR implies that namespace is percepio and component name is tracerecorder. See https://docs.espressif.com/projects/idf-component-manager/en/latest/guides/packaging_components.html#publish-the-component.

Also you can publish new versions of the component automatically using GitHub actions. See https://docs.espressif.com/projects/idf-component-manager/en/latest/guides/packaging_components.html#upload-component-with-github-action

@@ -0,0 +1,148 @@
| Supported Targets | ESP32 | ESP32-C2 | ESP32-C3 | ESP32-C5 | ESP32-C6 | ESP32-C61 | ESP32-H2 | ESP32-H21 | ESP32-P4 | ESP32-S2 | ESP32-S3 |
| ----------------- | ----- | -------- | -------- | -------- | -------- | --------- | -------- | --------- | -------- | -------- | -------- |
# Example: Application Level Tracing - Percepio Tracealyzer Traces (tracealyzer)
Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Still need to update example docs

rsource "kernelports/FreeRTOS/config/Kconfig"
endif # PERCEPIO_TRC_CFG_RECORDER_RTOS_FREERTOS
# if PERCEPIO_TRC_CFG_RECORDER_RTOS_FREERTOS
# rsource "kernelports/FreeRTOS/config/Kconfig"
Copy link
Author

@gerekon gerekon Mar 26, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I had to comment this because sourced file re-defines PERCEPIO_TRC_CFG_RECORDER_RTOS_FREERTOS defined above and IDF build system complains on it.

What can we do with this? Was it done intentionally?

@gerekon gerekon force-pushed the esp_idf_comp_registry branch from 523246a to 0c7669a Compare March 26, 2025 16:10
@gerekon gerekon changed the title Draft: Integrate into ESP-IDF component registry Integrate into ESP-IDF component registry Mar 26, 2025
@erhankur
Copy link

Hi @eriktamlin, Could you please take a look at this and share your feedback? We’re happy to spend more time on it to get it merged.

@eriktamlin
Copy link
Member

Hi,
Sorry about the delay, we're working on a major update to the TraceRecorder so had to get some stuff down before integrating this.
This looks excellent!
I'm thinking we do an esp-idf branch so we can have the esp-idf specific files such as idf-component.yml and CMakeLists.txt without messing with any others.
Regarding the Kconfig in the root. I don't think that is used by anyone anymore so unless you explicitly need it (it looked like you mostly disabled it) I can just remove it instead.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants