Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly
Appearance settings

Commit 94f759f

Browse filesBrowse files
bors[bot]bors[bot]
authored
Try #16:
2 parents 46705c4 + 1bda754 commit 94f759f
Copy full SHA for 94f759f

File tree

15 files changed

+97
-288
lines changed
Filter options

15 files changed

+97
-288
lines changed

‎rtic_v5/bluepill_blinky/.embed.toml

Copy file name to clipboard
+16Lines changed: 16 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,16 @@
1+
# Refer to https://github.com/probe-rs/cargo-embed/blob/master/src/config/default.toml
2+
# for the comprehensive list of options
3+
4+
[default.general]
5+
chip = "STM32F103"
6+
7+
[default.rtt]
8+
enabled = true
9+
show_timestamps = true
10+
11+
[default.gdb]
12+
# Whether or not a GDB server should be opened after flashing.
13+
# This is exclusive and cannot be used with RTT at the moment.
14+
enabled = false
15+
# The connection string in host:port format wher the GDB server will open a socket.
16+
# gdb_connection_string

‎rtic_v5/bluepill_blinky/README.md

Copy file name to clipboardExpand all lines: rtic_v5/bluepill_blinky/README.md
+6-56Lines changed: 6 additions & 56 deletions
Original file line numberDiff line numberDiff line change
@@ -35,63 +35,13 @@ You need to connect you bluepill board to ST-Link and connect pins:
3535

3636
Plug in ST-Link to USB port and wait it to initialize.
3737

38-
### Upload
38+
### Flashing and running
3939

40-
We will use openocd to upload the code wit simple one-line one-command script:
40+
Flashing with a standard STLink v2 is easy with `cargo-embed`:
4141

42-
```bash
43-
openocd -f openocd.cfg -c "program target/thumbv7m-none-eabi/debug/app verify reset exit"
44-
```
45-
46-
You will see something like:
47-
48-
```bash
49-
openocd -f openocd.cfg -c "program target/thumbv7m-none-eabi/debug/app verify reset exit"
50-
Open On-Chip Debugger 0.10.0
51-
Licensed under GNU GPL v2
52-
For bug reports, read
53-
http://openocd.org/doc/doxygen/bugs.html
54-
Info : auto-selecting first available session transport "hla_swd". To override use 'transport select <transport>'.
55-
Info : The selected transport took over low-level target control. The results might differ compared to plain JTAG/SWD
56-
adapter speed: 1000 kHz
57-
adapter_nsrst_delay: 100
58-
none separate
59-
Info : Unable to match requested speed 1000 kHz, using 950 kHz
60-
Info : Unable to match requested speed 1000 kHz, using 950 kHz
61-
Info : clock speed 950 kHz
62-
Info : STLINK v2 JTAG v33 API v2 SWIM v7 VID 0x0483 PID 0x3748
63-
Info : using stlink api v2
64-
Info : Target voltage: 3.196863
65-
Info : stm32f1x.cpu: hardware has 6 breakpoints, 4 watchpoints
66-
target halted due to debug-request, current mode: Thread
67-
xPSR: 0x01000000 pc: 0x080033b4 msp: 0x20005000
68-
** Programming Started **
69-
auto erase enabled
70-
Info : device id = 0x20036410
71-
Info : flash size = 64kbytes
72-
target halted due to breakpoint, current mode: Thread
73-
xPSR: 0x61000000 pc: 0x2000003a msp: 0x20005000
74-
wrote 19456 bytes from file target/thumbv7m-none-eabi/debug/app in 1.118153s (16.992 KiB/s)
75-
** Programming Finished **
76-
** Verify Started **
77-
target halted due to breakpoint, current mode: Thread
78-
xPSR: 0x61000000 pc: 0x2000002e msp: 0x20005000
79-
verified 18588 bytes in 0.288441s (62.933 KiB/s)
80-
** Verified OK **
81-
** Resetting Target **
82-
shutdown command invoked
42+
```shell
43+
$ cargo install cargo-embed
44+
$ cargo embed --release
8345
```
8446

85-
## Troubleshooting
86-
87-
If you are lucky and have new version of OpenOCD, you will need to change `openocd.cfg` file. Openocd will report error during the upload process, so you will just need to change line:
88-
89-
```txt
90-
source [find interface/stlink-v2.cfg]
91-
```
92-
93-
to
94-
95-
```txt
96-
source [find interface/stlink.cfg]
97-
```
47+
Please review the `.embed.toml` file to change your target IC among other options.

‎rtic_v5/bluepill_blinky/openocd.cfg

Copy file name to clipboardExpand all lines: rtic_v5/bluepill_blinky/openocd.cfg
-15Lines changed: 0 additions & 15 deletions
This file was deleted.

‎rtic_v5/bluepill_blinky/openocd.gdb

Copy file name to clipboardExpand all lines: rtic_v5/bluepill_blinky/openocd.gdb
-42Lines changed: 0 additions & 42 deletions
This file was deleted.

‎rtic_v5/heartbeat_stm32l4/.embed.toml

Copy file name to clipboard
+16Lines changed: 16 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,16 @@
1+
# Refer to https://github.com/probe-rs/cargo-embed/blob/master/src/config/default.toml
2+
# for the comprehensive list of options
3+
4+
[default.general]
5+
chip = "STM32L412"
6+
7+
[default.rtt]
8+
enabled = true
9+
show_timestamps = true
10+
11+
[default.gdb]
12+
# Whether or not a GDB server should be opened after flashing.
13+
# This is exclusive and cannot be used with RTT at the moment.
14+
enabled = false
15+
# The connection string in host:port format wher the GDB server will open a socket.
16+
# gdb_connection_string

‎rtic_v5/heartbeat_stm32l4/README.md

Copy file name to clipboardExpand all lines: rtic_v5/heartbeat_stm32l4/README.md
+6-57Lines changed: 6 additions & 57 deletions
Original file line numberDiff line numberDiff line change
@@ -38,64 +38,13 @@ You need to connect you Bluepill board to ST-Link and connect pins:
3838

3939
Plug in ST-Link to USB port and wait it to initialize.
4040

41-
### Upload
41+
### Flashing and running
4242

43-
We will use openocd to upload the code wit simple one-line one-command script:
43+
Flashing with a standard STLink v2 is easy with `cargo-embed`:
4444

45-
```bash
46-
openocd -f openocd.cfg -c "program target/thumbv7m-none-eabi/debug/app verify reset exit"
47-
```
48-
49-
You will see something like:
50-
51-
```bash
52-
openocd -f openocd.cfg -c "program target/thumbv7m-none-eabi/debug/app verify reset exit"
53-
Open On-Chip Debugger 0.10.0
54-
Licensed under GNU GPL v2
55-
For bug reports, read
56-
http://openocd.org/doc/doxygen/bugs.html
57-
Info : auto-selecting first available session transport "hla_swd". To override use 'transport select <transport>'.
58-
Info : The selected transport took over low-level target control. The results might differ compared to plain JTAG/SWD
59-
adapter speed: 1000 kHz
60-
adapter_nsrst_delay: 100
61-
none separate
62-
Info : Unable to match requested speed 1000 kHz, using 950 kHz
63-
Info : Unable to match requested speed 1000 kHz, using 950 kHz
64-
Info : clock speed 950 kHz
65-
Info : STLINK v2 JTAG v33 API v2 SWIM v7 VID 0x0483 PID 0x3748
66-
Info : using stlink api v2
67-
Info : Target voltage: 3.196863
68-
Info : stm32f1x.cpu: hardware has 6 breakpoints, 4 watchpoints
69-
target halted due to debug-request, current mode: Thread
70-
xPSR: 0x01000000 pc: 0x080033b4 msp: 0x20005000
71-
** Programming Started **
72-
auto erase enabled
73-
Info : device id = 0x20036410
74-
Info : flash size = 64kbytes
75-
target halted due to breakpoint, current mode: Thread
76-
xPSR: 0x61000000 pc: 0x2000003a msp: 0x20005000
77-
wrote 19456 bytes from file target/thumbv7m-none-eabi/debug/app in 1.118153s (16.992 KiB/s)
78-
** Programming Finished **
79-
** Verify Started **
80-
target halted due to breakpoint, current mode: Thread
81-
xPSR: 0x61000000 pc: 0x2000002e msp: 0x20005000
82-
verified 18588 bytes in 0.288441s (62.933 KiB/s)
83-
** Verified OK **
84-
** Resetting Target **
85-
shutdown command invoked
45+
```shell
46+
$ cargo install cargo-embed
47+
$ cargo embed --release
8648
```
8749

