-
Notifications
You must be signed in to change notification settings - Fork 296
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
Pin Viewer is unable to show GPIO 23, 24, 25, 29 #871
Comments
@CapnHawke are all of those pins assigned to addons elsewhere in the config? |
CORRECTION: I just reviewed my original post. Please forgive my bad memory. Given that part of my process for pin 23 was to assign it to an input, I assume I had released the USB host. The video showing the button working (assigned to up) used pin 23. I think that would only be possible if Pin 23 had been released. /Correction As to pin 25, I am unsure how to best answer the question. Pin 25 looks to be mapped to the On-Board LED in the add-on configuration menu. I have not found a way to select any other pin, or to release the pin assigned to that function. Unlike other add-ons, there is not a field available to enter a pin number. I first experienced this issue nine days ago, and I do not remember whether I was experiencing it at a time when the On-Board LED addon was enabled or disabled. So I tested again today. Pin 29 was not and never has been mapped to an add-on while experiencing this issue. Today's test:
|
If you reboot the webconfig mode after step 6, does that make 23 and 24 work in the pin mapper? |
Just ran through the steps from the beginning, saved, and rebooted into web config after step 6. Pin viewer still does not show these pins. To be clear, the pins do function. |
Odd, but we'll continue to investigate. |
I have an update on this, isolating the issue.
It appears that the pin viewer is unable to detect pins 23, 24, 25, and 29, when they are not mapped to a function in the pin mapper. However, the pin viewer is able to detect other unmapped pins. For example, pins 26, 27, 2, and 3 can all be detected even when they have no assignment to any function. |
I wanted to add more buttons to my hitbox, thinking 23,24,25 are available, but they are not. after looking into it for a while led me to this: from the schematics posted there, GPIO23,24,25,29 all have hardware purpose and are thus wired differently for their purpose, the current firmware shows pin 25 as customisable, rest as addons, but thats most likely not true as you won't be able to connect a button to 25 |
You may simply need a different PCB. The schematic for the PCB being discussed in this issue is pictured here. The buttons which have been mapped to these pins function just fine. They also show up in the pin viewer after they have been assigned to an input. The sole issue is that while these pins are not assigned, they are not visible to the pin viewer while other pins are. |
I am only using the standard pico board i can't find the wiring diagam for the breakout board, thus cannot confirm if they share these uses |
GPIO 25 can be used for other things too. I suggest we leave the "issue" alone and you can join the GP2040-CE discord if you are interested in learning more about what your basic pico can do, and what the RP2040 Advanced Breakout Board (and its revisions) can do. The capabilities of these boards are maybe a discussion better had somewhere else. Same with your controller. |
Prerequisites
Please check the following before posting an issue / bug report.
Context
Expected Behavior
When using the Pin Viewer function at http://192.168.7.1/pin-mapping I expect the pin viewer to confirm whenever a GPIO pin connects to ground/a button is pressed.
Current Behavior
When using the Pin Viewer function, the pin viewer displays the pin corresponding to the pressed button, except for GPIO 23, 24, 25, and 29. For each of those four pins, the pin viewer times out waiting for an input and it appears that any button presses occurring on those pins simply do not register.
Steps to Reproduce
Repeat the steps above for pins 23, 24, 25 (with the LED slide switch configured correctly), and 29.
Screenshots & Files
Video of the pin mapper failing to register on Pin 23: https://cdn.discordapp.com/attachments/1049370387563163731/1212664412083716107/Pin_viewer_failure.mp4?ex=65f2a8be&is=65e033be&hm=01bc576ea0be3e621fa0347b5da4405ee5b4e538a93b1cfb24b62851dad12e42&
Video of the button press succeeding notwithstanding that the pin is invisible to the Pin Viewer:
https://cdn.discordapp.com/attachments/1049370387563163731/1212664506820329492/Button_press_success.mp4?ex=65f2a8d4&is=65e033d4&hm=52705a5b0dfbd714d712e0f3c0bd175e10332740a8fd4c997bb14f95b5905105&
The text was updated successfully, but these errors were encountered: