eFuse factory already wrote

User avatar
urbanze
Posts: 267
Joined: Sat Jun 10, 2017 9:55 pm
Location: Brazil

eFuse factory already wrote

Postby urbanze » Thu Jan 30, 2020 3:49 pm

Hello! I want to know about de chances of eFuses become burned from de factory :lol:

In this week, I'm uploading all boards from my job and in process to burn flash key, tool tell's about already value in keys.

See, Flash key and Block 3 has 0xFF bytes wrote, and I never get, in my hands, this esp32 before (factory new). How? Why? I need to burn this flash key :(

ps: This not happened on all the boards I uploaded until today (~30), just one.

Code: Select all

python ~/esp/esp-idf/components/esptool_py/esptool/espefuse.py --port /dev/ttyUSB0 summary
espefuse.py v2.6
Connecting...
EFUSE_NAME             Description = [Meaningful Value] [Readable/Writeable] (Hex Value)
----------------------------------------------------------------------------------------
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            = 1 R/W (0x1)
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 ff 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 ff 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                    Factory MAC Address                               
  = 3c:71:bf:6e:aa:14 (CRC 9f OK) R/W 
CHIP_VER_REV1          Silicon Revision 1                                = 1 R/W (0x1)
CHIP_VERSION           Reserved for future chip versions                 = 2 R/W (0x2)
CHIP_PACKAGE           Chip package identifier                           = 0 R/W (0x0)

Calibration fuses:
BLK3_PART_RESERVE      BLOCK3 partially served for ADC calibration data  = 0 R/W (0x0)
ADC_VREF               Voltage reference calibration                     = 1156 R/W (0x8)

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

ESP_Sprite
Posts: 3914
Joined: Thu Nov 26, 2015 4:08 am

Re: eFuse factory already wrote

Postby ESP_Sprite » Fri Jan 31, 2020 11:36 am

Obviously, that shouldn't happen. Is this consistent across readouts? This only happens with one module/chip, right? What is the MAC number?

User avatar
urbanze
Posts: 267
Joined: Sat Jun 10, 2017 9:55 pm
Location: Brazil

Re: eFuse factory already wrote

Postby urbanze » Fri Jan 31, 2020 11:42 pm

ESP_Sprite wrote:
Fri Jan 31, 2020 11:36 am
Obviously, that shouldn't happen. Is this consistent across readouts? This only happens with one module/chip, right? What is the MAC number?
Yes, all eFuse read are the same value.
Yes, I noticed this behaviour only one time in my life with esp32.
Summary above has MAC (MAC Factory MAC Address = 3c:71:bf:6e:aa:14 (CRC 9f OK) R/W)

Whats happen? Why? Any chance to recover?

User avatar
urbanze
Posts: 267
Joined: Sat Jun 10, 2017 9:55 pm
Location: Brazil

Re: eFuse factory already wrote

Postby urbanze » Thu Aug 13, 2020 2:06 pm

any one can help me to understand this situation?

Who is online

Users browsing this forum: No registered users and 29 guests