Skip to content

Commit 0f34110

Browse files
authored
Merge pull request #3982 from mysterywolf/pr2
[bsp] [stm32] [bluepill] update README.md
2 parents bd91d54 + 0cacc10 commit 0f34110

File tree

6 files changed

+62
-10
lines changed

6 files changed

+62
-10
lines changed

bsp/stm32/stm32f103-blue-pill/README.md

Lines changed: 62 additions & 10 deletions
Original file line numberDiff line numberDiff line change
@@ -9,23 +9,23 @@ The document is covered in four parts:
99
- Onboard Resources
1010
- Quickly Get Started
1111
- Advanced Features
12-
- References
12+
- Read more
1313

1414
By reading the ***Quickly Get Started*** section developers can quickly get their hands on this BSP and run RT-Thread on the board. More advanced features will be introduced in the Advanced Features section to help developers take advantage of RT-Thread to drive more on-board resources.
1515

1616

1717

1818
## Onboard Resources
1919

20-
The "blue pill" is a STM32F103 based development board with Cortex-M3 ARM CPU that runs at 72 MHz, 20 KB of RAM and 64 or 128 KB of flash memory. The microcontroller (MCU) has a USB port, two serial ports, 16 bit PWM pins and 12 bit ADC pins. It runs at 3.3V, but some of its pins are 5V tolerant.
20+
The Blue Pill is a STM32F103 based development board with Cortex-M3 ARM CPU that runs at 72 MHz, 20 KB of RAM and 64 or 128 KB of flash memory. The microcontroller (MCU) has a USB port, two serial ports, 16 bit PWM pins and 12 bit ADC pins. It runs at 3.3V, but some of its pins are 5V tolerant.
2121

2222
- MCU:STM32F103C8T6 @72MHz, 64KB FLASH , 20KB RAM
2323

2424
- Peripherals
2525

2626
- LED:PC13
2727

28-
- Debug IO interface type: SWD / ST-LINK
28+
- Debug IO interface type: ST-LINK V2 (SWD)
2929

3030

3131
![board](figures/Bluepill_pinout.png)
@@ -38,23 +38,73 @@ The "blue pill" is a STM32F103 based development board with Cortex-M3 ARM CPU th
3838

3939
This BSP provides MDK4, MDK5, and IAR projects for developers and it supports the GCC development environment. Here's an example of the MDK5 development environment, to introduce how to run the system.
4040

41-
### Hardware connection
41+
### Use ST-LINK Debugger to connect the Blue Pill Board
42+
43+
ST-LINK driver: https://www.st.com/en/development-tools/stsw-link009.html
44+
45+
| ST-LINK Debugger | Blue Pill 4-Pin SWD |
46+
| :--------------: | :-----------------: |
47+
| SWDIO | IO |
48+
| SWDCLK | CLK |
49+
| VCC3.3 | VCC3.3 |
50+
| GND | GND |
51+
52+
![connection](figures/connecter1.jpeg)
53+
54+
![connection](figures/connecter2.png)
55+
56+
![connection](figures/connecter3.jpeg)
57+
58+
59+
60+
### Use FTDI adapter(USB to UART) to connect the Blue Pill Board's PA9(Tx) and PA10(Rx) pins
61+
62+
FTDI adapter driver: https://www.ftdichip.com/FTDrivers.htm
63+
64+
You can use other USB to UART adapters to replace FTDI adapter.
65+
66+
| FTDI adapter(USB to UART) | Blue Pill Board |
67+
| :-----------------------: | :-----------------------------------: |
68+
| Tx | PA10 Rx |
69+
| Rx | PA9 Tx |
70+
| GND | GND |
71+
| VCC 3.3 | **Don't need to connect VCC 3.3 pin** |
72+
| VCC 5 | **Don't need to connect VCC 5 pin** |
4273

43-
1) Use a Type-A to Mini-B cable to connect the development board to the PC and turn on the power switch.
4474

45-
2) Use FTDI adapter(USB to UART) to connect the Blue Pill board's PA9(Tx) and PA10(Rx) pins.
4675

4776
![connection](figures/connection.jpg)
4877

78+
79+
80+
### Make sure Jumper Position (Both 0 Position)
81+
82+
| BOOTx | High / Low |
83+
| :---: | :--------: |
84+
| BOOT0 | 0 |
85+
| BOOT1 | 0 |
86+
87+
![connection](figures/jumper.jpg)
88+
89+
90+
4991
### Compile and Download
5092

51-
Double-click the `project.uvprojx` file to open the MDK5 project; compile and download the program to the board.
93+
- Double-click the `project.uvprojx` file to open the MDK5 project (**NOT** `template.uvprojx` file)
94+
- Click the “option for target” button
95+
- Debug: Choose "ST-LINK Debugger" and Click "Setting" button:
96+
- Port: choose "SW (Serial Wire)"
97+
- Flash Download: check "Reset and Run"
98+
99+
- Compile and download the program to the board
100+
101+
52102

53103
### Running Results
54104

55105
After the program is successfully downloaded, the system runs automatically. Observe the running results of the LED on the development board, and you will see the LED is flashing periodically.
56106

57-
The USB virtual COM port connects to USART1(PA9-Tx, PA10-Rx) by default, and when the corresponding serial port (115200-8-1-N) is opened in the terminal tool, the output information of RT-Thread can be seen when the device is reset:
107+
The USB virtual COM port connects to **USART1 (PA9-Tx, PA10-Rx) by default**, and when the corresponding serial port (**115200**-8-1-N) is opened in the terminal tool, the output information of RT-Thread can be seen when the device is reset:
58108

59109
```shell
60110
\ | /
@@ -64,6 +114,8 @@ The USB virtual COM port connects to USART1(PA9-Tx, PA10-Rx) by default, and whe
64114
msh >
65115
```
66116

117+
- If you have no terminal tool software available, you can download *Putty*: https://www.chiark.greenend.org.uk/~sgtatham/putty/latest.html
118+
67119

68120

69121
## **Advanced Features**
@@ -79,7 +131,7 @@ Learn how to use RT-Thread ENV, click [Here](https://github.com/RT-Thread/rtthre
79131

80132

81133

82-
## References
134+
## Read more
83135

84136
- [[Schematic]](https://stm32duinoforum.com/forum/images/c/c1/wiki_subdomain/Vcc-gnd.com-STM32F103C8-schematic.pdf)
85137
- [[STM32 Blue Pill vs Black Pill Microcontroller Boards]](https://www.youtube.com/watch?v=QCdnO43RBK4&t=875s)
@@ -91,7 +143,7 @@ Learn how to use RT-Thread ENV, click [Here](https://github.com/RT-Thread/rtthre
91143

92144
## Maintained By
93145

94-
Meco Man @ rt-thread community
146+
Meco Man @ RT-Thread Community
95147

96148
97149

3.45 MB
Binary file not shown.
452 KB
Loading
144 KB
Loading
1.81 MB
Loading
237 KB
Loading

0 commit comments

Comments
 (0)