Show HN: Interactive pinout for the Raspberry Pi Pico 2 (pico2.pinout.xyz)
I've been trying to make accessible and beautiful GPIO pinouts since I started one for the Raspberry Pi in 2013 [1]. I've since given the Raspberry Pi Pico [2] and Pico 2 [3] microcontrollers the same treatment when they launched.
Recently I've updated these with a new "Upside-down" view to complement the rear view, giving a pinout in the right orientation to match your project.
The Pico sites are all hand-coded single HTML pages with supporting CSS and minimal JS. They are set up to optionally install as a "Desktop" web app. They also degrade into a somewhat usable table in lieu of CSS and use vector graphics (for the board itself) to be viewable and printable at any size.
Finally, hidden behind "Advanced" is a pinout of the test pads and special function pins!
[1] - https://web.archive.org/web/20130505194305/pi.gadgetoid.com/... [2] - https://pico.pinout.xyz [3] - https://pico2.pinout.xyz
21 comments
[ 2.5 ms ] story [ 47.2 ms ] threadThanks for your pimoroni [1] work as well, I've used quite a few products and they're always easy to work with because of good software and examples.
[1] - https://shop.pimoroni.com/
Pico never quite has a function where it’s needed.
At least that's my main pain point when working with microcontrollers. They give you like 20 pins and you plan out all the functionality and then it turns out that one of those pins is like an EEPROM pin that needs to be low at boot or linked to something else internally or some shenanigans like that and the idea is actually completely impossible to implement (looking at you ESP32-CAM lmao). Or PWM channel conflicts that set some specific sets of pins to the same frequency and the like. It would be such a great workflow step to be able to verify if something would theoretically work given the known limitations at least.
Microcontrollers are like if a PC had 4 USB ports and if you used two of them the third and fourth just stopped working cause nobody intended all four to be used at the same time. Absolutely maddening.
I have definitely struggled with making the Pinout spinoffs discoverable- the OG site had ten plus years to bed in.
I keep a slightly modified version of it as a top comment in my main C file in every pico project. Super handy for quick reference and you can annotate it with the actual uses in your project.
ASCII-only really cuts to the meat of the problem though.
Bonus points if it could generate example initialisation code for the selected pins on the fly or maybe even an example snippet of code to get the peripheral going.
[1] https://deepbluembedded.com/arduino-uno-pinout/
I especially love the ability to flip and reverse things, since I try to avoid comparing any two objects in different orientations, to cut down on mistakes.
It would be really cool if the community had a more general purpose open standard interactive diagramming tool for this sort of thing.
I guess the easy way would be to mark up photographs with pin locations, which would map to pins in a table, allowing for multiple tables in a document.
I'm not sure how you'd capture the data in a way that could be rendered to something like a screen reader or a more abstract diagram though, without a lot of complexity and edge cases.
Would it be enough to just verbally describe the mapping between pin numbers and the physical layout, as in "Across then down, starting at upper left", or would you need a meta data scheme for that?