ESP32 PICO V3 - boot problems
Posted: Thu Apr 27, 2023 12:39 pm
Hello,
I am up to now using more than a few thousand WROOM32 and WROVER32 modules so far and now I am struggling with a simple problem, but I can not find the issue up to now in my hardware design.
The problem is simple:
-> Flashing the unchanged hello_world example to a custom ESP32 PICO V3 board works (see output later in this post)
-> Starting the module does not work (it hangs in a loop with RTCWDC_RTC_RESET) (see output later in this post)
What I have tried to far:
-> MTDI is floating to ensure 3.3V flash supply
-> burning the Fuse, that even if there is some bootstrapping problem to ensure 3.3V flash supply
-> trying a different 3.3V power
-> trying to disconnect every soldered peripheral like Display LEDs and switches
-> the same hello_world example flashed to one of our WROOM32 board or a DEV board comes up without any problems
Any ideas? I assume a simple stupid mistake, but I spent hours and meanwhile it is really nothing connected except the programming Pins and the EN lowpass.
It think about a powers supply issue, perhaps one bad soldered Pad or so, but what can cause this behaviour? (there are more than one Power Pins in that QFN, but if flashing works, so there it seems to be a connection to the embedded flash)
Thanks!
--------
FLASHING:
STARTING
I am up to now using more than a few thousand WROOM32 and WROVER32 modules so far and now I am struggling with a simple problem, but I can not find the issue up to now in my hardware design.
The problem is simple:
-> Flashing the unchanged hello_world example to a custom ESP32 PICO V3 board works (see output later in this post)
-> Starting the module does not work (it hangs in a loop with RTCWDC_RTC_RESET) (see output later in this post)
What I have tried to far:
-> MTDI is floating to ensure 3.3V flash supply
-> burning the Fuse, that even if there is some bootstrapping problem to ensure 3.3V flash supply
-> trying a different 3.3V power
-> trying to disconnect every soldered peripheral like Display LEDs and switches
-> the same hello_world example flashed to one of our WROOM32 board or a DEV board comes up without any problems
Any ideas? I assume a simple stupid mistake, but I spent hours and meanwhile it is really nothing connected except the programming Pins and the EN lowpass.
It think about a powers supply issue, perhaps one bad soldered Pad or so, but what can cause this behaviour? (there are more than one Power Pins in that QFN, but if flashing works, so there it seems to be a connection to the embedded flash)
Thanks!
--------
FLASHING:
Code: Select all
esptool.py v3.3.2
Serial port /dev/cu.usbserial-AI03K223
Connecting.......
Chip is ESP32-PICO-V3 (revision 3)
Features: WiFi, BT, Dual Core, 240MHz, Embedded Flash, VRef calibration in efuse, Coding Scheme None
Crystal is 40MHz
MAC: e8:9f:6d:13:4c:50
Uploading stub...
Running stub...
Stub running...
Changing baud rate to 460800
Changed.
Configuring flash size...
Flash will be erased from 0x00001000 to 0x00007fff...
Flash will be erased from 0x00010000 to 0x0003afff...
Flash will be erased from 0x00008000 to 0x00008fff...
Compressed 25520 bytes to 15995...
Writing at 0x00001000... (100 %)
Wrote 25520 bytes (15995 compressed) at 0x00001000 in 0.7 seconds (effective 289.6 kbit/s)...
Hash of data verified.
Compressed 172304 bytes to 91205...
Writing at 0x00010000... (16 %)
Writing at 0x0001b18b... (33 %)
Writing at 0x000209c3... (50 %)
Writing at 0x00026152... (66 %)
Writing at 0x0002e760... (83 %)
Writing at 0x00036a99... (100 %)
Wrote 172304 bytes (91205 compressed) at 0x00010000 in 2.5 seconds (effective 559.8 kbit/s)...
Hash of data verified.
Compressed 3072 bytes to 103...
Writing at 0x00008000... (100 %)
Wrote 3072 bytes (103 compressed) at 0x00008000 in 0.1 seconds (effective 380.0 kbit/s)...
Hash of data verified.
Leaving...
Hard resetting via RTS pin...
Done
Code: Select all
--- idf_monitor on /dev/cu.usbserial-AI03K223 115200 ---
--- Quit: Ctrl+] | Menu: Ctrl+T | Help: Ctrl+T followed by Ctrl+H ---
ets Jul 29 2019 12:21:46
rst:0x1 (POWERON_RESET),boot:0x13 (SPI_FAST_FLASH_BOOT)
configsip: 271414342, SPIWP:0xee
clk_drv:0x00,q_drv:0x00,d_drv:0x00,cs0_drv:0x00,hd_drv:0x00,wp_drv:0x00
mode:DIO, clock div:2
load:0x3fff0030,len:6664
load:0x40078000,len:14944
load:0x40080400,len:3816
0x40080400: _init at ??:?
entry 0x40080698
ets Jul 29 2019 12:21:46
rst:0x10 (RTCWDT_RTC_RESET),boot:0x13 (SPI_FAST_FLASH_BOOT)
configsip: 271414342, SPIWP:0xee
clk_drv:0x00,q_drv:0x00,d_drv:0x00,cs0_drv:0x00,hd_drv:0x00,wp_drv:0x00
mode:DIO, clock div:2
load:0x3fff0030,len:6664
load:0x40078000,len:14944
load:0x40080400,len:3816
0x40080400: _init at ??:?
entry 0x40080698
ets Jul 29 2019 12:21:46
rst:0x10 (RTCWDT_RTC_RESET),boot:0x13 (SPI_FAST_FLASH_BOOT)
configsip: 271414342, SPIWP:0xee
clk_drv:0x00,q_drv:0x00,d_drv:0x00,cs0_drv:0x00,hd_drv:0x00,wp_drv:0x00
mode:DIO, clock div:2
load:0x3fff0030,len:6664
load:0x40078000,len:14944
load:0x40080400,len:3816
0x40080400: _init at ??:?
- Bildschirmfoto 2023-04-27 um 14.15.15.png (55.42 KiB) Viewed 2384 times
