adafruit
WS 1.0.0-beta.84 fails on Adafruit ESP32-S3 Feather with 4MB Flash 2MB PSRAM
Describe the bug I tried to update .83 to .84 (via .uf2 drag-n-drop) and the device fails to boot afterwards, including a lack of COM port presenting to computer. Reverting back to .83 works as expected.
Arduino board Adafruit ESP32-S3 Feather with 4MB Flash 2MB PSRAM
Which components are connected to your device STH45
Desktop (please complete the following information):
- OS: Win11
- Browser: chrome
This issue is related to a bug within the ESP32 BSP on release 3.0.2. Beta 84 is based on this release.
https://github.com/espressif/arduino-esp32/issues/9936
@microfoundry Until Espressif adds and releases a patch for this issue, we have rolled back WipperSnapper to Beta 83. Well cut a new release (beta 85) when the BSP is patched and ready.
@microfoundry We just released Beta 85 which should patch the issue you're experiencing with the Adafruit ESP32-S3 Feather w/4MB Flash 2MB PSRAM.
Please try this new firmware and let me know if the issue persists
@brentru - Beta 85 loaded without issues. Good to go.
On a different topic, which just happened again before going to 85: If I have this same board running on battery and allow the battery to drain, the system will be toast. Removing the battery and connecting via USB only, I will not get a WIPPER drive nor connection to Adafruit IO, but the uf2 bootloader is still available. 2 for 2 times so far. Will test again.
I read me-no-dev's last comments posted, it opens up some interesting possibilities...
UPDATE: The battery drain/no run issue did not occur with v85, but was only a single test.
On a different topic, which just happened again before going to 85: If I have this same board running on battery and allow the battery to drain, the system will be toast. Removing the battery and connecting via USB only, I will not get a WIPPER drive nor connection to Adafruit IO, but the uf2 bootloader is still available. 2 for 2 times so far. Will test again.
This is surprising to me. What battery and board are you using to test this?
What battery and board are you using to test this?
The same Adafruit ESP32-S3 Feather w/4MB Flash 2MB PSRAM with Adafruit SHT45 sensor. And a generic 300mA Li-Ion cell
Hey Terry, can you just confirm if that feather board has the MAX17048 or the LC709203f lipo charger onboard (newer boards use the Max17048 but maybe old stock so do check). You can also just show the I2C address of the onboard battery charging device (from the wippersnapper device page click I2C Scan button) as that will equally tell us.
On Fri, 28 Jun 2024, 16:27 Terry Phillips, @.***> wrote:
What battery and board are you using to test this?
The same Adafruit ESP32-S3 Feather w/4MB Flash 2MB PSRAM with Adafruit SHT45 sensor. And a generic 300mA Li-Ion cell
— Reply to this email directly, view it on GitHub https://github.com/adafruit/Adafruit_Wippersnapper_Arduino/issues/595#issuecomment-2197178102, or unsubscribe https://github.com/notifications/unsubscribe-auth/ABTBZ4YHODK3UT4UCFP6XVLZJV6GNAVCNFSM6AAAAABJ7PTB3GVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCOJXGE3TQMJQGI . You are receiving this because you are subscribed to this thread.Message ID: @.*** com>
Ah brilliant thank you for confirming a suspicion. We had a similar issue with the MAX17048 and provided more generous error handling, but as there were no reports of the lc709203f I believe it was left untouched. Anyway that gives a good direction to head next week, so thanks again!
On Fri, 28 Jun 2024, 17:50 Terry Phillips, @.***> wrote:
Hi Tyeth - it's the LC709203f lipo charger.
— Reply to this email directly, view it on GitHub https://github.com/adafruit/Adafruit_Wippersnapper_Arduino/issues/595#issuecomment-2197304250, or unsubscribe https://github.com/notifications/unsubscribe-auth/ABTBZ45W2KU4M32DEYATLUDZJWH4TAVCNFSM6AAAAABJ7PTB3GVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCOJXGMYDIMRVGA . You are receiving this because you commented.Message ID: @.***>
@microfoundry I am closing this stale issue due to inactivity. If you are still experiencing this functionality/behavior, please let us know and I'll re-open this issue to investigate.