Skip to content

GitLab

  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • F firmware
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 74
    • Issues 74
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 29
    • Merge requests 29
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Releases
  • External wiki
    • External wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • card10
  • firmware
  • Issues
  • #198

Closed
Open
Created May 21, 2020 by Rahix@rahixOwner

Add proper hardfaults handlers

Right now, we don't deal well with hardfaults:

  • Epicardium just becomes unresponsive and at some point the watchdog kicks in.
  • Pycardium epic_exit()s with ret-code 255 which will at least be logged to the console but no user feed-back nor a stacktrace either.
  • l0dables don't have any handling by default.

MR !79 (closed) has a basic implementation of a HardFault handler which could be repurposed for this in tandem with the new panic() functionality.

Edited Oct 05, 2020 by Rahix
Assignee
Assign to
Time tracking