ESP32DEV board stuck in RTCWDT_RTC_RESET reboot after fresh PlatformIO install #8835
Comments
|
Unless you are saying that a Hello World sketch causes this, you need to provide your code. Something in your initialization is blocking the cpu. |
|
I think it is related to the partition scheme. There was no code change, all I had done was build a new PC after mine had died and I wasn't able to get any of my modules to boot up. I didn't recall the Espressif32 version I had previously. It turns out this is a common issue with Release 6.4.0 as I came across references to this reboot loop on the PlatformIO forum. The workaround is to pin it at 6.3.2 This was the issue from another project that provided the version pin suggestion. |
|
I would normally say let's try to fix it instead of workaround, but 3.0.0 will be out soon, and will have a whole new set of migration issues. |
|
I agree a fix would be better. As I have a commercial product that is being rolled out, I just don't have time to try and find the root cause. I'll revisit the 6.4.0 release at some point and see if I can offer any more insights. I did create a simple blink sketch using the same partition scheme and it did work using the 6.4.0 release. I use tasks and RTOS in my commercial code base and one of the issues I found while trying to figure out the issue, mentioned something about the CPU being maxed out and not servicing the IDLE-task. |
Board
ESP DEV Module
Device Description
esp32dev board which is being used to run a generic module with ESP32-WROOM-32 module
Hardware Configuration
No external connections
Version
v2.0.11
IDE Name
PlatformIO
Operating System
Windows 11
Flash frequency
40MHz
PSRAM enabled
yes
Upload speed
115200
Description
I've got a code base about 2 years old which has been working fine. I just installed fresh install of PlatformIO and VS Code on a new Windows PC. Although the project builds and outputs the bin file, the command line has all the supporting files as usual, the binary once released to an ESP32 Dev module fails to run and just emits the RTCWDT_RTC_RESET in a continuous cycle. Only when I take a binary built on the old PC and flash the device does it work as it did before:
I am using min_spiffs.csv
Command line release
Build and Release
Reset cycle ad infinitum
ets Jun 8 2016 00:22:57
I have tried different boards, erasing the flash and using the Espressif Download tool as an alternative to PlatformIO just to try but the problem seems to be that the offsets in the binary are incorrect or something has changed that seems to have broken the release binary.
Any suggestions greatly appreciated. I'm stuck on this one for the last 24 hours without being any closer to a resolution.
Sketch
The most relevant would be to use the partitions configuration as this seems to be most relevant: [env:esp32dev] board_build.partitions = min_spiffs.csv platform = espressif32 board = esp32devDebug Message
Other Steps to Reproduce
I see I have v2.0.11 of the ESP32 Arduino framework and have tried updating the platform, so not sure how I can get the latest version as running the "pio update" command indicates everything is up to date.
I am using the standard build and release workflows that PlatformIO provides. The code compiles, the bin and supporting files are created and the release step deploys the code. But the device does run the deployed code and stays stuck in this reset cycle. Using a binary created a few weeks ago and uploading using the same commands that are issued by the PlatformIO release workflow results in working device.
I tried a fresh installation on my laptop and the result is the same, the device does not start:
I have checked existing issues, online documentation and the Troubleshooting Guide
The text was updated successfully, but these errors were encountered: