-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
Update to IDF 5.3 #9526
Update to IDF 5.3 #9526
Conversation
The Funhouse problem was due to a locking change for SPI. The Funhouse is one of a few boards with DotStar status LEDs that use SPI and have this bug. I thought it might be IDF related so I updated it first. :-) Fixes micropython#9486
A few boards disable the "main" component I thought would indicate if a chip had a peripheral.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Testing:
Metro ESP32-S3: simple BLE and WiFi HTTPS requests worked fine.
FunHouse: originally I couldn't get it to come up with serial or CIRCUITPY. I erased the FunHouse and reloaded the UF2 bootloader, and at first it was fine. But then it failed again. To reproduce, erase and load .bin, or load TinyUF2 and the .uf2. It will come up, but if you do import wifi
, it hangs or crashes, with no output. If a settings.toml is present, the status line will come up with No IP
, and again, no serial or CIRCUITPY, indicating a crash or hang.
More testing: Metro ESP32-S2: this has the same ESP32-S2 WROVER module as the FunHouse. Erased completely, loaded .bin. So again the problem seems to be FunHouse specific. I could go ahead and merge this and you could keep working on FunHouse, if that makes sense. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The Funhouse problem was due to a locking change for SPI. The Funhouse is one of a few boards with DotStar status LEDs that use SPI and have this bug.
I thought it might be IDF related so I updated it first. :-)
This was meant to fix #9486, but it doesn't however, it has other useful fixes.