-
Notifications
You must be signed in to change notification settings - Fork 51
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
Badger_OS v0.0.4 does not recognize 'WL_GPIO2' on Badger2040W #60
Comments
Hello! Seems like 'EXT_GPIO2' works for the VBUS sense pin with v0.0.4, but 'WL_GPIO2' does not - not sure why that might be 🤔 Paging @Gadgetoid ? |
Day late and a dollar short here, but I think this is a bug in MicroPython's CMakeLists here: We're supplying an explicit But the above code assumes I'll raise a patch for this, but it'll probably be a while before that fix makes its way to Badger. |
Okay after digging my way through multiple levels of code broken by bleeding-edge MicroPython I managed to produce a build and test that my fix actually works- thankfully it does:
If you really need "WL_GPIO2" (granted quite some time has passed since you raised this) then you can grab a test build here: But BEWARE this test build will trash your Badger filesystem. Even if you grab the one without Badger OS. It may also have multiple other bugs caused by bleeding edge MicroPython that we haven't yet found/fixed. |
It would be really great, if we could expect a newer version with updated python and fixed bugs. |
Newer version is imminent (I've been working on it this e... morning.. night?) and it will add The fix for this ended up being applied after MicroPython v1.23.0 was released 😭 so I ended up having to make a patch anyway. WIP is now in #75 |
Same code from #59 on same Badger2040W with Badger_OS v0.0.4 :
I personally find this one the more challenging output:
Did I mess something up or are the releases getting some "winter tuning" lately?
Need a towel?
The Hitchhiker
The text was updated successfully, but these errors were encountered: