-
-
Notifications
You must be signed in to change notification settings - Fork 16
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
Xiao RP2040 support? #17
Comments
If the software is just utilizing the pins as gpio, would gpio pin 7 in the software not still translate to gpio pin 7 regardless of the board? |
I think my brain just caught up with my project. Consider this closed and I'll report back. |
Xiao-rp2040 pin names don't directly match. But using gpio7 is the same for all, but you have to check where that pin is connected to which pin. |
I understand. Working on implementation now
…On Mon, May 20, 2024, 1:57 AM Shalx ***@***.***> wrote:
If the software is just utilizing the pins as gpio, would gpio pin 7 in
the software not still translate to gpio pin 7 regardless of the board?
Xiao-rp2040 pin names doesnt directly match. But using gpio7 is the same
for all, but you have to check where that pin is connected to which pin.
—
Reply to this email directly, view it on GitHub
<#17 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/BDYL4VH5BZRXMPMO5NQCIQLZDGNGTAVCNFSM6AAAAABH67Y5YKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCMJZG44TOMJXGQ>
.
You are receiving this because you modified the open/close state.Message
ID: ***@***.***>
|
Would this be possible at all? Looking at this image, it appears that all required pins are there except for pin7 for 1.6 D0. Could that signal be found elsewhere on the Xiao?
The text was updated successfully, but these errors were encountered: