ESP32-MINI-1 Module

[libusbdotnet]

I'm looking for information on the embedded flash memory speed for the ESP32-MINI-1 Module. My M1 devkit says that it is running in DIO mode when it boots. Is this really true? I would expect the embeeded flash to operate in QIO mode.

Code: Select all

spi_flash: detected chip: generic
spi_flash: flash io: dio

[ESP_Sprite]

It's something you can set in menuconfig, under 'serial flasher settings' if memory serves. We default to dio as that works on most setups, but there's nothing stopping you from selecting qio mode there.

[libusbdotnet]

I'm aware of this and I have tried it. When I select QIO it can't load the partition table:

rst:0x3 (SW_RESET),boot:0x13 (SPI_FAST_FLASH_BOOT)
configsip: 188777542, 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:7368
load:0x40078000,len:14956
ho 0 tail 12 room 4
load:0x40080400,len:4404
entry 0x40080694
I (29) boot: ESP-IDF v4.3-rc-2-g88c2b69c6-dirty 2nd stage bootloader
I (29) boot: compile time 08:23:05
I (29) boot: chip revision: 3
I (34) boot_comm: chip revision: 3, min. bootloader chip revision: 0
I (41) qio_mode: Enabling default flash chip QIO
I (46) boot.esp32: SPI Speed : 40MHz
I (51) boot.esp32: SPI Mode : QIO
I (55) boot.esp32: SPI Flash Size : 4MB
I (60) boot: Enabling RNG early entropy source...
E (65) flash_parts: partition 0 invalid magic number 0x44ce
E (72) boot: Failed to verify partition table
E (77) boot: load partition table error!

Considering it runs code from the embedded flash, it really needs to operate as fast as possible.

I am using the ESP-IDF 4.3 release branch if that makes a difference. I purchased this dev board from Digikey:
https://www.digikey.com/en/products/det ... 1/13532113

[ESP_Sprite]

Interesting, it's not supposed to do that. And there's nothing otherwise connected to the devboard? (Something to specifically watch out for is that 'CMD' and 'GND' can look the same on silkscreen.) Do you happen to have a 2nd devboard to try this on?

[libusbdotnet]

I actually had 2 problems:
#1:
Yes, I do have other things connected. Most importantly, the JTAG pins are connected to an ESP-PROG. When I plug the dev board in without anything else connected it does indeed work in QIO mode using Visual Studio Code. Thanks for that.

I assumed that since the flash is actually embedded into the SOC that it would always use the correct flash voltage. I was wrong..

I have since burnt the efuses to permanently set VDD_SDIO to 3.3v and now it works with JTAG connected. (Using Visual Studio Code)

#2:
I was using the VisualGDB plugin for Visual Studios and there is something in it specifically that is creating the partition load error. It is a separate, unrelated problem to the GPIO12 strapping pin. Oddly it is still only when I try and use QIO mode. I am yet to resolve this issue.

The main difference I see between the two is in Visual Studio Code, I am using the IDF master development branch. In VisualGDB, I am using the 4.3 release branch.

I appreciate your help!

Regards,
Travis