fly316/PX4-Autopilot
7
0
Fork 0
mirror of https://gitee.com/mirrors_PX4/PX4-Autopilot.git synced 2026-10-21 05:33:35 +08:00
Code Issues Packages Projects Releases Wiki Activity

Add Niklas Debugging Video to GDB and hard fault sections (#24845)

Browse Source
This commit is contained in:
Hamish Willee
2025-05-14 17:52:59 +10:00
committed by GitHub
parent 79660d0a39
commit 3af9a3f76e
2 changed files with 32 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/en/debug/gdb_hardfault.md
+8 -1
View File
@@ -3,13 +3,20 @@
A hard fault is a state when a CPU executes an invalid instruction or accesses an invalid memory address.
This might occur when key areas in RAM have been corrupted.
## Video
## Videos
The following video demonstrates hardfault debugging on PX4 using Eclipse and a JTAG debugger.
It was presented at the PX4 Developer Conference 2019.
<lite-youtube videoid="KZkAM_PVOi0" title="Hardfault debugging on PX4"/>
---
The following video provides an overview of the tooling available for advanced debugging of PX4 via GDB (including hard fault debugging).
It was presented at the PX4 Developer Conference 2023.
<lite-youtube videoid="1c4TqEn3MZ0" title="Debugging PX4 - Niklas Hauser, Auterion AG"/>
## Debugging Hard Faults in NuttX
A typical scenario that can cause a hard fault is when the processor overwrites the stack and then the processor returns to an invalid address from the stack.