Hi folks!
I am a little desperate with my project - maybe one of you has a good pointer for me?
Hardware setup:
I am using a ESP32 Devkit V1 - connected GPIOs:
i2c SCL 22
i2c Data 21
ACS712 sensor 39
HX711 Scale 3 SCK 35
HX711 Scale 3 DT 32
HX711 Scale 2 SCK 33
HX711 Scale 2 DT 25
HX711 Scale 1 SCK 26
HX711 Scale 1 DT 27
HX711 Scale 4 SCK 14
HX711 Scale 4 DT 16
GND
3v3 Power
Via I2C I have connected:
- SSD1306 oled
- MCP23017 I/O Expander
- tca9548 Multiplexer covering a bunch of BME280 and SHT31 sensors
My problem: I dont understand why I cannot esp_restart(); without ending up in a reboot loop. (see output below)
Only after uploading the sketch it seems to work - but not always.
I am using the latest arduino branch and flash QIO @ 80MHZ. When flashing an identical external ESP32 which is not soldered on my project - then it works directly, so I think I am using a PIN I shouldnt? The error message points me somehow to watchdogs - but I did not configure them anyhow.
What steps would you suggest to pinpoint the problem?
Output loop:
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:0x3fff0018,len:4
load:0x3fff001c,len:956
load:0x40078000,len:0
load:0x40078000,len:13256
entry 0x40078a90
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:0x3fff0018,len:4
load:0x3fff001c,len:956
load:0x40078000,len:0
load:0x40078000,len:13256
entry 0x40078a90
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:0x3fff0018,len:4
load:0x3fff001c,len:956
load:0x40078000,len:0
load:0x40078000,len:13256
entry 0x40078a90
ets Jun 8 2016 00:22:57
etc.
Boot Loop - forbidden PIN? Watchdog?
Re: Boot Loop - forbidden PIN? Watchdog?
After reading more literature, I got an idea: Maybe its all that timecritic bitbanging stuff going on for the HX711 scales... - while it looks for me as its "non blocking" code it seems to trigger that watchdog...
Who is online
Users browsing this forum: No registered users and 39 guests