I've assembled my first prototype ESP32 PCB and cannot get my code to boot up. I have a ESP32D0WDQ5 installed and I am able to successfully flash my code with an FTDI serial cable:
Code: Select all
Connecting........__
Chip is ESP32D0WDQ5 (revision 1)
Features: WiFi, BT, Dual Core, 240MHz, VRef calibration in efuse, Coding Scheme None
Crystal is 40MHz
MAC: 98:f4:ab:13:b9:1c
Uploading stub...
Running stub...
Stub running...
Configuring flash size...
Auto-detected Flash size: 16MB
Compressed 8192 bytes to 31...
Wrote 8192 bytes (31 compressed) at 0x00016000 in 0.0 seconds (effective 4103.1 kbit/s)...
Hash of data verified.
Flash params set to 0x0240
Compressed 28672 bytes to 16937...
Wrote 28672 bytes (16937 compressed) at 0x00001000 in 1.5 seconds (effective 151.0 kbit/s)...
Hash of data verified.
Compressed 931344 bytes to 571439...
Wrote 931344 bytes (571439 compressed) at 0x00020000 in 50.7 seconds (effective 146.9 kbit/s)...
Hash of data verified.
Compressed 3072 bytes to 127...
Wrote 3072 bytes (127 compressed) at 0x00010000 in 0.0 seconds (effective 782.6 kbit/s)...
Hash of data verified.
Leaving...
Hard resetting via RTS pin...
Code: Select all
D (54) boot: spi_mode 02
D (56) boot: spi_speed 00
D (58) boot: spi_size 04
I (61) boot: SPI Speed : 40MHz
I (64) boot: SPI Mode : DIO
I (67) boot: SPI Flash Size : 16MB
D (70) bootloader_flash: mmu set paddr=00010000 count=1 size=c00 src_addr=10000 src_addr_aligned=10000
D (79) boot: mapped partition table 0x10000 at 0x3f400000
E (84) flash_parts: partition 0 invalid magic number 0x0
E (89) boot: Failed to verify partition table
E (93) boot: load partition table error!
ets Jun 8 2016 00:22:57
Code: Select all
python /home/c32958/esp/esp-idf/components/partition_table/parttool.py --partition-table-offset 0x10000 get_partition_info --table ppp
Code: Select all
python /home/c32958/esp/esp-idf/components/partition_table/gen_esp32part.py ppp
Code: Select all
# Espressif ESP32 Partition Table
# Name, Type, SubType, Offset, Size, Flags
nvs,data,nvs,0x12000,16K,
otadata,data,ota,0x16000,8K,
phy_init,data,phy,0x18000,4K,
ota_0,app,ota_0,0x20000,1500K,
ota_1,app,ota_1,0x1a0000,1500K,
I would welcome any ideas or pointers on how to diagnose this.
-Chris