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
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?
The text was updated successfully, but these errors were encountered:
github-actionsbot
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
Answers checklist.
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?
The text was updated successfully, but these errors were encountered: