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

[Feature Request] #6

Closed
HarvsG opened this issue Dec 2, 2022 · 6 comments
Closed

[Feature Request] #6

HarvsG opened this issue Dec 2, 2022 · 6 comments

Comments

@HarvsG
Copy link

HarvsG commented Dec 2, 2022

  1. Support PICO W
  2. label the LED with it's pin number - 32 for Pico W, (25 for Pico)
@lurch
Copy link
Contributor

lurch commented Dec 3, 2022

  1. The user-accessible GPIO pins on the Pico W are the same as for Pico. See https://www.raspberrypi.com/documentation/microcontrollers/raspberry-pi-pico.html
  2. The pin number for the LED on Pico W isn't 32 - instead it's controllable via the WiFi chip. See https://github.com/raspberrypi/pico-examples/tree/master/pico_w/blink

@Gadgetoid
Copy link
Collaborator

If I can get a good SVG for the front/back of the Pico W then it would be nice to add the option to switch between either-or. Even if that just hits different HTML pages.

I've raised #13 to ruminate about documenting extra pin functions, since I think these could be useful to surface outside of the datasheet(s). Granted I am keen to keep things clean.

Gadgetoid added a commit that referenced this issue Apr 24, 2023
Gadgetoid added a commit that referenced this issue Apr 24, 2023
@Gadgetoid
Copy link
Collaborator

Done: https://picow.pinout.xyz/

And done: https://pico.pinout.xyz/

Check "Advanced" in both cases to see the additional tables. I realise that the user LED isn't all that advanced on Pico, but I didn't want things to get too visually cluttered.

@lurch
Copy link
Contributor

lurch commented Apr 25, 2023

Doesn't seem 100% reproducible, but sometimes goes a bit funny when switching between the two sites? (Google Chrome on Linux)

Screenshot from 2023-04-25 22-20-57

@Gadgetoid
Copy link
Collaborator

That's the old CSS still lurking about in the cache, a bit of shift + F5 action usually clears it up. If it persists I might need to drop a cache-buster in the CSS URL for good measure 😆

There are only two really hard problems in programming:

  1. Naming things
  2. Cache invalidation
  3. Off by one errors

@lurch
Copy link
Contributor

lurch commented Apr 25, 2023

  1. Forgetting to start at index 0

This issue was closed.
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