Lines Matching +full:run +full:- +full:in +full:- +full:debug
6 The Raspberry Pi Pico and Pico W are small, low-cost, versatile boards from
7 Raspberry Pi. They are equipped with an RP2040 SoC, an on-board LED,
9 Infineon CYW43439 2.4 GHz Wi-Fi/Bluetooth module. The USB bootloader allows the
10 ability to flash without any adapter, in a drag-and-drop manner.
11 It is also possible to flash and debug the boards with their SWD interface,
16 - Dual core Arm Cortex-M0+ processor running up to 133MHz
17 - 264KB on-chip SRAM
18 - 2MB on-board QSPI flash with XIP capabilities
19 - 26 GPIO pins
20 - 3 Analog inputs
21 - 2 UART peripherals
22 - 2 SPI controllers
23 - 2 I2C controllers
24 - 16 PWM channels
25 - USB 1.1 controller (host/device)
26 - 8 Programmable I/O (PIO) for custom peripherals
27 - On-board LED
28 - 1 Watchdog timer peripheral
29 - Infineon CYW43439 2.4 GHz Wi-Fi chip (Pico W only)
50 .. list-table::
51 :header-rows: 1
53 * - Peripheral
54 - Kconfig option
55 - Devicetree compatible
56 * - NVIC
57 - N/A
58 - :dtcompatible:`arm,v6m-nvic`
59 * - UART
60 - :kconfig:option:`CONFIG_SERIAL`
61 - :dtcompatible:`raspberrypi,pico-uart`
62 * - GPIO
63 - :kconfig:option:`CONFIG_GPIO`
64 - :dtcompatible:`raspberrypi,pico-gpio`
65 * - ADC
66 - :kconfig:option:`CONFIG_ADC`
67 - :dtcompatible:`raspberrypi,pico-adc`
68 * - I2C
69 - :kconfig:option:`CONFIG_I2C`
70 - :dtcompatible:`snps,designware-i2c`
71 * - SPI
72 - :kconfig:option:`CONFIG_SPI`
73 - :dtcompatible:`raspberrypi,pico-spi`
74 * - USB Device
75 - :kconfig:option:`CONFIG_USB_DEVICE_STACK`
76 - :dtcompatible:`raspberrypi,pico-usbd`
77 * - HWINFO
78 - :kconfig:option:`CONFIG_HWINFO`
79 - N/A
80 * - Watchdog Timer (WDT)
81 - :kconfig:option:`CONFIG_WATCHDOG`
82 - :dtcompatible:`raspberrypi,pico-watchdog`
83 * - PWM
84 - :kconfig:option:`CONFIG_PWM`
85 - :dtcompatible:`raspberrypi,pico-pwm`
86 * - Flash
87 - :kconfig:option:`CONFIG_FLASH`
88 - :dtcompatible:`raspberrypi,pico-flash`
89 * - Clock controller
90 - :kconfig:option:`CONFIG_CLOCK_CONTROL`
91 - :dtcompatible:`raspberrypi,pico-clock-controller`
92 * - UART (PIO)
93 - :kconfig:option:`CONFIG_SERIAL`
94 - :dtcompatible:`raspberrypi,pico-uart-pio`
95 * - SPI (PIO)
96 - :kconfig:option:`CONFIG_SPI`
97 - :dtcompatible:`raspberrypi,pico-spi-pio`
110 Since GPIO 25 is routed to the on-board LED on the Pico, but to the Infineon module
115 ----------------------------------
117 .. rst-class:: rst-columns
119 - UART0_TX : P0
120 - UART0_RX : P1
121 - I2C0_SDA : P4
122 - I2C0_SCL : P5
123 - I2C1_SDA : P6
124 - I2C1_SCL : P7
125 - SPI0_RX : P16
126 - SPI0_CSN : P17
127 - SPI0_SCK : P18
128 - SPI0_TX : P19
129 - ADC_CH0 : P26
130 - ADC_CH1 : P27
131 - ADC_CH2 : P28
132 - ADC_CH3 : P29
137 co-processors that are designed for I/O operations. The PIOs run
142 manually assembled and embedded in source code. An example of how this is done
162 ----------------------------
165 provided by Infineon. Run the command below to retrieve those files:
167 .. code-block:: console
179 ------------------
181 You can Flash the rpi_pico with a SEGGER JLink debug probe as described in
182 :ref:`Building, Flashing and Debugging <west-flashing>`.
184 Here is an example of building and flashing the :zephyr:code-sample:`blinky` application.
186 .. zephyr-app-commands::
187 :zephyr-app: samples/basic/blinky
191 .. code-block:: bash
193 west flash --runner jlink
196 -------------
198 To use CMSIS-DAP, You must configure **udev**.
200 Create a file in /etc/udev.rules.d with any name, and write the line below.
202 .. code-block:: bash
209 and debug the on board RP2040. This interface can be utilized by OpenOCD.
217 Build and install OpenOCD as described in the README.
219 Here is an example of building and flashing the :zephyr:code-sample:`blinky` application.
221 .. zephyr-app-commands::
222 :zephyr-app: samples/basic/blinky
225 …:gen-args: -DOPENOCD=/usr/local/bin/openocd -DOPENOCD_DEFAULT_PATH=/usr/local/share/openocd/script…
232 **RPI_PICO_DEBUG_ADAPTER** specifies what debug adapter is used for debugging.
234 If **RPI_PICO_DEBUG_ADAPTER** was not assigned, ``cmsis-dap`` is used by default.
235 The other supported adapters are ``raspberrypi-swd``, ``jlink`` and ``blackmagicprobe``.
236 How to connect ``cmsis-dap`` and ``raspberrypi-swd`` is described in `Getting Started with Raspberr…
237 Any other SWD debug adapter maybe also work with this configuration.
240 ``west flash`` and ``west debug`` if it was previously set while running
243 **RPI_PICO_DEBUG_ADAPTER** is used in an argument to OpenOCD as ``"source [find interface/${RPI_PIC…
244 Thus, **RPI_PICO_DEBUG_ADAPTER** needs to be assigned the file name of the debug adapter.
249 .. code-block:: console
251 …$ openocd -f interface/jlink.cfg -c 'transport select swd' -f target/rp2040.cfg -c "adapter speed …
254 ---------
260 UF2 file should be drag-and-dropped to the device, which will flash the Pico.
265 The SWD interface can also be used to debug the board. To achieve this, you can
269 ------------------
271 Use a SEGGER JLink debug probe and follow the instruction in
272 :ref:`Building, Flashing and Debugging<west-debugging>`.
276 -------------
280 Here is an example for debugging the :zephyr:code-sample:`blinky` application.
282 .. zephyr-app-commands::
283 :zephyr-app: samples/basic/blinky
285 :maybe-skip-config:
286 :goals: debug
287 …:gen-args: -DOPENOCD=/usr/local/bin/openocd -DOPENOCD_DEFAULT_PATH=/usr/local/share/openocd/script…
289 As with flashing, you can specify the debug adapter by specifying **RPI_PICO_DEBUG_ADAPTER**
290 at ``west build`` time. No needs to specify it at ``west debug`` time.
292 You can also debug with OpenOCD and gdb launching from command-line.
293 Run the following command:
295 .. code-block:: console
297 …$ openocd -f interface/jlink.cfg -c 'transport select swd' -f target/rp2040.cfg -c "adapter speed …
299 On another terminal, run:
301 .. code-block:: console
303 $ gdb-multiarch
305 Inside gdb, run:
307 .. code-block:: console
314 .. target-notes::
317 https://raw.githubusercontent.com/raspberrypi/pico-setup/master/pico_setup.sh
320 https://datasheets.raspberrypi.com/pico/getting-started-with-pico.pdf