alex/rp-hal-boards
1
0
Fork 0
mirror of https://github.com/italicsjenga/rp-hal-boards.git synced 2024-12-23 12:41:31 +11:00
Code Issues Packages Projects Releases Wiki Activity

Change references to probe-run-rp back to upstream probe-run

Browse source
This commit is contained in:
Jan Niehusmann 2021-11-28 10:21:17 +00:00 committed by 9names
parent fad1dfa259
commit 05e072025d
2 changed files with 7 additions and 12 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

2
.cargo/config
View file

@ -39,4 +39,4 @@ runner = "elf2uf2-rs -d"
# This runner will find a supported SWD debug probe and flash your RP2040 over # This runner will find a supported SWD debug probe and flash your RP2040 over
# SWD: # SWD:
# runner = "probe-run-rp --chip RP2040" # runner = "probe-run --chip RP2040"

17
README.md
View file

@ -73,7 +73,7 @@ You may also want to install these helpful tools:
# Useful to creating UF2 images for the RP2040 USB Bootloader # Useful to creating UF2 images for the RP2040 USB Bootloader
cargo install elf2uf2-rs --locked cargo install elf2uf2-rs --locked
# Useful for flashing over the SWD pins using a supported JTAG probe # Useful for flashing over the SWD pins using a supported JTAG probe
cargo install --git https://github.com/rp-rs/probe-run.git --branch rp2040-support cargo install probe-run
``` ```
## Packages ## Packages
@ -258,22 +258,17 @@ debug/JTAG probes. It is based on a library called
[probe-rs](https://github.com/probe-rs/probe-rs). Unlike using, say, OpenOCD, [probe-rs](https://github.com/probe-rs/probe-rs). Unlike using, say, OpenOCD,
probe-rs can autodetect your debug probe, which can make it easier to use. probe-rs can autodetect your debug probe, which can make it easier to use.
Currently, probe-rs supports the slightly unusual debug hardware in the RP2040, *Step 1* - Install `probe-run`:
but the last released probe-run tool (v0.2.6, as of September 2021), does not.
However, there is a special version of probe-run for the RP2040 called
[probe-run-rp](https://github.com/rp-rs/probe-run/tree/rp2040-support).
*Step 1* - Install `probe-run-rp`:
```console ```console
$ cargo install --git https://github.com/rp-rs/probe-run.git --branch rp2040-support $ cargo install probe-run
``` ```
*Step 2* - Make sure your .cargo/config contains the following: *Step 2* - Make sure your .cargo/config contains the following:
```toml ```toml
[target.thumbv6m-none-eabi] [target.thumbv6m-none-eabi]
runner = "probe-run-rp --chip RP2040" runner = "probe-run --chip RP2040"
``` ```
*Step 3* - Connect your USB JTAG/debug probe (such as a Raspberry Pi Pico *Step 3* - Connect your USB JTAG/debug probe (such as a Raspberry Pi Pico
@ -282,7 +277,7 @@ programming pins on your RP2040 board. Check the probe has been found by
running: running:
```console ```console
$ probe-run-rp --chip RP2040 --list-probes $ probe-run --chip RP2040 --list-probes
The following devices were found: The following devices were found:
[0]: J-Link (J-Link) (VID: 1366, PID: 0101, Serial: 000099999999, JLink) [0]: J-Link (J-Link) (VID: 1366, PID: 0101, Serial: 000099999999, JLink)
``` ```
@ -291,7 +286,7 @@ There is a SEGGER J-Link connected in the example above - the mesage you see
will reflect the probe you have connected. will reflect the probe you have connected.
*Step 4* - Use `cargo run`, which will compile the code and start the specified *Step 4* - Use `cargo run`, which will compile the code and start the specified
'runner'. As the 'runner' is the `probe-run-rp` tool, it will connect to the 'runner'. As the 'runner' is the `probe-run` tool, it will connect to the
RP2040 via the first probe it finds, and install your firmware into the Flash RP2040 via the first probe it finds, and install your firmware into the Flash
connected to the RP2040. connected to the RP2040.