Repository navigation
Add L552 stack-corruption trace demo and source reports - #5
Merged
Merged
Conversation
thorstendb-ARM
marked this pull request as ready for review
October 8, 2026 12:23
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Add the
ULINKplus StackCorruptiontarget set for NUCLEO-L552ZE-Q. It creates an additional thread that deliberately overwrites the magic word of its 256-byte RTX stack. A single DWT write watch emits the responsible PC over SWO; the normal debug start/stop workflow writes the capture and converts it to CSV. Other demo trace sources are disabled.Add the Trace Stack Magic corruption test skill to verify the trace setup, run a capture, resolve PCs with
arm-none-eabi-addr2line, and open a Markdown report with one section per CSV record. Each section contains source code, a project-relative location, and a source-based explanation. A report-only mode analyzes an existing CSV without a build or debug session. The CSV stays unchanged; no capture archives or sidecar files are created.Validation:
docs/VALIDATION.mdfrom 2026-10-05 confirmed stack-magic corruption, RTX detection, and uninterrupted SWO capture with PC resolution. These are prior results; no new firmware build or hardware run was performed for this PR update.Known limitation: breakpoints near the corrupting store can lose its PC packet. The automated capture runs uninterrupted through the write before stopping.