Skip to content

Record bounded crash and reset diagnostics #46

Description

@PurpleSentinel

Parent: #23

Summary

Retain enough information after an unexpected reset to identify failure stage and frequency without exhausting flash.

Acceptance criteria

  • Record reset cause, firmware version, last application state, and a concise error.
  • Use a bounded log with controlled write frequency.
  • Show the latest fault in diagnostics and expose it over USB.
  • Allow logs to be cleared deliberately.
  • Test malformed logs, repeated resets, and storage limits.

Roadmap group

Data, configuration, and maintenance

Activity

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

Metadata

Metadata

Assignees

No one assigned

    Labels

    NewFeatureCandidate product capability for future development

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions