Skip to content
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

Unable to combine COREDUMP_RTC_DATA_ATTR and RTC_NOINIT_ATTR (IDFGH-14676) #15420

Open
3 tasks done
ammaree opened this issue Feb 18, 2025 · 0 comments
Open
3 tasks done
Labels
Status: Opened Issue is new

Comments

@ammaree
Copy link

ammaree commented Feb 18, 2025

Answers checklist.

  • I have read the documentation ESP-IDF Programming Guide and the issue is not addressed there.
  • I have updated my IDF branch (master or release) to the latest version and checked that the issue is present there.
  • I have searched the issue tracker for a similar issue and not found a similar issue.

General issue report

We have been using RTC_NOINIT_ATTR successfully to preserve the contents of an STDOUT buffer in RTC slow RAM across reboots. This buffer allows us to view ESP_LOG messages generated just prior to a reboot or crash, or whilst a console was not connected, at a later stage.

We now would like to add this RTC slow RAM based STDOUT buffer to the COREDUMP image but cannot find a way to do this.

Since RTC_NOINIT_ATTR is primarily used during boot to disable the zero init of this memory area, and COREDUMP_RTC_DATA_ATTR is used at crash time to control memory area(s) included with the coredump info, theoretically we cannot see a reason why these 2 attributes cannot be combined.

Is there any way to achieve the effect of preserving the contents of this single memory block across reboots and also include it in coredumps?

@github-actions github-actions bot changed the title Unable to combine COREDUMP_RTC_DATA_ATTR and RTC_NOINIT_ATTR Unable to combine COREDUMP_RTC_DATA_ATTR and RTC_NOINIT_ATTR (IDFGH-14676) Feb 18, 2025
@espressif-bot espressif-bot added the Status: Opened Issue is new label Feb 18, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Status: Opened Issue is new
Projects
None yet
Development

No branches or pull requests

2 participants