You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
To build the blink example, run the following command:
30
+
To build the blink example, run the following command:
31
31
```bash
32
32
cmake --build build_pico --target blink
33
33
```
34
-
This builds the specified target `blink` in the build folder `build_pico`
34
+
This builds the specified target `blink` in the build folder `build_pico` - it will probably display `no work to do` because `blink` was built earlier by `pico_setup.sh`
35
35
36
36
Then to run it, attach a Pico-series microcontroller in BOOTSEL mode, and run:
37
37
```bash
@@ -43,7 +43,7 @@ You should now have a blinking LED on your board! For more info on the `picotool
43
43
44
44
## Console Input/Output
45
45
46
-
To view console output, you can either connect the UART output to a [Debug Probe](https://www.raspberrypi.com/documentation/microcontrollers/debug-probe.html#getting-started) (or similar) and use `stdio_uart` (see the hello_serial example), or you can use `stdio_usb` (see the hello_usb example).
46
+
To view console output, you can either connect the UART output to a [Debug Probe](https://www.raspberrypi.com/documentation/microcontrollers/debug-probe.html#getting-started) (or similar) and use `stdio_uart` (see the [hello_serial example](https://github.com/raspberrypi/pico-examples/blob/master/hello_world/serial)), or you can use `stdio_usb` (see the [hello_usb example](https://github.com/raspberrypi/pico-examples/blob/master/hello_world/usb)).
47
47
48
48
First, build & run the example for your `stdio` choice on your Pico-series microcontroller with the same commands as before:
49
49
```bash
@@ -61,7 +61,7 @@ To exit minicom, type Ctrl+A then X
61
61
62
62
## Debugging with OpenOCD and GDB
63
63
64
-
To debug programs on the Pico-series microcontroller, you first need to attach a debugger such as the [Debug Probe](https://www.raspberrypi.com/documentation/microcontrollers/debug-probe.html#getting-started). Once that's done, you can attach OpenOCD to your Pico-series microcontroller with this command (replace `rp2040.cfg` with `rp2350.cfg`, if using an RP2350-bashed board like a Pico 2):
64
+
To debug programs on the Pico-series microcontroller, you first need to attach a debugger such as the [Debug Probe](https://www.raspberrypi.com/documentation/microcontrollers/debug-probe.html#getting-started). Once that's done, you can attach OpenOCD to your Pico-series microcontroller with this command (replace `rp2040.cfg` with `rp2350.cfg`, if using an RP2350-based board like a Pico 2):
* On Windows, download and extract libUSB from here https://libusb.info/ (hover over Downloads, and click Latest Windows Binaries), and set LIBUSB_ROOT environment variable to the extracted directory.
188
188
* On MacOS `brew install libusb`
189
-
* On Linux `apt install libusb-1.0-0-dev`
189
+
* On Linux `sudo apt install libusb-1.0-0-dev`
190
190
191
-
Then build and install picotool using these commands
191
+
Then build and install picotool using these commands:
192
192
```bash
193
193
cd picotool
194
194
cmake -S . -B build
@@ -201,20 +201,22 @@ To use picotool without sudo on Linux, you'll also need to install the picotool
201
201
For more details on building & installing picotool, see its [README](https://github.com/raspberrypi/picotool?tab=readme-ov-file#readme)
0 commit comments