https://www.raspberrypi.com/news/raspberry-pi-pico-windows-installer/
and follow the directions. Let the installer put the install data in your Documents folder.
After installation you should see a 'Pico - developer power shell' app in the power shell window type 'code'. VScode should open.
- To test compile, download a project folder, perhaps the zip file from the Protothreads 1.3 page
- Remove the build folder, if any, and add back a new build folder.
- In the VS File->Open Folder menu item, ask VScode to select the project folder you downloaded.
- You may be prompted for a 'kit' or 'compiler' choose either 'Pico arm compiler' or 'let the project choose'
- You should see a bunch of messages, but the key messages are [cmake] -- Configuring done [cmake] -- Generating done
- Now click the 'build' button or type cntl-shift-B. the project should build, and if sucessful exits with condition code zero.
- The build folder should contain a file of type uf2. IF you hold down the button on the pico and cycle the power you should be able to drag the uf2 to the pico device.
The next section will describe a better download protocol.
-
The debugger allows easier program download (no power cycling or fiddling with switches), plus a hardware debugger.
see also https://www.circuitstate.com/tutorials/debugging-rp2040-pico-c-cpp-sdk-projects-using-raspberry-pi-debug-probe-and-vs-code/#SWD Connect the three wire SWD connector at the bottom of the board, plus the GPIO0 and GPIO1 pins as serial connection.
The U port on the Probe means UART, the D means DEBUG port. Using the modular connectors,
as supplied with the probe connect the U port yellow wire to GPIO0 and the orange wire to GPIO1.
zoomed image. Connect the D port orange wire to the let terminal of the SWD port (viewed with the
USB plug at the top), black to the middle, and yellow to the right.
Connect the debugger to the host machine. You should see a new serial device, if everything is working.
Now you should be able to program by
- changing the current directory in the power shell window to your current build diectory.
- Make sure the debugger is stopped. Menu item: Run->stop debugging
- Issue this command (with the name of your executable elf file) openocd -f interface/cmsis-dap.cfg -f target/rp2040.cfg -c "adapter speed 5000" -c "program graphics_test.elf verify reset exit"
- The target board should get new code, then reset and start.
During the normal test-edit-compile-run cycle, you will probably compile and download code as described above.
The general debug process will be
- IF necessary, edit the files in the .vscode folder for the project to match those below,
but change the name of the executable.The version I installed had to be edited, but yours might not.
If it does need editing, then you have to look into the .vscode folder in your project and hack three json files.- launch.json (image, file)
Launch.json controls how VScode starts the specific debugger you will use.
You need to tell VScode how to download, turn on openOCD, set some paths, then run the code. - tasks.json (image, file)
Tasks.json informs the launch process how to do certain tasks, particularly download code.
(called Flash in the code) - settings.json (image, file)
Settings.json sets up some general features of VScode.
I did not change anything in it.
- launch.json (image, file)
- Plug in the debugger and attach as shown above to the pico.
- Start VScode then Build the project (this is not automatic yet)
there should be an .elf file now in the build folder.
- Start the debugger using the triangle-debug icon on the far left.
(or by choosing menu Run->start debugging ) A small green arrow and pop-up menu should appear at the top of the left panel.
In the pop-up menu next to the green arrow, choose 'Pico-Debug (Cortex Debug)'.
A screenshot shows the triangle-debug (with a small blue disk on it),
the green arrow, and a pop-up menu in which Pico Debug is highlighted. - Clicking the green arrow should then download and start the program.
(or use menu Run->start debugging) you should see download messages, then after a few seconds the program should start running. - To set a breakpoint in the code, click on the extreme left column (left of the line number) of any line of source code. you may need to enable the breakpoint with a right-click
- When the code breaks, you should see local variables printed in the debug panel if you expand the variables tab. -- Expand the watch tab to add other variables, or hover the mouse over a variable in the code. -- use Run-> stop debugging when done.
- Stop debugging, edit, recompile, restart debugger. Repeat until you run out of coffee.