88-
## Troubleshooting
89-
90-
If you are lucky and have new version of OpenOCD, you will need to change `openocd.cfg` file.
91-
Openocd will report error during the upload process, so you will just need to change line:
92-
93-
```txt
94-
source [find interface/stlink-v2.cfg]
95-
```
96-
97-
to
98-
99-
```txt
100-
source [find interface/stlink.cfg]
101-
```
50+
Please review the `.embed.toml` file to change your target IC among other options.

‎rtic_v5/heartbeat_stm32l4/openocd.cfg

Copy file name to clipboardExpand all lines: rtic_v5/heartbeat_stm32l4/openocd.cfg
-15Lines changed: 0 additions & 15 deletions
This file was deleted.

‎rtic_v5/heartbeat_stm32l4/openocd.gdb

Copy file name to clipboardExpand all lines: rtic_v5/heartbeat_stm32l4/openocd.gdb
-42Lines changed: 0 additions & 42 deletions
This file was deleted.

‎rtic_v5/hid_mouse_stm32f0/.embed.toml

Copy file name to clipboardExpand all lines: rtic_v5/hid_mouse_stm32f0/.embed.toml
+3Lines changed: 3 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -1,3 +1,6 @@
1+
# Refer to https://github.com/probe-rs/cargo-embed/blob/master/src/config/default.toml
2+
# for the comprehensive list of options
3+
14
[default.general]
25
chip = "STM32F042G6Ux"
36

‎rtic_v5/monotonic_nrf52/.embed.toml

Copy file name to clipboard
+16Lines changed: 16 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,16 @@
1+
# Refer to https://github.com/probe-rs/cargo-embed/blob/master/src/config/default.toml
2+
# for the comprehensive list of options
3+
4+
[default.general]
5+
chip = "nrf52832"
6+
7+
[default.rtt]
8+
enabled = true
9+
show_timestamps = true
10+
11+
[default.gdb]
12+
# Whether or not a GDB server should be opened after flashing.
13+
# This is exclusive and cannot be used with RTT at the moment.
14+
enabled = false
15+
# The connection string in host:port format wher the GDB server will open a socket.
16+
# gdb_connection_string

‎rtic_v5/monotonic_nrf52/README.md

Copy file name to clipboard
+11Lines changed: 11 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -1,3 +1,14 @@
11
# nRF52 Monotonic
22

33
In this example we show the use of a custom `rtic::Monotonic` implementation which uses a timer of the `nRF52832` MCU.
4+
5+
### Flashing and running
6+
7+
Flashing with a standard STLink v2 is easy with `cargo-embed`:
8+
9+
```shell
10+
$ cargo install cargo-embed
11+
$ cargo embed --release
12+
```
13+
14+
Please review the `.embed.toml` file to change your target IC among other options.

‎rtic_v5/monotonic_nrf52/jlink.cfg

Copy file name to clipboardExpand all lines: rtic_v5/monotonic_nrf52/jlink.cfg
-29Lines changed: 0 additions & 29 deletions
This file was deleted.

‎rtic_v5/monotonic_nrf52/openocd.gdb

Copy file name to clipboardExpand all lines: rtic_v5/monotonic_nrf52/openocd.gdb
-19Lines changed: 0 additions & 19 deletions
This file was deleted.

0 commit comments

Comments
0 (0)
Morty Proxy This is a proxified and sanitized view of the page, visit original site.