-
Notifications
You must be signed in to change notification settings - Fork 7.6k
ESP32 board resetting again and again #7072
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
Comments
@Sureshbe - It sounds like your sketch is using one of the Flash assigned pins. Flash SPI QIO pins are: GPIO 6, 7, 8, 9, 10 and 11 GPIO 9 is used for the LED and set as OUPUT by the Sketch. In QIO mode, it will reset the board.#define LED 9
...
void setup() {
randomSeed(analogRead(0));
pinMode(LED, OUTPUT);
... |
I am not sure if using mode DIO solves the reboot. Isnt there still activity on this GPIO (2nd stage bootloader)? And if this is not the case, the are still electrical connected to flash and will end in issues when connecting additional hardware (led) here. |
I tested setting DIO, and I can use GPIO 9 and 10. |
Ahh yes, nice trap. All newer boards have connected the flash to GPIO 9 / 10. |
ESP32-S3-DEVKITC-1-N8I have the same issue when programming an ESP32-S3-DEVKITC-1-N8 v1.8 board. The only connection to the board is a USB cable connected to the UART port. CompileI compiled the BareMinimum example using : arduino-cli compile -b esp32:esp32:esp32s3 -v Used platform Version Path UploadI uploaded sketch using: arduino-cli upload -p /dev/ttyUSB0 --fqbn esp32:esp32:esp32s3 -v Leaving... ResultConnecting to the UART port with picocom reveals: ESP-ROM:esp32s3-20210327 Compiling with the arduino IDE yields the same result. |
@dbhaig i think same as #6980 (comment) |
Re. ArduinoIDE: (1) I note that you are trying to use the EEPROM before you have done an "EEPROM.begin(EEPROM_SIZE);" (2) I often get ESP32 "rst:0x8 (TG1WDT_SYS_RESET),boot:0x13 (SPI_FAST_FLASH_BOOT)" crashes when doing “EEPROM.commit” or similar EEPROM activities when other processes are using interrupts (both external interrupts and also internal timer-interrupts). [The solution for me was to specifically disable the offending interrupt before the crashing EEPROM activity.] Under these circumstances I have seen an EEPROM activity at the top of setup() causing repeated boot-crashes similar to the one shown above. (I have also seen the use of "SerialM.setDebugOutput(true)" causing the above crash on a subsequent “EEPROM.commit()” when an error message is generated from any other interrupt process during the “EEPROM.commit()” – in instances where removing the "SerialM.setDebugOutput(true)" is sufficient to allow the error-message (eg. “cam_hal: EV-EOF-OVF”) to be printing during the “EEPROM.commit()” without crashing it.) |
Same crash here with ESP32-S3, 16MB Flash. Not using SPI0 pins it seems. |
I have a related issue on a new PCB and what @Jason2866 says here does scare me a bit? According to the documentation from Espressif, the pins 6, 7, 8, 9, 10 and 11 are all perfectly good? But for modules with PSRAM, you must absolutely not use pins 35, 36 and 37 since that's connected to the PSRAM (at the end of section 3.2 in ESP32S3-WROOM-1 datasheet). In my case, that is what caused this (and lots of other issues). Or maybe the statement was for a very specific board? |
ESP32-S3 != ESP32 so the forbidden GPIOs are different. |
Thanks for clarifying @Jason2866 ! |
what can we do to resolve the issue of the serial monitor output rst:0x8 (TG1WDT_SYS_RESET),boot:0x13 (SPI_FAST_FLASH_BOOT) |
I had similar issue, ESP32 C3 ----- PROBLEM was that I tried to use wrong PIN numbers. I accidentally tried to use these pins on ESP32 c3 mini (some are not even wired out for usage, 18,23,16,4,5,17 in TFT_eSPI library as DIO pins. (Hate that User_Setup.h that you need to redefine for each ESP32-Screen combo). This gave me error: |
Bump |
I had something similar in my XIAO ESP32S3, I was really confused because I do not use "forbidden" pins. |
Hi, my 5 cents, for me this problem was if there is mismatch between past and new partition.csv and partition offset in menuconfig |
Board
ESP32 dev module
Device Description
ets Jun 8 2016 00:22:57
rst:0x8 (TG1WDT_SYS_RESET),boot:0x13 (SPI_FAST_FLASH_BOOT)
configsip: 0, SPIWP:0xee
clk_drv:0x00,q_drv:0x00,d_drv:0x00,cs0_drv:0x00,hd_drv:0x00,wp_drv:0x00
mode:DIO, clock div:1
load:0x3fff0030,len:1344
load:0x40078000,len:13516
load:0x40080400,len:3604
entry 0x400805f0
ets Jun 8 2016 00:22:57
rst:0x8 (TG1WDT_SYS_RESET),boot:0x13 (SPI_FAST_FLASH_BOOT)
configsip: 0, SPIWP:0xee
clk_drv:0x00,q_drv:0x00,d_drv:0x00,cs0_drv:0x00,hd_drv:0x00,wp_drv:0x00
mode:DIO, clock div:1
load:0x3fff0030,len:1344
load:0x40078000,len:13516
load:0x40080400,len:3604
entry 0x400805f0
ets Jun 8 2016 00:22:57
rst:0x8 (TG1WDT_SYS_RESET),boot:0x13 (SPI_FAST_FLASH_BOOT)
configsip: 0, SPIWP:0xee
clk_drv:0x00,q_drv:0x00,d_drv:0x00,cs0_drv:0x00,hd_drv:0x00,wp_drv:0x00
mode:DIO, clock div:1
load:0x3fff0030,len:1344
load:0x40078000,len:13516
load:0x40080400,len:3604
entry 0x400805f0
ets Jun 8 2016 00:22:57
rst:0x8 (TG1WDT_SYS_RESET),boot:0x13 (SPI_FAST_FLASH_BOOT)
configsip: 0, SPIWP:0xee
clk_drv:0x00,q_drv:0x00,d_drv:0x00,cs0_drv:0x00,hd_drv:0x00,wp_drv:0x00
mode:DIO, clock div:1
load:0x3fff0030,len:1344
load:0x40078000,len:13516
load:0x40080400,len:3604
entry 0x400805f0
ets Jun 8 2016 00:22:57
rst:0x8 (TG1WDT_SYS_RESET),boot:0x13 (SPI_FAST_FLASH_BOOT)
configsip: 0, SPIWP:0xee
clk_drv:0x00,q_drv:0x00,d_drv:0x00,cs0_drv:0x00,hd_drv:0x00,wp_drv:0x00
mode:DIO, clock div:1
load:0x3fff0030,len:1344
load:0x40078000,len:13516
load:0x40080400,len:3604
entry 0x400805f0
ets Jun 8 2016 00:22:57
Hardware Configuration
LoRa moduole connected to ESP32
Version
v2.0.4
IDE Name
ARDUINO IDE
Operating System
WINDOWS 11
Flash frequency
80MHZ
PSRAM enabled
yes
Upload speed
115200
Description
Board resetting again and again
Sketch
Debug Message
Other Steps to Reproduce
I tried on 2 more boards
I have checked existing issues, online documentation and the Troubleshooting Guide
The text was updated successfully, but these errors were encountered: