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

• The demo is based on the open-source program no-OS-FatFS-SD-SDIO-SPI-RPi-Pico

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
   
   

• 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
   
   

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
  
  

Running result

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

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
   • Click this link to download
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"
   
   
2. Click on "Edit the System Environment Variables"
   
   
3. Double-click the "Path" variable to enter the editing interface
   
   
4. Add a new path
   
   
   • ①Create a new variable address
   • ②Enter the address where the OpenOCD is stored
   • ③Click OK to save
5. Click "OK" to save your changes
   
   
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
   • Official download address
   • Offline package

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
    
    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
   
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

   
   
3. Enter the following commands in sequence

   target remote localhost:3333
   load
   continue
   

   
   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
   
   
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
   
   
   • 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
   
   
   • ①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
   
   
7. The debugging toolbar appears
   
   
   • ①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

Resources

Supporting resources

Document

• RP2350-GEEK Schematic diagram
  

Demo

• RP2350-GEEK Demo

Official Resources

Raspberry Pi official documents

• Pico2 Getting Started
• Pico2 C SDK User Manual
• Pico2 Python SDK User Manual
• RP2350 Datasheet

Raspberry Pi open source demos

• Raspberry Pi official C/C++ Demos (github)
• Raspberry Pi official micropython Demos (github)
• PicoProbe source code (GitHub)

FAQ

Support

Monday-Friday (9:30-6:30) Saturday (9:30-5:30)

Email: services01@spotpear.com