-
Notifications
You must be signed in to change notification settings - Fork 769
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
blink does not blink on a Pico W #421
Comments
@aallan I've just had another look at Chapter 3 of https://datasheets.raspberrypi.com/pico/getting-started-with-pico.pdf and it has this boxout on page 9 |
Yes, I forget how we got into this situation. We should probably do something as it seems to be causing confusion. |
@repentsinner Thank you for opening this issue as I am a beginner and have just experienced what you described. I followed with the "Getting Started with Raspberry Pi Pico" document and assumed that the Pico and Pico W were the same except for the addition of the WiFi/BT chip. Panicked for a moment thinking I had a defective Pico W. |
This will be fixed in the next documentation release, where the two blink examples are explicitly addressed in the Getting Started book. |
The Pico W 'hardware hello world' (aka blink) out-of-the-box experience is terrible as of sdk-1.5.1.
Please add at least an additional
#warning if using a pico w, blink has moved to pico-examples/pico_w/wifi/blink
inpico-examples\blink\blink.c
. Preferred would be to updateblink.c
to include both the vanilla and W code paths. I suspect beginners to the Pico (W)(H) platform using the C SDK will be able to figure out what is going on, and it could be a good place to include some comments about other potential gotcha differences between the two boards.The official overview documentation has a few W-specific notes; none of them describe the moved LED. It is only section 3.8 of the Pico W datasheet that gets around to rather dryly describing this move that then might point someone in the correct direction in the examples directory:
While truly the LED is now connected to the wireless chip and therefore pedantically sample code for it should be in the
pico-examples/pico_w
directory somewhere, I highly doubt anyone looking forblink
cares about that distinction when looking for a first thing to run to figure out if their board is working at all. I strongly disagree thatpico_w/**/blink
should be underwifi
orbt
and the current location underwifi
is nonsensical; what makes the user LED more wifi-ey than bt-ey? If anything, per the data sheet andpico/cyw43_arch.h
, it should be inpico_w/cyw43/blink
.#350 has drifted off topic to somewhat address this, but it seems like a new issue is more appropriate.
It seems fine that other RP2040 boards may need different instructions for their fancy RGB LEDs or whatever; the Pico W is a first party board and IMO should work out of the box with the guidance in the Getting Started With Pico document.
Thanks for considering!
The text was updated successfully, but these errors were encountered: