I am the proud owner of a Raspberry Pi Pico which is a dinky microcontroller from the lovely people at Raspberry Pi. I also have the RGB Pico Keypad Base, because my husband was buying something else from Pimoroni (3D printer filament, more on that another day) and we love them and … here we are 🙂
I’ve tried to write down and link to the stuff I found useful along the way with this project, in case it helps you too. Well, no, really so I can come back to it next time I’m using one of these!
The Picos ship without the legs soldered on, so that was step 1. There’s some good info in the Pimoroni getting started tutorial for pico but I would also recommend the How to solder pins to your RPi Pico article from Tom’s Hardware, it was a lot like having @biglesp actually here to help me!
Tl;DR put the legs into a breadboard and then solder the board on top, that way everything is aligned correctly.
I used the custom firmware from Pimoroni because I needed the library for the RGB keypad. To add the firmware, connect the chip to your computer in bootloader mode (hold down the button when you connect and for another couple of seconds) and it will appear as USB storage. Put the firmware
.uf2 file into the USB storage and it will reboot itself.
A lot of the tutorials suggest something called Thonny but I’m a software developer with accessibility needs, so I steered clear of that. Instead, I used a neat tool called rshell which you can install via
pip. It is designed for micropython and has a repl and some file handling features; I found it did everything I needed.
One thing to look out for is that the current release
0.0.28 seemed to be a little bit strange about both its default values and it had some problems with file uploads just hanging on particular files. However, it’s an active project and the
pico branch worked like a charm. Clone the repo, check out the branch, and use
r.py in place of your usual rshell command. This information will probably be outdated quite quickly though so it’s just here in case it helps.
rshell with your pico already attached:
When it starts, it’ll tell you what it thinks your board is called, probably
pyboard, in which case the files on the device will appear as being in the path
/pyboard/. The RPi Pico runs
main.py when it boots, and you can copy it up with a command like:
The Raspberry Pi Pico DataSheet has some excellent information about getting set up and connected, and also has some good examples. It looks like a serious document but the “Say Hello World” and the “Blink an LED” section should work with any repl and any Pico.
Ctrl+xto exit the rshell repl. It does helpfully point this out when it starts, but of course that’s not the moment when you need the info.
Actual Development Cycle
I find with a lot of hardware projects that I can get to “hello world” quite quickly but then there’s a whole cycle of ejecting the disk or attaching to get debug output that makes the feedback loop pretty tedious. With
rshell I am using this one-liner after each time I’ve saved my
'~' off the end if you want to keep the repl active and watch the debug output.
Mini Memory Game (The Actual Software)
This bit is the most fun because it’s when the lights light up and there are buttons to press 🙂
I made a game! It works like this:
- A pattern of lights is shown for a few seconds
- The lights are shuffled around the board
- The user presses pairs of buttons to swap lights over until the lights match the first pattern
- You win! Press the flashing green button in the corner to get the next level
Posting all the code into a blog post doesn’t seem that useful so instead, check out my GitHub repo of fun RPi Pico things.
There are a bunch of other resources that I found useful:
This Raspberry Pi Pico is a very different beast from the traditional approach of a tiny linux computer, and is more like the ESPs that I’ve used before. But they’re quite approachable and MicroPython is fairly friendly to code with as well, so I’m looking forward to hearing what everyone is making!