Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

pinout is wrong #18

Open
bablokb opened this issue Nov 8, 2023 · 5 comments
Open

pinout is wrong #18

bablokb opened this issue Nov 8, 2023 · 5 comments

Comments

@bablokb
Copy link

bablokb commented Nov 8, 2023

Comparing your pinout with the official pico-datasheet, your pinout labels some pins wrong:

  • GPIO20/21: pico-datasheet does not list them as UART
  • GPIO20: not a SPI-RX pin
  • GPIO26-28: no SPI pins

Not sure if this is complete or not...

@lurch
Copy link
Contributor

lurch commented Nov 8, 2023

I just checked, and the diagram at https://pico.pinout.xyz/ is in fact correct - if you look at the table on page 13 of https://datasheets.raspberrypi.com/rp2040/rp2040-datasheet.pdf you can see that the "errors" you list above are actually correct.

The pinout diagram in https://datasheets.raspberrypi.com/pico/pico-datasheet.pdf (and at https://www.raspberrypi.com/documentation/microcontrollers/raspberry-pi-pico.html#pinout-and-design-files ) chooses to omit the UART1 TX function from GP20 because GP23 isn't user-accessible on the Pico board, and so the "full set" of UART pins (TX, RX, CTS, RTS) on GP20-GP23 isn't user-accessible on the Pico. And similar logic explains the SPI pins you mention too.

@lurch
Copy link
Contributor

lurch commented Nov 8, 2023

It's not quite the same thing that you're asking, but see also raspberrypi/pico-feedback#193

@bablokb
Copy link
Author

bablokb commented Nov 8, 2023

This is a real pity and confuses users. The official datasheet does not list CTS/RTS at all, so omitting these pins does not make sense to me.

So maybe adding a note to https://pico.pinout.xyz/ might help? E.g. "This pinout also shows available functions not listed in the Pico Datasheet"?

@Gadgetoid
Copy link
Collaborator

Wait, we're more correct than the official documentation? NEVER! 😆

A little asterisk on unlisted functions and a footnote might work. Though I'm apprehensive to add too much clutter.

@lurch
Copy link
Contributor

lurch commented Nov 8, 2023

One person's "more correct" is another person's "overly verbose" 😉 🤷

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants