Custom board error

[seopyoon]

Hello Espressif,

I have made a new custom board. It is an updated version with more peripherals, such as colour sensor, etc. (It uses WROOM-32 module)

I am getting a new error. I do not know what may have gone wrong. I am consulting the circuit company, but in the meantime, your help is greatly appreciated.

First,
When I connect the board and look at terminal, I get,

Code: Select all

flash read err, 1000 

then repeats.

So, I try flashing, and I get,

Code: Select all

Warning: Could not auto-detect ...
Flash params set to 0x0220

A fatal error occurred: Time out waiting for packet content.

When I do efuse, I get:

Code: Select all

Security fuses:
FLASH_CRYPT_CNT        Flash encryption mode counter                     = 0 R/W (0x0)
FLASH_CRYPT_CONFIG     Flash encryption config (key tweak bits)          = 0 R/W (0x0)
CONSOLE_DEBUG_DISABLE  Disable ROM BASIC interpreter fallback            = 0 R/W (0x0)
ABS_DONE_0             secure boot enabled for bootloader                = 0 R/W (0x0)
ABS_DONE_1             secure boot abstract 1 locked                     = 0 R/W (0x0)
JTAG_DISABLE           Disable JTAG                                      = 0 R/W (0x0)
DISABLE_DL_ENCRYPT     Disable flash encryption in UART bootloader       = 0 R/W (0x0)
DISABLE_DL_DECRYPT     Disable flash decryption in UART bootloader       = 0 R/W (0x0)
DISABLE_DL_CACHE       Disable flash cache in UART bootloader            = 0 R/W (0x0)
BLK1                   Flash encryption key                              
  = 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 R/W 
BLK2                   Secure boot key                                   
  = 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 R/W 
BLK3                   Variable Block 3                                  
  = 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 R/W 

Efuse fuses:
WR_DIS                 Efuse write disable mask                          = 0 R/W (0x0)
RD_DIS                 Efuse read disablemask                            = 0 R/W (0x0)
CODING_SCHEME          Efuse variable block length scheme                = 0 R/W (0x0)
KEY_STATUS             Usage of efuse block 3 (reserved)                 = 0 R/W (0x0)

Config fuses:
XPD_SDIO_FORCE         Ignore MTDI pin (GPIO12) for VDD_SDIO on reset    = 0 R/W (0x0)
XPD_SDIO_REG           If XPD_SDIO_FORCE, enable VDD_SDIO reg on reset   = 0 R/W (0x0)
XPD_SDIO_TIEH          If XPD_SDIO_FORCE & XPD_SDIO_REG, 1=3.3V 0=1.8V   = 0 R/W (0x0)
SPI_PAD_CONFIG_CLK     Override SD_CLK pad (GPIO6/SPICLK)                = 0 R/W (0x0)
SPI_PAD_CONFIG_Q       Override SD_DATA_0 pad (GPIO7/SPIQ)               = 0 R/W (0x0)
SPI_PAD_CONFIG_D       Override SD_DATA_1 pad (GPIO8/SPID)               = 0 R/W (0x0)
SPI_PAD_CONFIG_HD      Override SD_DATA_2 pad (GPIO9/SPIHD)              = 0 R/W (0x0)
SPI_PAD_CONFIG_CS0     Override SD_CMD pad (GPIO11/SPICS0)               = 0 R/W (0x0)
DISABLE_SDIO_HOST      Disable SDIO host                                 = 0 R/W (0x0)

Identity fuses:
MAC                    MAC Address                                       = 24:0a:c4:05:15:a4 R/W 
CHIP_VERSION           Chip version                                      = 0 R/W (0x0)
CHIP_PACKAGE           Chip package identifier                           = 0 R/W (0x0)

Flash voltage (VDD_SDIO) determined by GPIO12 on reset (High for 1.8V, Low/NC for 3.3V).

Please any insight may be helpful in resolving the issue.
Thanks.

[WiFive]

What does it say for boot mode?

[seopyoon]

Sorry, boot mode?

When I connect the chip, I get,

Code: Select all

rst:0x10 (RTCWDT_RTC_RESET), boot:0x32 (SPI_FAST_FLASH_BOOT)
flash read err, 1000
Failing back to built-in command interpreter
OK

repeats.

[WiFive]

Yes boot mode is

Code: Select all

boot:0x32 (SPI_FAST_FLASH_BOOT)

This shows that gpio12/mtdi strapping pin is pulled up causing 1.8v on vdd_sdio but the wroom32 needs 3.3v so either pull it low or set efuse for 3.3v.

[seopyoon]

I had my GPIO12 pulled up, which caused the error.

(Please could someone let me know why that is the problem? GPIO12 is used for something on boot? I got the idea of pulling it down from a third party chip maker, https://cdn-learn.adafruit.com/download ... eather.pdf page 12)

Thanks.

[WiFive]

Esp32 datasheet section 2.4 strapping pins

[seopyoon]

Could it be pulled up after it boots? It seems to be okay when I try, but could it be a problem?

[WiFive]

It could be a problem if chip resets and it stays pulled up. Try efuse.