The version of the ESP32-C3 seems to be wrong, could you confirm?

joseMiguel
Posts: 22
Joined: Sun Oct 25, 2020 11:43 pm

The version of the ESP32-C3 seems to be wrong, could you confirm?

Postby joseMiguel » Fri Jan 06, 2023 3:11 pm

Hello,

I buy a development board based on ESP32-C3 with two USB connectors.
The first for the USB/COM CH340 (USB to Serial protocol convertor),
The second to the is USB/JTAG or USB/COM depending on your configuration.

When i type this command to see the chip version, i have this log :

(idf5.1_py3.9_env) C:\ESP\esp-idf-v5.0\examples\wifi\fast-scan>espefuse.py -p COM6 dump
espefuse.py v4.5.dev0
Connecting....
Detecting chip type... ESP32-C3
BLOCK0 ( ) [0 ] read_regs: 00000000 00000000 00000000 00000000 80000000 00000000
MAC_SPI_8M_0 (BLOCK1 ) [1 ] read_regs: b368545c 000068b6 00000000 8a0c0000 30d122d9 00470a90
BLOCK_SYS_DATA (BLOCK2 ) [2 ] read_regs: 76062310 83f4a406 398118a2 98b89ee7 1b7498c9 7b7a6193 ee1506e2 00000008
BLOCK_USR_DATA (BLOCK3 ) [3 ] read_regs: 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
BLOCK_KEY0 (BLOCK4 ) [4 ] read_regs: 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
BLOCK_KEY1 (BLOCK5 ) [5 ] read_regs: 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
BLOCK_KEY2 (BLOCK6 ) [6 ] read_regs: 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
BLOCK_KEY3 (BLOCK7 ) [7 ] read_regs: 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
BLOCK_KEY4 (BLOCK8 ) [8 ] read_regs: 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
BLOCK_KEY5 (BLOCK9 ) [9 ] read_regs: 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
BLOCK_SYS_DATA2 (BLOCK10 ) [10] read_regs: 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000

BLOCK0 ( ) [0 ] err__regs: 00000000 00000000 00000000 00000000 00000000 00000000
EFUSE_RD_RS_ERR0_REG 0x00000000
EFUSE_RD_RS_ERR1_REG 0x00000000

=== Run "dump" command ===

For me is this a problem!!!!!

Could you help me please.

Thank you

JoseMiguel
José Michel

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

Re: The version of the ESP32-C3 seems to be wrong, could you confirm?

Postby ESP_Sprite » Sat Jan 07, 2023 6:27 am

...what specifically is your issue?

joseMiguel
Posts: 22
Joined: Sun Oct 25, 2020 11:43 pm

Re: The version of the ESP32-C3 seems to be wrong, could you confirm?

Postby joseMiguel » Sat Jan 07, 2023 8:27 pm

I am using JTAG in built debugger.

But i have problems with the Debug Adapter

I want to verify if the Chip revision is above or equal to 3.

Could you help me please.

Thank you in advance

Jose Miguel

Here below, the summary of the eFuse configuration.

(idf5.1_py3.9_env) C:\ESP\esp-idf-v5.0\examples\wifi\fast-scan>espefuse.py -p COM6 summary
espefuse.py v4.5.dev0
Connecting....
Detecting chip type... ESP32-C3

