Skip to content

Commit 048f407

Browse files
committed
Merge remote-tracking branch 'ChouzArt/LinksPatch' into relativeUrlWorkaround
2 parents e6fa999 + f7537ca commit 048f407

File tree

17 files changed

+25
-25
lines changed

17 files changed

+25
-25
lines changed

src/02-requirements/README.md

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -25,7 +25,7 @@ Also, to follow this material you'll need the following hardware:
2525
[3]: http://www.ebay.com/sch/i.html?_nkw=stm32f3discovery
2626

2727
<p align="center">
28-
<img title="STM32F3DISCOVERY" src="/assets/f3.jpg">
28+
<img title="STM32F3DISCOVERY" src="../assets/f3.jpg">
2929
</p>
3030

3131
- OPTIONAL. A **3.3V** USB <-> Serial module. [This particular model][sparkfun] will be used
@@ -39,7 +39,7 @@ cheaper for you to get)
3939
[4]: https://www.aliexpress.com/wholesale?SearchText=CH340G
4040

4141
<p align="center">
42-
<img title="A 3.3v USB <-> Serial module" src="/assets/serial.jpg">
42+
<img title="A 3.3v USB <-> Serial module" src="../assets/serial.jpg">
4343
</p>
4444

4545
- OPTIONAL. A HC-05 Bluetooth module (with headers!). A HC-06 would work too.
@@ -51,14 +51,14 @@ cheaper for you to get)
5151
[6]: https://www.aliexpress.com/wholesale?SearchText=hc-05
5252

5353
<p align="center">
54-
<img title="The HC-05 Bluetooth module" src="/assets/bluetooth.jpg">
54+
<img title="The HC-05 Bluetooth module" src="../assets/bluetooth.jpg">
5555
</p>
5656

5757
- Two mini-B USB cables. One is required to make the STM32F3DISCOVERY board work. The other is only
5858
required if you have the Serial <-> USB module.
5959

6060
<p align="center">
61-
<img title="mini-B USB cable" src="/assets/usb-cable.jpg">
61+
<img title="mini-B USB cable" src="../assets/usb-cable.jpg">
6262
</p>
6363

6464
> **NOTE** These are **not** the USB cables that ship with pretty much every Android phone; those
@@ -75,7 +75,7 @@ cheaper for you to get)
7575
[9]: https://www.aliexpress.com/wholesale?SearchText=dupont+wire
7676

7777
<p align="center">
78-
<img title="Jumper wires" src="/assets/jumper-wires.jpg">
78+
<img title="Jumper wires" src="../assets/jumper-wires.jpg">
7979
</p>
8080

8181
> **FAQ**: Wait, why do I need this specific hardware?

src/04-meet-your-hardware/README.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -5,7 +5,7 @@ Let's get familiar with the hardware we'll be working with.
55
## STM32F3DISCOVERY (the "F3")
66

77
<p align="center">
8-
<img title="F3" src="/assets/f3.jpg">
8+
<img title="F3" src="../assets/f3.jpg">
99
</p>
1010

1111
We'll refer to this board as "F3" throughout this book.
@@ -46,7 +46,7 @@ What does this board contain?
4646
## The Serial module
4747

4848
<p align="center">
49-
<img title="Serial module" src="/assets/serial.jpg">
49+
<img title="Serial module" src="../assets/serial.jpg">
5050
</p>
5151

5252
We'll use this module to exchange data between the microcontroller in the F3 and your laptop. This
@@ -55,7 +55,7 @@ module will be connected to your laptop using an USB cable. I won't say more at
5555
## The Bluetooth module
5656

5757
<p align="center">
58-
<img title="The HC-05 Bluetooth module" src="/assets/bluetooth.jpg">
58+
<img title="The HC-05 Bluetooth module" src="../assets/bluetooth.jpg">
5959
</p>
6060

6161
This module has the exact same purpose as the serial module but it sends the data over Bluetooth

src/05-led-roulette/flash-it.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -44,7 +44,7 @@ and debug a microcontroller. The ST-LINK is connected to the "USB ST-LINK" port
4444
a USB device when you connect the F3 to your laptop.
4545

