Skip to content

Commit 2cdba4a

Browse files
committed
Minor corrections
1 parent 043e55c commit 2cdba4a

File tree

5 files changed

+13
-5
lines changed

5 files changed

+13
-5
lines changed

0A_power/Cargo.lock

Lines changed: 2 additions & 0 deletions
Some generated files are not rendered by default. Learn more about customizing how changed files appear on GitHub.

0A_power/src/power.rs

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,7 @@
11
/*
22
* MIT License
33
*
4-
* Copyright (c) 2018 Andre Richter <andre.o.richter@gmail.com>
4+
* Copyright (c) 2018-2019 Andre Richter <andre.o.richter@gmail.com>
55
*
66
* Permission is hereby granted, free of charge, to any person obtaining a copy
77
* of this software and associated documentation files (the "Software"), to deal
@@ -95,7 +95,7 @@ impl Power {
9595
compiler_fence(Ordering::Release);
9696

9797
if mbox.call(mbox::channel::PROP).is_err() {
98-
return Err(PowerError::MailboxError); // Abort if UART clocks couldn't be set
98+
return Err(PowerError::MailboxError);
9999
};
100100
}
101101

0B_hw_debug_JTAG/README.md

Lines changed: 7 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -6,7 +6,7 @@ processor's `Exception Level` or introducing `virtual memory`.
66

77
A hardware based debugger can sometimes be the last resort when searching for a
88
tricky bug. Especially for debugging intricate, architecture-specific HW issues,
9-
it will be handy, because in this area `QEMU` sometimes can not help, because it
9+
it will be handy, because in this area `QEMU` sometimes can not help, since it
1010
abstracts certain features of our RPi's HW and doesn't simulate down to the very
1111
last bit.
1212

@@ -15,6 +15,11 @@ through our kernel on the real HW. How cool is that?!
1515

1616
![JTAG live demo](../doc/jtag_demo.gif)
1717

18+
## Outline
19+
20+
Functionally, this tutorial is the same as the previous one, where we reset or
21+
power down the RPi. Around that, we add infrastructure for JTAG debugging.
22+
1823
## Hardware
1924

2025
Unlike microcontroller boards like the `STM32F3DISCOVERY`, which is used in our
@@ -185,7 +190,7 @@ the minimal JTAG pin enablement binary).
185190
>>> break _boot_cores
186191
Breakpoint 1 at 0x80000
187192
>>> target remote :3333 # Connect to OpenOCD, raspi3.core0
188-
>>> load kernel8_for_jtag # Load the kernel into the Raspi's DRAM over JTAG.
193+
>>> load # Load the kernel into the Raspi's DRAM over JTAG.
189194
Loading section .text, size 0x6cc lma 0x80000
190195
Loading section .rodata, size 0x9a lma 0x806cc
191196
Start address 0x80000, load size 1894

0B_hw_debug_JTAG/src/power.rs

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -95,7 +95,7 @@ impl Power {
9595
compiler_fence(Ordering::Release);
9696

9797
if mbox.call(mbox::channel::PROP).is_err() {
98-
return Err(PowerError::MailboxError); // Abort if UART clocks couldn't be set
98+
return Err(PowerError::MailboxError);
9999
};
100100
}
101101

docker/raspi3-openocd/rpi3.cfg

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,6 @@
11
# Script from
22
# https://www.suse.com/c/debugging-raspberry-pi-3-with-jtag/
3+
# with minor adaptions.
34

45
transport select jtag
56

0 commit comments

Comments
 (0)