summaryrefslogtreecommitdiff
path: root/pelican/content/DisasterRecovery.md
diff options
context:
space:
mode:
authorRob Austein <sra@hactrn.net>2021-02-15 22:29:56 +0000
committerRob Austein <sra@hactrn.net>2021-02-15 22:29:56 +0000
commit18fb1695b84248fc75ceb3569ff03cbeca51a620 (patch)
tree74e8c1473c11ca8db6f942d52acd5743c3e4d17c /pelican/content/DisasterRecovery.md
parentdd255ef58a617214ea3ece613c417af1fc1549ec (diff)
Seriously rework link processing
Diffstat (limited to 'pelican/content/DisasterRecovery.md')
-rw-r--r--pelican/content/DisasterRecovery.md4
1 files changed, 2 insertions, 2 deletions
diff --git a/pelican/content/DisasterRecovery.md b/pelican/content/DisasterRecovery.md
index 1c2ba6f..2fae666 100644
--- a/pelican/content/DisasterRecovery.md
+++ b/pelican/content/DisasterRecovery.md
@@ -22,7 +22,7 @@ PIN: <your-wheel-pin>
### Recovering from a bad bootloader install
Well, now you've done it. You'll need to buy an ST-LINK programmer.
-See [UsingSTLink](UsingSTLink).
+See [UsingSTLink](UsingSTLink.md).
## Oh no, I'm locked out of my device
@@ -33,7 +33,7 @@ best case scenario. Log in as wheel with the default PIN
able to reset the PINs.
If you forgot the PIN, I feel sorry for you. The only way out of this is
-via [ST-LINK](UsingSTLink). The easiest way is to debug with `gdb`, set a breakpoint on
+via [ST-LINK](UsingSTLink.md). The easiest way is to debug with `gdb`, set a breakpoint on
`hal_rpc_login`, and issue the gdb command `return 0`.
## Oh no, I forgot (or reset) the master key