ESP32-S3 eFuse DIS_BOOT_REMAP

skiddd
Posts: 11
Joined: Sat May 28, 2022 8:58 am

ESP32-S3 eFuse DIS_BOOT_REMAP

Postby skiddd » Tue Dec 20, 2022 2:55 am

Greetings Dear Colleagues,

The information regarding the bit position of DIS_BOOT_REMAP in EFUSE BLOCK0 appears to be missing in online documentation here:

https://docs.espressif.com/projects/esp ... efuse.html

It is also missing from the current ESP32-S3 Technical Referece Manual (v1.1) here:
https://www.espressif.com/sites/default ... ual_en.pdf

Burning this specific eFuse via espefuse.py -p COM1 burn_efuse DIS_BOOT_REMAP also gives as error:

Code: Select all

espefuse.py v4.4
Connecting....
Detecting chip type... ESP32-S3

A fatal error occurred: Invalid the efuse name 'DIS_BOOT_REMAP'. Available the efuse names: ['WR_DIS', 'RD_DIS', 'DIS_ICACHE', 'DIS_DCACHE', 'DIS_DOWNLOAD_ICACHE', 'DIS_DOWNLOAD_DCACHE', 'DIS_FORCE_DOWNLOAD', 'DIS_USB', 'DIS_CAN', 'DIS_APP_CPU', 'SOFT_DIS_JTAG', 'HARD_DIS_JTAG', 'DIS_DOWNLOAD_MANUAL_ENCRYPT', 'USB_EXCHG_PINS', 'EXT_PHY_ENABLE', 'BTLC_GPIO_ENABLE', 'VDD_SPI_XPD', 'VDD_SPI_TIEH', 'VDD_SPI_FORCE', 'WDT_DELAY_SEL', 'SPI_BOOT_CRYPT_CNT', 'SECURE_BOOT_KEY_REVOKE0', 'SECURE_BOOT_KEY_REVOKE1', 'SECURE_BOOT_KEY_REVOKE2', 'KEY_PURPOSE_0', 'KEY_PURPOSE_1', 'KEY_PURPOSE_2', 'KEY_PURPOSE_3', 'KEY_PURPOSE_4', 'KEY_PURPOSE_5', 'SECURE_BOOT_EN', 'SECURE_BOOT_AGGRESSIVE_REVOKE', 'DIS_USB_JTAG', 'DIS_USB_SERIAL_JTAG', 'STRAP_JTAG_SEL', 'USB_PHY_SEL', 'FLASH_TPUW', 'DIS_DOWNLOAD_MODE', 'DIS_DIRECT_BOOT', 'DIS_USB_SERIAL_JTAG_ROM_PRINT', 'FLASH_ECC_MODE', 'DIS_USB_SERIAL_JTAG_DOWNLOAD_MODE', 'ENABLE_SECURITY_DOWNLOAD', 'UART_PRINT_CONTROL', 'PIN_POWER_SELECTION', 'FLASH_TYPE', 'FLASH_PAGE_SIZE', 'FLASH_ECC_EN', 'FORCE_SEND_RESUME', 'SECURE_VERSION', 'DIS_USB_OTG_DOWNLOAD_MODE', 'DISABLE_WAFER_VERSION_MAJOR', 'DISABLE_BLK_VERSION_MAJOR', 'MAC', 'SPI_PAD_CONFIG_CLK', 'SPI_PAD_CONFIG_Q', 'SPI_PAD_CONFIG_D', 'SPI_PAD_CONFIG_CS', 'SPI_PAD_CONFIG_HD', 'SPI_PAD_CONFIG_WP', 'SPI_PAD_CONFIG_DQS', 'SPI_PAD_CONFIG_D4', 'SPI_PAD_CONFIG_D5', 'SPI_PAD_CONFIG_D6', 'SPI_PAD_CONFIG_D7', 'WAFER_VERSION_MINOR_LO', 'PKG_VERSION', 'BLK_VERSION_MINOR', 'WAFER_VERSION_MINOR_HI', 'WAFER_VERSION_MAJOR', 'OPTIONAL_UNIQUE_ID', 'BLK_VERSION_MAJOR', 'CUSTOM_MAC', 'BLOCK_USR_DATA', 'BLOCK_KEY0', 'BLOCK_KEY1', 'BLOCK_KEY2', 'BLOCK_KEY3', 'BLOCK_KEY4', 'BLOCK_KEY5', 'BLOCK_SYS_DATA2', 'TEMP_SENSOR_CAL', 'ADC1_MODE0_D2', 'ADC1_MODE1_D2', 'ADC1_MODE2_D2', 'ADC1_MODE3_D2', 'ADC2_MODE0_D2', 'ADC2_MODE1_D2', 'ADC2_MODE2_D2', 'ADC2_MODE3_D2', 'ADC1_MODE0_D1', 'ADC1_MODE1_D1', 'ADC1_MODE2_D1', 'ADC1_MODE3_D1', 'ADC2_MODE0_D1', 'ADC2_MODE1_D1', 'ADC2_MODE2_D1', 'ADC2_MODE3_D1', 'WAFER_VERSION_MINOR']
I need to manually burn this eFuse because it was specified here:
https://docs.espressif.com/projects/esp ... ption.html

Code: Select all

Flash Encryption Process

6. For Development Mode, the firmware bootloader allows the UART bootloader to re-flash encrypted binaries. Also, the SPI_BOOT_CRYPT_CNT eFuse bits are NOT write-protected. In addition, the firmware bootloader by default sets the eFuse bits [b]DIS_BOOT_REMAP[/b], DIS_DOWNLOAD_ICACHE, DIS_DOWNLOAD_DCACHE, HARD_DIS_JTAG and DIS_LEGACY_SPI_BOOT.

I need to manually burn DIS_BOOT_REMAP as I don't want to rely on the bootloader to automatically burn it upon the first boot after flash encryption is enabled.

My specific task is described here: viewtopic.php?f=12&t=30893


Best Regards

skiddd
Posts: 11
Joined: Sat May 28, 2022 8:58 am

Re: ESP32-S3 eFuse DIS_BOOT_REMAP

Postby skiddd » Tue Dec 20, 2022 5:25 pm

After checking bootloader.elf in a disassembler, I can conclude that DIS_BOOT_REMAP is not even used in the current ESP32-S3 bootloader and therefore the online documentation needs to be corrected.

ESP_Mahavir
Posts: 190
Joined: Wed Jan 24, 2018 6:51 am

Re: ESP32-S3 eFuse DIS_BOOT_REMAP

Postby ESP_Mahavir » Wed Dec 21, 2022 3:57 am

Hello,

I can confirm that DIS_BOOT_REMAP EFuse bit exists only for ESP32-S2. We will correct our docs in this regard. Thank you for notifying!

Thanks.

Who is online

Users browsing this forum: Google [Bot] and 124 guests