4646
<p align="center">
47-
<img height=640 title="On-board ST-LINK" src="/assets/st-link.png">
47+
<img height=640 title="On-board ST-LINK" src="../assets/st-link.png">
4848
</p>
4949

5050

src/05-led-roulette/the-challenge.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -12,7 +12,7 @@ Here's the GIF again:
1212
Also, this may help:
1313

1414
<p align="center">
15-
<img src="/assets/timing-diagram.png">
15+
<img src="../assets/timing-diagram.png">
1616
</p>
1717

1818
This is a timing diagram. It indicates which LED is on at any given instant of time and for how long

src/06-hello-world/README.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -10,7 +10,7 @@
1010
[User Manual]: http://www.st.com/resource/en/user_manual/dm00063382.pdf
1111

1212
<p align="center">
13-
<img height=640 title="Manual SWD connection" src="/assets/f3-swd.png">
13+
<img height=640 title="Manual SWD connection" src="../assets/f3-swd.png">
1414
</p>
1515

1616
---

src/10-serial-communication/loopbacks.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -6,7 +6,7 @@ can send us some data ... or is there?
66
Enter: loopbacks
77

88
<p align="center">
9-
<img title="Serial module loopback" src="/assets/serial-loopback.png">
9+
<img title="Serial module loopback" src="../assets/serial-loopback.png">
1010
</p>
1111

1212
You can send data to yourself! Not very useful in production but very useful for debugging.

src/10-serial-communication/nix-tooling.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -67,7 +67,7 @@ This tells `minicom` to open the serial device at `/dev/ttyUSB0` and set its bau
6767
A text-based user interface (TUI) will pop out.
6868

6969
<p align="center">
70-
<img height="480" title="minicom" src="/assets/minicom.png">
70+
<img height="480" title="minicom" src="../assets/minicom.png">
7171
</p>
7272

7373
You can now send data using the keyboard! Go ahead and type something. Note that the TUI *won't*

src/10-serial-communication/windows-tooling.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -16,7 +16,7 @@ on the list. That's the COM port assigned to the serial module.
1616
Now launch `putty`. A GUI will pop out.
1717

1818
<p align="center">
19-
<img title="PuTTY settings" src="/assets/putty-settings.png">
19+
<img title="PuTTY settings" src="../assets/putty-settings.png">
2020
</p>
2121

2222
On the starter screen, which should have the "Session" category open, pick "Serial" as the
@@ -35,7 +35,7 @@ that the serial port is configured as follows:
3535
Finally, click the Open button. A console will show up now:
3636

3737
<p align="center">
38-
<img title="PuTTY console" src="/assets/putty-console.png">
38+
<img title="PuTTY console" src="../assets/putty-console.png">
3939
</p>
4040

4141
If you type on this console, the TX (red) LED on the Serial module should blink. Each key stroke

src/11-usart/README.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -26,7 +26,7 @@ microcontroller's TX pin to the serial module's RX pin and the micro's RX pin to
2626
TX pin. The wiring diagram below shows all the necessary connections.
2727

2828
<p align="center">
29-
<img height=640 title="F3 <-> Serial connection" src="/assets/f3-serial.png">
29+
<img height=640 title="F3 <-> Serial connection" src="../assets/f3-serial.png">
3030
</p>
3131

3232
These are the recommended steps to connect the microcontroller and the serial module:

src/12-bluetooth-setup/README.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -11,7 +11,7 @@ The first thing we'll need to do is: turn on the Bluetooth module. We'll have to
1111
F3 power to it using the following connection:
1212

1313
<p align="center">
14-
<img height=640 title="F3 <-> Bluetooth connection (power only)" src="/assets/f3-bluetooth-power-only.png">
14+
<img height=640 title="F3 <-> Bluetooth connection (power only)" src="../assets/f3-bluetooth-power-only.png">
1515
</p>
1616

1717
The recommend steps to wire this up are:

0 commit comments

Comments
 (0)