Document GPIO23, 24 and 25

[Gadgetoid]

Something of a dupe of #6 except it's a different approach.

Might be handy to have an addendum at the bottom of the page, a small table that covers these additional pins and their functions. This could include the SWD pins for #7

• GPIO23 is connected to the PS pin of the onboard RT6150B-33GQW, if it's LOW (default) it's in PFM mode for best efficiency, if it's HIGH it's in PWM mode for improved ripple but worse efficiency at light loads. See: https://datasheets.raspberrypi.com/pico/pico-datasheet.pdf#pico-schematic-diagram

• GPIO24 is the VBUS sense pin, if VBUS (either via USB, or the VBUS pin) is present then it's HIGH, otherwise LOW.

• GPIO25 on Pico is the USER LED, and on Pico W it's the wireless SPI chip-select. See: https://datasheets.raspberrypi.com/picow/pico-w-datasheet.pdf

[lurch]

Yeah, see also section 2.1 of https://datasheets.raspberrypi.com/picow/pico-w-datasheet.pdf

[samveen]

Slightly related, but not much, maybe separate out the PiCow into it's own correl at picow.pinout.xyz ??

[lurch]

maybe separate out the PiCow

Isn't that what #6 is about? Just out of curiosity, what specific difference between the Pico and Pico W do you think needs clarifying?

[samveen]

@lurch The board layout of the 2 is different (not the pins, but the components), so it might be a tad disconcerting for newbie users (who are probably the primary target audience of pinout), and thus leading to extra time wasted in figuring things like the location of the debug headers being a cosmetic change. I spent an hour extra verifying that the pico pinout, and that's one hour I'm not getting back.

[lurch]

I'm surprised to hear that it took you a whole hour - did you look at https://www.raspberrypi.com/documentation/microcontrollers/raspberry-pi-pico.html ?

[samveen]

No, I didn't . I do wish google had given me this result first. I was muddling through comparing multiple pinout diagrams on the datasheets subsection of the raspi website.

[Gadgetoid]

I’m not opposed to a PicoW version of the site for clarity. Now that I’ve moved the JS and CSS to separate files it’s rather less onerous to maintain multiple variations. I really should distill the pin details to some database format and generate the HTML from that, though.

I’m not sure how easy it would be to convince Google to serve the right version, but we can - at least - interlink the two. They might also need to be subfolders rather than subdomains to more easily support installation as a PWA and preserve the ability to view each respective board offline. Though I guess two separate PWA’s for separate boards (ie: two icons on your desktop or phone) is a nice separation of concerns?

[samveen]

I should probably apologize for my little side comment about a variant sub-site for the Pico W hijacking this issue .

Given that the search term combination for 'pinout+pico' already lead to the correct location with Google, I'm expecting a new subdomain like picow.pinout.xyz will be among the top results for 'pinout+pico+w' very quickly, if interlink from the pico page.

[Gadgetoid]

I've cleared the first hurdle- getting front/back SVG files for the Pico W which are here:

https://raw.githubusercontent.com/pinout-xyz/pico.pinout.xyz/pico-w-prototype/raspberry-pi-picow.svg

and here:

https://raw.githubusercontent.com/pinout-xyz/pico.pinout.xyz/pico-w-prototype/raspberry-pi-picow-underside.svg

Edit: Live example https://pico.pinout.xyz/picow.html

GitHub pages can only serve a single subdomain, maybe I'll just forego complexity and copy this repo to host the W version.

[Gadgetoid]

And through the magic of just forking this whole repository and setting up another CNAME: https://picow.pinout.xyz/

Now I guess we've got that distraction out of the way, might do well to actually add these extra documentation tables somehow 😆

[Gadgetoid]

And - if we're adding a whole new table - I don't think it would be unreasonable to link to the respective documentation and datasheets for both boards? ... at least somewhere

[samveen]

Thank you.

[Gadgetoid]

Okay, I've rolled out some extra labels for the debug pins and a little table documenting GP23, GP24 and GP25 as noted above, plus GP29 and ADC4 which I had missed.

[Gadgetoid]

And on the Pico W side of things:

[samveen]

Some formatting issues crop up in Firefox 112.0.1 ((x)Ubuntu 20.04) as below:

[lurch]

#6 (comment)

😉