Skip to content

Commit 5bfcdb3

Browse files
authored
Better handle previous merge
1 parent 1ccfe90 commit 5bfcdb3

File tree

1 file changed

+7
-2
lines changed

1 file changed

+7
-2
lines changed

README.md

Lines changed: 7 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -12,10 +12,15 @@ however certain examples that use chip-specific functionality will only build on
1212
Similarly, Wi-Fi and Bluetooth examples will only build on a board that includes Wi-Fi and Bluetooth support.
1313

1414
Platform and board information are passed to the CMake build via the `PICO_PLATFORM` and `PICO_BOARD` variables.
15+
16+
By default, the Pico SDK targets builds for RP2040 (`PICO_PLATFORM=rp2040`). To build for RP2350 instead, pass
17+
`-DPICO_PLATFORM=rp2350` to CMake (or `-DPICO_PLATFORM=rp2350-riscv` for RISC-V). Alternatively, in many cases, you can rely
18+
on the board configuration to set the platform for you. For example, passing `-DPICO_BOARD=pico2` will automatically select `PICO_PLATFORM=rp2350`.
19+
1520
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
21+
the [Raspberry Pi Pico-series C/C++ SDK](https://rptl.io/pico-c-sdk) book.
1722

18-
Information on which examples are not being built is output during the CMake configuration step.
23+
Information on which examples are not being built is displayed during the CMake configuration step.
1924

2025
### First Examples
2126

0 commit comments

Comments
 (0)