Add minimal watchdog functionnalities to the H7 #23570
Open
+160
−0
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.
This add the functionnalities to use the independant watchdog of the H743 inside PX4 modules. This allow to reset the PX4 FMU CPU when there's a module that get stuck.
Solved Problem
I had an ongoing issue with a closed source module that was doing run-away CPU usage (using all the available CPU). By adding the independent watchdog to the H7, this allows me to configure the watchdog inside my module and if it starts behaving incorrectly, the watchdog will reset the board. I understand this is an improper solution, but it is valuable for us.
Fixes internal issue. But I've post in one of the Q&A session about it, please see: https://discuss.px4.io/t/px4-sync-q-a-july-10-2024/39614/2?u=ludovicvanasse
Solution
Changelog Entry
For release notes:
Alternatives
We could finding the bug inside my module (?) 🥲
Test coverage
Context
The forum post and the GIF gives a bit of context. But more than happy to provide more.