RP2350-GEEK

From Waveshare Wiki
Jump to: navigation, search

Overview

RP2350-GEEK
RP2350-GEEK

SWD/UART/USB-A
{{{name2}}}

{{{name3}}}

{{{name4}}}

{{{name5}}}

{{{name6}}}

Introduction

RP2350-GEEK is a development board designed for geeks by Waveshare. It comes with a USB-A port, 1.14-inch LCD screen, TF card slot, and other peripherals. Depending on the firmware used, it can provide SWD interface, UART interface, and I2C interface, offering endless possibilities for your projects.

Features

  • RP2350 microcontroller chip designed by Raspberry Pi
  • Adopts unique dual-core and dual-architecture design, equipped with dual-core ARM Cortex-M33 processor and dual-core Hazard3 RISC-V core processor, flexible clock running up to 150 MHz
  • Built-in 520KB of SRAM and 16MB of on-chip Flash
  • Onboard 1.14inch 240×135 pixels 65K color IPS LCD display
  • Onboard 3PIN SWD interface for connecting to the target board to be debugged
    • Standard CMSIS-DAP interface, applicable for most ARM-based microcontrollers
    • Works with OpenOCD and other tools supporting CMSIS-DAP
    • Adopts the Raspberry Pi 3PIN Debug Connector Specification
  • Onboard 3PIN UART interface for USB serial adapter
  • Onboard 4PIN I2C port for the testing target board
  • Equipped with plastic case and cables
  • Open-source firmware, more convenient to upgrade

Dimensions

800px-RP2040-GEEK-details-size.jpg

Pico Getting Started

Firmware download

  • MicroPython firmware download

Pico MicroPython.gif

  • C_Blink firmware download

Pico Blink.gif

Text tutorial

Introduction

Raspberry Pi Pico Basics

MicroPython series

Install Thonny IDE

In order to facilitate the development of Pico/Pico2 boards using MicroPython on a computer, it is recommended to download the Thonny IDE

  • Download Thonny IDE and follow the steps to install, the installation packages are all Windows versions, please refer to Thonny's official website for other versions
  • After installation, the language and motherboard environment need to be configured for the first use. Since we are using Pico/Pico2, we select the Raspberry Pi option for the motherboard environment

Pico-R3-Tonny1.png

  • Configure MicroPython environment and choose Pico/Pico2 port
    • Connect Pico/Pico2 to your computer first, and in the lower right corner of Thonny left-click on the configuration environment option --> select Configture interpreter
    • In the pop-up window, select MicroPython (Raspberry Pi Pico), and choose the corresponding port

700px-Raspberry-Pi-Pico-Basic-Kit-M-2.png
700px-Raspberry-Pi-Pico-Basic-Kit-M-3.png

  • Click OK to return to the Thonny main interface, download the corresponding firmware library and burn it to the device, and then click the Stop button to display the current environment in the Shell window
  • How to download the firmware library for Pico/Pico2 in windows: After holding down the BOOT button and connecting to the computer, release the BOOT button, a removable disk will appear on the computer, copy the firmware library into it
  • How to download the firmware library for RP2040/RP2350 in windows: After connecting to the computer, press the BOOT key and the RESET key at the same time, release the RESET key first and then release the BOOT key, a removable disk will appear on the computer, copy the firmware library into it (you can also use the Pico/Pico2 method)

Raspberry-Pi-Pico2-Python.png

Details

C/C++ series

For C/C++, it is recommended to use Pico VS Code for development. This is a Microsoft Visual Studio Code extension designed to make it easier for you to create, develop, and debug projects for the Raspberry Pi Pico series development boards. No matter if you are a beginner or an experienced professional, this tool can assist you in developing Pico with confidence and ease. Here's how to install and use the extension.

  • Official website tutorial: https://www.raspberrypi.com/news/pico-vscode-extension/
  • This tutorial is applicable to Raspberry Pi Pico, Pico2 and the RP2040 and RP2350 series development boards developed by our company
  • The default development environment is Windows. For other environments, please refer to the official website tutorial for installation

Install VSCode

  1. Firstly, click to download pico-vscode package, unzip and open the package, double-click to install VSCode
    Pico-vscode-1.JPG
    Note: If vscode is already installed, check if the version is v1.87.0 or higher
    Pico-vscode-2.JPG
    Pico-vscode-3.JPG

Install extension

  1. Click on EXTENSIONS, select Install from VSIX
    Pico-vscode-4.jpg
  2. Select the package with vsix suffix, click Install
    Pico-vscode-5.jpg
  3. Then vscode will automatically install Raspberry Pi Pico and its dependent extensions. You can click Refresh to view the installation progress
    Pico-vscode-6.jpg
  4. The bottom right corner shows installation completed, close vscode
    Pico-vscode-7.JPG

Configure extension

  1. Open the directory C:\Users\username and copy the entire .pico-sdk to that directory
    Pico-vscode-8.JPG
  2. The copy is completed
    Pico-vscode-9.JPG
  3. Open VSCode and configure various paths in the Raspberry Pi Pico extension
    Pico-vscode-10.JPG
    The configuration is as follows:
    Cmake Path:
    ${HOME}/.pico-sdk/cmake/v3.28.6/bin/cmake.exe
    
    Git Path:
    ${HOME}/.pico-sdk/git/cmd/git.exe    
    
    Ninja Path:
    ${HOME}/.pico-sdk/ninja/v1.12.1/ninja.exe
    
    Python3 Path:
    ${HOME}/.pico-sdk/python/3.12.1/python.exe             
    

New project

  1. Configuration is completed, then create a new project. First enter the project name, select the path, and click Create to create the project
    To test the official example, you can click Example next to the project name to select
    Pico-vscode-11.JPG
  2. The project was created successfully
    Pico-vscode-12.JPG
  3. Select SDK version
    Pico-vscode-13.JPG
  4. Select Yes for advanced configuration
    Pico-vscode-14.JPG
  5. Select the cross-compilation chain, 13.2.Rel1 is for ARM cores, RISCV.13.3 is for RISCV cores, and you can choose one of them according to your needs
    Pico-vscode-15.JPG
  6. Selects Default (the path configured earlier) for CMake version
    Pico-vscode-16.JPG
  7. Select Default for Ninja version
    Pico-vscode-17.JPG
  8. Select development board
    Pico-vscode-18.JPG
  9. Click Complie to compile
    Pico-vscode-19.JPG
  10. The uf2 format file is successfully compiled
    Pico-vscode-20.JPG

Import project

  1. The Cmake file for importing the project cannot have Chinese (including comments), otherwise it may cause import failure
  2. To import your own project, you need to add a line of code to the Cmake file to switch between pico and pico2 normally, otherwise even if pico2 is selected, the compiled firmware will still be suitable for pico
    Pico-vscode-21.JPG
    set(PICO_BOARD pico CACHE STRING "Board type")
    

Update extension

  1. The extension version in the offline package is 0.15.2, and you can also choose to update to the latest version after the installation is complete
    Pico-vscode-22.JPG

Arduino IDE series

Install Arduino IDE

  1. First, go to Arduino official website to download the installation package of the Arduino IDE.
    600px-Arduino下载2.0版本.jpg
  2. Here, you just need to select to download.
    仅下载不捐赠.png
  3. Once the download is complete, click Install.
    IDE安装水印-1.gif
    Notice: During the installation process, it will prompt you to install the driver, just click Install

Arduino IDE interface

  1. After the first installation, when you open the Arduino IDE, it will be in English. You can switch to other languages in File --> Preferences, or continue using the English interface.
    首选项-简体中文.jpg
  2. In the Language field, select the language you want to switch to, and click OK.
    600px-首选项-简体中文ok.jpg

Install Arduino-Pico Core in the Arduino IDE

  1. Open the Arduino IDE, click on the file in the top left corner, and select Preferences
    首选项-简体中文.jpg
  2. Add the following link to the attached board manager URL, and then click OK
    https://github.com/earlephilhower/arduino-pico/releases/download/4.0.2/package_rp2040_index.json

    RoArm-M1 Tutorial II05.jpg
    Note: If you already have an ESP32 board URL, you can use a comma to separate the URLs as follows:

    https://dl.espressif.com/dl/package_esp32_index.json,https://github.com/earlephilhower/arduino-pico/releases/download/4.0.2/package_rp2040_index.json
  3. Click Tools > Development Board > Board Manager > Search pico, as my computer has already been installed, it shows that it is installed
    Pico Get Start02.png
    Pico Get Start 06.png

First upload of the program

  1. Press and hold the BOOTSET button on the Pico board, connect the pico to the USB port of the computer via the Micro USB cable, and release the button after the computer recognizes a removable hard disk (RPI-RP2).
    Pico连接数据线.gif
  2. Download the program and open D1-LED.ino under the arduino\PWM\D1-LED path
  3. Click Tools --> Port, remember the existing COM, do not click this COM (the COM displayed is different on different computers, remember the COM on your own computer)
    UGV1 doenload02EN.png
  4. Connect the power board to the computer using a USB cable. Then, go to Tools > Port. For the first connection, select uf2 Board. After uploading, when you connect again, an additional COM port will appear
    UGV1 doenload03EN.png
  5. Click Tools > Development Board > Raspberry Pi Pico > Raspberry Pi Pico or Raspberry Pi Pico 2
    Pico Get Start02.png
  6. After setting it up, click the right arrow to upload the program
    Pico Get Start03.png
  • If issues arise during this period, and if you need to reinstall or update the Arduino IDE version, it is necessary to uninstall the Arduino IDE completely. After uninstalling the software, you need to manually delete all contents within the C:\Users\[name]\AppData\Local\Arduino15 folder (you need to show hidden files to see this folder). Then, proceed with a fresh installation.

Open source demos

MircoPython video demo (github)
MicroPython firmware/Blink demos (C)
Raspberry Pi official C/C++ demo (github)
Raspberry Pi official micropython demo (github)
Arduino official C/C++ demo (github)


Demo

C/C++ Demo

01-LCD

  1. LCD refreshes an image and waits for 2.5 seconds
  2. LCD refreshes GUI demo

02-picoprobe

  • This demo is based on the open-source program picoprobe
  • The RP2350-GEEK runs the picoprobe demo, which will emulate a USB TO SWD and USB TO UART device
  1. Using the UART interface as a USB to serial tool, it can be used for device communication
  2. Using the SWD interface as a debugging tool, when used with openocd, it can debug most ARM chips
  • For more information, please refer to the "PicoProbe Tutorial" below

03-FATFS

  1. The demo implements a command-line interface similar to busybox or DOS. It can mount a TF card, create and view files, and so on. The command “help” can be used to view all available commands
    600px-Geek-code-00.png
  • Note that the TF card file format is FAT32

Micropython Demo

01-LCD

How to use

  1. Upload all py and bmp files under the file to the RP2350-GEEK via thonny upload
    600px-Geek-code-01.jpg

Running result

  • LCD displays the GUI screen, waits for a few seconds, and then displays the bmp image

02-SD

How to use

  • Upload all py files under the file to the RP2350-GEEK via thonny and reset
    600px-Geek-code-02.jpg

Running result

  • After the RP2350-GEEK is reset, it will automatically mount the TF to the SD file according to the boot.py program
    600px-Geek-code-03.jpg
  • Double-click to open the SD folder, and you can see the files stored in the TF card
    600px-Geek-code-04.jpg

PicoProbe Tutorial

Install OpenOCD

Linux (and Raspberry Pi)

Download the dependency library

sudo apt install automake autoconf build-essential texinfo libtool libftdi-dev libusb-1.0-0-dev

Get and compile

git clone https://github.com/raspberrypi/openocd.git
cd openocd
./bootstrap
./configure
make -j4
sudo make install

Windows

  1. Because OpenOCD self-compilation is complicated in the Windows environment, it is recommended to use the compiled version
  2. Unzip and store in a shorter directory, such as directly in the C drive

Add environment variables

  1. Click on the Start menu and search for "Environment Variables"
    Debug-Probe-01.jpg
  2. Click on "Edit the System Environment Variables"
    Debug-Probe-02.jpg
  3. Double-click the "Path" variable to enter the editing interface
    Debug-Probe-03.jpg
  4. Add a new path
    Debug-Probe-04.jpg
    • ①Create a new variable address
    • ②Enter the address where the OpenOCD is stored
    • ③Click OK to save
  5. Click "OK" to save your changes
    Debug-Probe-05.jpg
  6. Restart the computer

Install GDB

Linux (and Raspberry Pi)

  1. Install gdb-multiarch
    sudo apt install gdb-multiarch

Windows

  1. If you have the pico-sdk environment installed correctly, skip this step, as GDB is already included in the Arm GNU Toolchain
  2. If you do not have pico-sdk installed, it is recommended to use the official pico installer to install it

Use Raspberry Pi Debug Probe to flash the program

  • Pico Debug Probe allows you to load binary files via the SWD port and OpenOCD
  • Every time you push a new binary file to Pico, you do not need to unplug and then hold down the BOOTSEL button
  1. Using RP2350 as an example, the flashing command is
    sudo openocd -f interface/cmsis-dap.cfg -f target/rp2350.cfg -c "adapter speed 5000" -c "p​​rogram {your elf file name}.elf verify reset exit”
  2. If you have a file named blink.elf in your current folder
    sudo openocd -f interface/cmsis-dap.cfg -f target/rp2350.cfg -c "adapter speed 5000" -c "p​​rogram blink.elf verify reset exit"

