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
Copy file name to clipboardExpand all lines: README.md
+20-8Lines changed: 20 additions & 8 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,18 +1,21 @@
1
1
# Raspberry Pi Pico SDK Examples
2
2
3
-
By default, the Pico SDK targets builds for RP2040 (PICO_PLATFORM=rp2040). To build for RP2350 instead, pass
4
-
`-DPICO_PLATFORM=rp2350` to CMake (or `-DPICO_PLATFORM=rp2350-riscv` for RISC-V). Alternatively, in many cases, you can rely
5
-
on the board configuration to set the platform for you. For example, passing `-DPICO_BOARD=pico2` will automatically select RP2350.
3
+
## Getting started
6
4
7
-
Most, but not all examples, currently work on RP2350 however you should be able to do a full build with any of the above platforms (PICO_PLATFORM=host however currently fails on some examples)
5
+
See [Getting Started with the Raspberry Pi Pico](https://rptl.io/pico-get-started) and the README in the [pico-sdk](https://github.com/raspberrypi/pico-sdk) for information
6
+
on getting up and running.
8
7
9
-
For RISC-V compilation, you should take a compiler from here: https://www.embecosm.com/resources/tool-chain-downloads/#riscv-stable
8
+
##### Notes on different boards and platforms (RP2040 / RP2350)
10
9
10
+
The majority of examples are applicable to both RP2040 and RP2350 based boards,
11
+
however certain examples that use chip-specific functionality will only build on that platform.
12
+
Similarly, Wi-Fi and Bluetooth examples will only build on a board that includes Wi-Fi and Bluetooth support.
11
13
12
-
## Getting started
14
+
Platform and board information are passed to the CMake build via the `PICO_PLATFORM` and `PICO_BOARD` variables.
15
+
For more information see the "Platform and Board Configuration" chapter of
16
+
the [Raspberry Pi Pico-series C/C++ SDK](https://rptl.io/pico-c-sdk) book
13
17
14
-
See [Getting Started with the Raspberry Pi Pico](https://rptl.io/pico-get-started) and the README in the [pico-sdk](https://github.com/raspberrypi/pico-sdk) for information
15
-
on getting up and running.
18
+
Information on which examples are not being built is output during the CMake configuration step.
16
19
17
20
### First Examples
18
21
@@ -187,6 +190,7 @@ App|Description
187
190
[picow_httpd](pico_w/wifi/httpd) | Runs a LWIP HTTP server test app
188
191
[picow_http_client](pico_w/wifi/http_client) | Demonstrates how to make http and https requests
189
192
[picow_http_client_verify](pico_w/wifi/http_client) | Demonstrates how to make a https request with server authentication
193
+
[picow_mqtt_client](pico_w/wifi/mqtt) | Demonstrates how to implement an MQTT client application
190
194
191
195
#### FreeRTOS examples
192
196
@@ -426,6 +430,14 @@ App|Description
426
430
---|---
427
431
[dev_lowlevel](usb/device/dev_lowlevel) | A USB Bulk loopback implemented with direct access to the USB hardware (no TinyUSB)
428
432
433
+
#### Custom CDC with SDK stdio
434
+
435
+
This example demonstrates how to use the TinyUSB CDC device library to create two USB serial ports, and assign one of them to the SDK for stdio.
436
+
437
+
App|Description
438
+
---|---
439
+
[dev_cdc](usb/device/dev_cdc) | A USB CDC device example with two serial ports, one of which is used for stdio. The example exposes two serial ports over USB to the host. The first port is used for stdio, and the second port is used for a simple echo loopback. You can connect to the second port and send some characters, and they will be echoed back on the first port while you will receive a "OK\r\n" message on the second port indicating that the data was received.
440
+
429
441
### USB Host
430
442
431
443
All the USB host examples come directly from the TinyUSB host examples directory [here](https://github.com/hathach/tinyusb/tree/master/examples/host).
0 commit comments