ESP32-C3-DEVKITM-1 continously resetting

[silbstep]

Hi, I have a ESP32-C3-DEVKITM-1 and use PlatformIO running on Visual Studio Code, I am using the ESP-IDF framework. The devkit successfully programs but when running continuously resets with the following messages:
rst:0x7 (TG0WDT_SYS_RST),boot:0xc (SPI_FAST_FLASH_BOOT)
Saved PC:0x40049a42
SPIWP:0xee
mode:QIO, clock div:1
load:0x3fcd6100,len:0x181c
ets_loader.c 78
ESP-ROM:esp32c3-api1-20210207
Build:Feb 7 2021
rst:0x10 (RTCWDT_RTC_RST),boot:0xc (SPI_FAST_FLASH_BOOT)
SPIWP:0xee
mode:QIO, clock div:1
load:0x3fcd6100,len:0x181c
ets_loader.c 78
ESP-ROM:esp32c3-api1-20210207
Build:Feb 7 2021

At the moment I have just used a simple program that toggles an io port. As a test I tried programming the device in the Arduino IDE and it both programs and then runs properly.

Any help and suggestions would be greatly appreciated.

[silbstep]

Ok sorted out why this was happening, use dio for the flash by putting the following into the .ini file: board_build.flash_mode = dio it looks like qio is the default as this line must be in otherwise the boot loop occurs.

[jkingdon]

Thanks @silbstep, this was driving me nuts!

[bobolink]

I’m just wondering how you are connecting to the ESP32-C3 Dev Kit and debugging with Visual Studio Code and PlatformIO. And what OS.

I filled this PlatformIO issue because I couldn’t get that setup to work without wiring up a separate USB connector.
https://github.com/platformio/platform- ... issues/651

Thanks

[jkingdon]

I’m just wondering how you are connecting to the ESP32-C3 Dev Kit and debugging with Visual Studio Code and PlatformIO. And what OS.

I filled this PlatformIO issue because I couldn’t get that setup to work without wiring up a separate USB connector.
https://github.com/platformio/platform- ... issues/651

Simple compile/flash/monitor functions seem to be working fine (now) with just the standard usb connection. I had to force the rtc/dtr lines on the monitor to allow it to run. I haven't tried debugging yet, I assume this will need a jtag debugger wired up. The toolchain does seem very slow to build even trivial projects though. Much slower than the toolchain for the gd32v.

Code: Select all

board_build.flash_mode = dio
monitor_rts = 0
monitor_dtr = 0

[bobolink]

I assume this will need a jtag debugger wired up

Yeah, I was trying to avoid buying a separate jtag J-Link type debugger and tried this:
https://dspobjects.com/2021/10/20/esp32 ... debugging/
Based on this:
https://docs.espressif.com/projects/esp ... nsole.html

I got it working but not through PlatformIO, thus the GitHub issue. And I’m not sure how VSCode figured it all out—which scares me a little.

[bobolink]

The USB Debugging interface is described in 21.3 of
https://www.espressif.com/sites/default ... #iomuxgpio
Mostly it's blah, blah, blah but of interest:
... which may happen in Light Sleep. Additionally, the USB serial/JTAG Controller (as well as the attached RISC-V CPU) will be entirely powered down in Deep Sleep mode. If a device needs to be debugged in either of these two modes, it may be preferable to use an external JTAG debugger and serial interface instead.