Use Raspberry Pi Debug Probe to debug the program

Open the OpenOCD server

  • You can use openocd in server mode and connect it to GDB, providing you with breakpoints and "correct" debugging
    • Using RP2350 as an example again, enter the following Linux command
      sudo openocd -f interface/cmsis-dap.cfg -f target/rp2350.cfg -c "adapter speed 5000"
    • In Windows PowerShell, enter the following command
      800px-Debug-Probe-06.jpg
      Starting to listen to the 3333 interface of this machine at this time indicates that the OpenOCD server has been successfully turned on

Use the GDB command line

  • This demo is built based on the pico-sdk environment, and the pico-example is compiled
  1. Open PowerShell and go to the corresponding build folder, here the blink demo is used as an example
    Debug-Probe-08.jpg
  2. Open GBD and enter the following command
    • If it is Windows, the input command is
      arm-none-eabi-gdb blink.elf
    • If it is Linux, the input command is
      gdb blink.elf
    800px-Debug-Probe-09.jpg
  3. Enter the following commands in sequence
    target remote localhost:3333
    load
    continue
    

    800px-Debug-Probe-07.jpg
    After successful execution, you can see pico executing blink, the led flickers

Debug with VSCode (Advanced)

  • Make sure that Open the OpenOCD server and Use the GDB command line are working properly
  • Make sure that the Pico compilation environment is set up properly
  • Make sure you have the following plugins installed on your VSCode
    1. Cortex-Debug
    2. Cmake-tools
    3. C/C++
  1. First open the OpenOCD server
    Debug-Probe-06.jpg
  2. Open the pico-examples folder with VSC and start the blink demo
  3. Use the shortcut key F1 and enter the following command
    open 'launch.json'
  4. Once opened, put the following in it
    Debug-Probe-11.jpg
    • If it is Windows, then enter
    {
        "version": "0.2.0",
        "configurations": [
            {
                "name": "Pico Debug",
                "type":"cortex-debug",
                "cwd": "${workspaceRoot}",
                "executable": "${command:cmake.launchTargetPath}",
                "request": "launch",
                "servertype": "external",
                // This may need to be arm-none-eabi-gdb depending on your system
                "gdbPath" : "gdb",
                // Connect to an already running OpenOCD instance
                "gdbTarget": "localhost:3333",
                "svdFile": "${env:PICO_SDK_PATH}/src/rp2350/hardware_regs/rp2350.svd",
                "runToMain": true,
                // Work around for stopping at main on restart
                "postRestartCommands": [
                    "break main",
                    "continue"
                ]
            }
        ]
    }
    
    • If it is Linux, then enter
    {
        "version": "0.2.0",
        "configurations": [
            {
                "name": "Pico Debug",
                "type":"cortex-debug",
                "cwd": "${workspaceRoot}",
                "executable": "${command:cmake.launchTargetPath}",
                "request": "launch",
                "servertype": "external",
                // This may need to be arm-none-eabi-gdb depending on your system
                "gdbPath" : "arm-none-eabi-gdb",
                // Connect to an already running OpenOCD instance
                "gdbTarget": "localhost:3333",
                "svdFile": "${env:PICO_SDK_PATH}/src/rp2350/hardware_regs/rp2350.svd",
                "runToMain": true,
                // Work around for stopping at main on restart
                "postRestartCommands": [
                    "break main",
                    "continue"
                ]
            }
        ]
    }
    
    • The difference between the two is that the gdb called is different
  5. Enter the Run & Debug interface with shortcut keys Ctrl+Shift+D
    Debug-Probe-12.jpg
    • ①Select Pico Debug as the debugger
    • ②Select CMake as debug mode
    • ③Start debugging button, shortcut key F5
    • ④Select blink as debugging object
  6. Click the debug button to enter the debugging mode, and the shortcut key is F5
    Debug-Probe-14.jpg
  7. The debugging toolbar appears
    Debug-Probe-15.jpg
    • ①Restart your device
    • ②Continue to run the program
    • ③Execute the next step
    • ④Enter function running
    • ⑤Exit function running
    • ⑥Stop debugging
  8. Click to continue running the program, using the shortcut key F5, you will see the pico running the blink program


Support




Technical Support

If you need technical support or have any feedback/review, please click the Submit Now button to submit a ticket, Our support team will check and reply to you within 1 to 2 working days. Please be patient as we make every effort to help you to resolve the issue.
Working Time: 9 AM - 6 PM GMT+8 (Monday to Friday)