=== Run "summary" command ===
EFUSE_NAME (Block) Description = [Meaningful Value] [Readable/Writeable] (Hex Value)
----------------------------------------------------------------------------------------
Calibration fuses:
TEMP_SENSOR_CAL (BLOCK2) Temperature calibration = -4.9 R/W
(0b100110001)
ADC1_MODE0_D2 (BLOCK2) ADC1 calibration 1 = 464 R/W (0x74)
ADC1_MODE1_D2 (BLOCK2) ADC1 calibration 2 = 108 R/W (0x1b)
ADC1_MODE2_D2 (BLOCK2) ADC1 calibration 3 = -76 R/W (0x93)
ADC1_MODE3_D2 (BLOCK2) ADC1 calibration 4 = 388 R/W (0x61)
ADC2_MODE0_D2 (BLOCK2) ADC2 calibration 5 = 488 R/W (0x7a)
ADC2_MODE1_D2 (BLOCK2) ADC2 calibration 6 = 492 R/W (0x7b)
ADC2_MODE2_D2 (BLOCK2) ADC2 calibration 7 = -392 R/W
(0xe2)
ADC2_MODE3_D2 (BLOCK2) ADC2 calibration 8 = 24 R/W (0x06)
ADC1_MODE0_D1 (BLOCK2) ADC1 calibration 9 = 84 R/W (0b010101)
ADC1_MODE1_D1 (BLOCK2) ADC1 calibration 10 = -96 R/W (0b111000)
ADC1_MODE2_D1 (BLOCK2) ADC1 calibration 11 = 56 R/W (0b001110)
ADC1_MODE3_D1 (BLOCK2) ADC1 calibration 12 = 8 R/W (0b000010)
ADC2_MODE0_D1 (BLOCK2) ADC2 calibration 13 = 0 R/W (0b000000)
ADC2_MODE1_D1 (BLOCK2) ADC2 calibration 14 = 0 R/W (0b000000)
ADC2_MODE2_D1 (BLOCK2) ADC2 calibration 15 = 0 R/W (0b000000)
ADC2_MODE3_D1 (BLOCK2) ADC2 calibration 16 = 0 R/W (0b000000)

Config fuses:
DIS_ICACHE (BLOCK0) Disables ICache = False R/W (0b0)
DIS_DOWNLOAD_ICACHE (BLOCK0) Disables Icache when SoC is in Download mode = False R/W (0b0)
DIS_FORCE_DOWNLOAD (BLOCK0) Disables forcing chip into Download mode = False R/W (0b0)
DIS_CAN (BLOCK0) Disables the TWAI Controller hardware = False R/W (0b0)
VDD_SPI_AS_GPIO (BLOCK0) Set this bit to vdd spi pin function as gpio = False R/W (0b0)
BTLC_GPIO_ENABLE (BLOCK0) Enable btlc gpio = 0 R/W (0b00)
POWERGLITCH_EN (BLOCK0) Set this bit to enable power glitch function = False R/W (0b0)
POWER_GLITCH_DSENSE (BLOCK0) Sample delay configuration of power glitch = 0 R/W (0b00)
DIS_DIRECT_BOOT (BLOCK0) Disables direct boot mode = False R/W (0b0)
DIS_USB_SERIAL_JTAG_ROM_PRINT (BLOCK0) Disables USB-Serial-JTAG ROM printing = False R/W (0b0)
UART_PRINT_CONTROL (BLOCK0) Sets the default UART boot message output mode = Enabled R/W (0b00)
FORCE_SEND_RESUME (BLOCK0) Force ROM code to send a resume command during SPI = False R/W (0b0)
bootduring SPI boot
ERR_RST_ENABLE (BLOCK0) Use BLOCK0 to check error record registers = with check R/W (0b1)
DISABLE_WAFER_VERSION_MAJOR (BLOCK0) Disables check of wafer version major = False R/W (0b0)
DISABLE_BLK_VERSION_MAJOR (BLOCK0) Disables check of blk version major = False R/W (0b0)
BLOCK_USR_DATA (BLOCK3) User data
= 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 (BLOCK0) Disables programming of individual eFuses = 0 R/W (0x00000000)
RD_DIS (BLOCK0) Disables software reading from BLOCK4-10 = 0 R/W (0b0000000)

Flash Config fuses:
FLASH_TPUW (BLOCK0) Configures flash startup delay after SoC power-up, = 0 R/W (0x0)
unit is (ms/2). When the value is 15, delay is 7.
5 ms

Identity fuses:
SECURE_VERSION (BLOCK0) Secure version (used by ESP-IDF anti-rollback feat = 0 R/W (0x0000)
ure)
MAC (BLOCK1) Factory MAC Address
= 68:b6:b3:68:54:5c (OK) R/W
WAFER_VERSION_MINOR_LO (BLOCK1) WAFER_VERSION_MINOR least significant bits = 3 R/W (0b011)
PKG_VERSION (BLOCK1) Package version = 0 R/W (0b000)
BLK_VERSION_MINOR (BLOCK1) BLOCK version minor = 2 R/W (0b010)
WAFER_VERSION_MINOR_HI (BLOCK1) WAFER_VERSION_MINOR most significant bits = 0 R/W (0b0)
WAFER_VERSION_MAJOR (BLOCK1) WAFER_VERSION_MAJOR = 0 R/W (0b00)
OPTIONAL_UNIQUE_ID (BLOCK2) Optional unique 128-bit ID
= 10 23 06 76 06 a4 f4 83 a2 18 81 39 e7 9e b8 98 R/W
BLK_VERSION_MAJOR (BLOCK2) BLOCK version major = With calibration R/W (0b01)
CUSTOM_MAC (BLOCK3) Custom MAC Address
= 00:00:00:00:00:00 (OK) R/W
WAFER_VERSION_MINOR (BLOCK0) calc WAFER VERSION MINOR = WAFER_VERSION_MINOR_HI = 3 R/W (0x3)
<< 3 + WAFER_VERSION_MINOR_LO (read only)

Jtag Config fuses:
SOFT_DIS_JTAG (BLOCK0) Software disables JTAG. When software disabled, JT = 0 R/W (0b000)
AG can be activated temporarily by HMAC peripheral
DIS_PAD_JTAG (BLOCK0) Permanently disable JTAG access via pads. USB JTAG = False R/W (0b0)
is controlled separately.

Security fuses:
DIS_DOWNLOAD_MANUAL_ENCRYPT (BLOCK0) Disables flash encryption when in download boot mo = False R/W (0b0)
des
SPI_BOOT_CRYPT_CNT (BLOCK0) Enables encryption and decryption, when an SPI boo = Disable R/W (0b000)
t mode is set. Enabled when 1 or 3 bits are set,di
sabled otherwise
SECURE_BOOT_KEY_REVOKE0 (BLOCK0) If set, revokes use of secure boot key digest 0 = False R/W (0b0)
SECURE_BOOT_KEY_REVOKE1 (BLOCK0) If set, revokes use of secure boot key digest 1 = False R/W (0b0)
SECURE_BOOT_KEY_REVOKE2 (BLOCK0) If set, revokes use of secure boot key digest 2 = False R/W (0b0)
KEY_PURPOSE_0 (BLOCK0) KEY0 purpose = USER R/W
(0x0)
KEY_PURPOSE_1 (BLOCK0) KEY1 purpose = USER R/W
(0x0)
KEY_PURPOSE_2 (BLOCK0) KEY2 purpose = USER R/W
(0x0)
KEY_PURPOSE_3 (BLOCK0) KEY3 purpose = USER R/W
(0x0)
KEY_PURPOSE_4 (BLOCK0) KEY4 purpose = USER R/W
(0x0)
KEY_PURPOSE_5 (BLOCK0) KEY5 purpose = USER R/W
(0x0)
SECURE_BOOT_EN (BLOCK0) Enables secure boot = False R/W (0b0)
SECURE_BOOT_AGGRESSIVE_REVOKE (BLOCK0) Enables aggressive secure boot key revocation mode = False R/W (0b0)
DIS_DOWNLOAD_MODE (BLOCK0) Disables all Download boot modes = False R/W (0b0)
ENABLE_SECURITY_DOWNLOAD (BLOCK0) Enables secure UART download mode (read/write flas = False R/W (0b0)
h only)
BLOCK_KEY0 (BLOCK4)
Purpose: USER
Encryption key0 or user data
= 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
BLOCK_KEY1 (BLOCK5)
Purpose: USER
Encryption key1 or user data
= 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
BLOCK_KEY2 (BLOCK6)
Purpose: USER
Encryption key2 or user data
= 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
BLOCK_KEY3 (BLOCK7)
Purpose: USER
Encryption key3 or user data
= 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
BLOCK_KEY4 (BLOCK8)
Purpose: USER
Encryption key4 or user data
= 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
BLOCK_KEY5 (BLOCK9)
Purpose: USER
Encryption key5 or user data
= 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
BLOCK_SYS_DATA2 (BLOCK10) System data (part 2)
= 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

Spi_Pad_Config fuses:
SPI_PAD_CONFIG_CLK (BLOCK1) SPI CLK pad = 0 R/W (0b000000)
SPI_PAD_CONFIG_Q (BLOCK1) SPI Q (D1) pad = 0 R/W (0b000000)
SPI_PAD_CONFIG_D (BLOCK1) SPI D (D0) pad = 0 R/W (0b000000)
SPI_PAD_CONFIG_CS (BLOCK1) SPI CS pad = 0 R/W (0b000000)
SPI_PAD_CONFIG_HD (BLOCK1) SPI HD (D3) pad = 0 R/W (0b000000)
SPI_PAD_CONFIG_WP (BLOCK1) SPI WP (D2) pad = 0 R/W (0b000000)
SPI_PAD_CONFIG_DQS (BLOCK1) SPI DQS pad = 0 R/W (0b000000)
SPI_PAD_CONFIG_D4 (BLOCK1) SPI D4 pad = 0 R/W (0b000000)
SPI_PAD_CONFIG_D5 (BLOCK1) SPI D5 pad = 0 R/W (0b000000)
SPI_PAD_CONFIG_D6 (BLOCK1) SPI D6 pad = 0 R/W (0b000000)
SPI_PAD_CONFIG_D7 (BLOCK1) SPI D7 pad = 0 R/W (0b000000)

Usb Config fuses:
DIS_USB_JTAG (BLOCK0) Disables USB JTAG. JTAG access via pads is control = False R/W (0b0) b0)
led separately b0)
DIS_USB_DEVICE (BLOCK0) Disables USB DEVICE = False R/W (0b0) b0) b0)
USB_EXCHG_PINS (BLOCK0) Exchanges USB D+ and D- pins = False R/W (0b0)
DIS_USB_SERIAL_JTAG_DOWNLOAD_MODE (BLOCK0) Disables USB-Serial-JTAG download feature in UART = False R/W (0b0) b0)
download boot mode

Wdt Config fuses:
WDT_DELAY_SEL (BLOCK0) Selects RTC WDT timeout threshold at startup = False R/W (0b0)
José Michel

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

Re: The version of the ESP32-C3 seems to be wrong, could you confirm?

Postby ESP_Sprite » Sun Jan 08, 2023 3:01 am

Can't you simply run ``esptool.py chip_id``?

joseMiguel
Posts: 22
Joined: Sun Oct 25, 2020 11:43 pm

Re: The version of the ESP32-C3 seems to be wrong, could you confirm?

Postby joseMiguel » Sun Jan 08, 2023 7:19 am

Hi,

Tgank you

(idf5.1_py3.9_env) C:\ESP\esp-idf-v5.0\examples\wifi\fast-scan>esptool.py chip_id
esptool.py v4.5.dev0
Found 2 serial ports
Serial port COM8
Connecting...
Detecting chip type... ESP32-C3
Chip is ESP32-C3 (revision v0.3)
Features: WiFi, BLE
Crystal is 40MHz
MAC: 68:b6:b3:68:54:5c
Uploading stub...
Running stub...
Stub running...
Warning: ESP32-C3 has no Chip ID. Reading MAC instead.
MAC: 68:b6:b3:68:54:5c
Hard resetting via RTS pin...
José Michel

User avatar
ESP_Roland
Posts: 265
Joined: Tue Oct 09, 2018 10:28 am

Re: The version of the ESP32-C3 seems to be wrong, could you confirm?

Postby ESP_Roland » Mon Jan 09, 2023 7:06 am

Perhaps the confusion is caused by the fact that MAJOR and MINOR revision numbers were introduced recently. You can read about it here: https://docs.espressif.com/projects/esp ... ision.html

Who is online

Users browsing this forum: Baidu [Spider] and 152 guests