Warning

This document is not updated for ESP32C61 yet, so some of the content may not be correct.

This warning was automatically inserted due to the source file being in the add_warnings_pages list.

Chip Revision

[中文]

Overview

ESP32-C61 may have different revisions. These revisions mainly fix some issues, and sometimes also bring new features to the chip. Versioning Scheme describes the versioning of these chip revisions, and the APIs to read the versions at runtime.

There are some considerations of compatibility among application, ESP-IDF version, and chip revisions:

  • Applications may depend on some fixes/features provided by a chip revision.

  • When using updated version of hardware, the hardware may be incompatible with earlier versions of ESP-IDF.

Compatibility Checks of ESP-IDF describes how the application can specify its chip revision requirements, and the way ESP-IDF checks the compatibility. After that, there is troubleshooting information for this mechanism.

Versioning Scheme

A chip's revision number is typically expressed as vX.Y, where:

  • X means a Major wafer version. If it is changed, it means that the current software version is not compatible with this released chip and the software must be updated to use this chip.

  • Y means a Minor wafer version. If it is changed that means the current software version is compatible with the released chip, and there is no need to update the software.

If a newly released chip does not contain breaking changes, the chip can run the same software as the previous chip. As such, the new chip's revision number will only increment the minor version while keeping the major version the same (e.g., v1.1 to v1.2).

Conversely, if a newly released chip contains breaking changes, the chip cannot run the same software as the previous chip. As such, the new chip's revision number will increment the major version and set the minor version to 0 (e.g., v1.1 to v2.0).

This versioning scheme was selected to indicate the derivation relationship of chip revisions, and clearly distinguish changes in chips between breaking changes and non-breaking changes.

ESP-IDF is designed to execute seamlessly on future chip minor revisions with the same logic as the chip's nearest previous minor revision. Thus，users can directly port their compiled binaries to newer MINOR chip revisions without upgrading their ESP-IDF version and re-compile the whole project.

When a binary is executed on a chip revision of unexpected MAJOR revision, the software is also able to report issues according to the MAJOR revision. The major and minor versioning scheme also allows hardware changes to be branchable.

Note

The current chip revision scheme using major and minor versions was introduced from ESP-IDF v5.0 onwards. Thus bootloaders built using earlier versions of ESP-IDF will still use the legacy chip revision scheme of wafer versions.

EFuse Bits for Chip Revisions

Chips have several eFuse version fields:

  • Major wafer version (WAFER_VERSION_MAJOR eFuse)

  • Minor wafer version (WAFER_VERSION_MINOR eFuse)

  • Ignore maximum wafer revision (DISABLE_WAFER_VERSION_MAJOR eFuse). See Compatibility Checks of ESP-IDF on how this is used.

Note

The previous versioning logic was based on a single eFuse version field (WAFER_VERSION). This approach makes it impossible to mark chips as breaking or non-breaking changes, and the versioning logic becomes linear.

EFuse Bits for eFuse Block Revisions

EFuse block has version fields:

  • Major efuse block version (BLK_VERSION_MAJOR eFuse)

  • Minor efuse block version (BLK_VERSION_MINOR eFuse)

  • Ignore maximum efuse block revision (DISABLE_BLK_VERSION_MAJOR eFuse). See Compatibility Checks of ESP-IDF on how this is used.

Chip Revision APIs

These APIs helps to get chip revision from eFuses:

The following Kconfig definitions (in major * 100 + minor format) that can help add the chip revision dependency to the code:

  • CONFIG_ESP32C61_REV_MIN_FULL

  • CONFIG_ESP_REV_MIN_FULL

  • CONFIG_ESP32C61_REV_MAX_FULL

  • CONFIG_ESP_REV_MAX_FULL

EFuse Block Revision APIs

These APIs helps to get eFuse block revision from eFuses:

  • efuse_hal_blk_version(). It returns revision in the major * 100 + minor format.

  • efuse_ll_get_blk_version_major(). It returns Major revision of eFuse block.

  • efuse_ll_get_blk_version_minor(). It returns Minor revision of eFuse block.

The following Kconfig definitions (in major * 100 + minor format) that can help add the eFuse block revision dependency to the code:

  • CONFIG_ESP_EFUSE_BLOCK_REV_MIN_FULL

  • CONFIG_ESP_EFUSE_BLOCK_REV_MAX_FULL

Compatibility Checks of ESP-IDF

When building an application that needs to support multiple revisions of a particular chip, the minimum and maximum chip revision numbers supported by the build are specified via Kconfig.

The minimum chip revision can be configured via the CONFIG_ESP32C61_REV_MIN option. Specifying the minimum chip revision will limit the software to only run on a chip revisions that are high enough to support some features or bugfixes.

The maximum chip revision cannot be configured and is automatically determined by the current ESP-IDF version being used. ESP-IDF will refuse to boot any chip revision exceeding the maximum chip revision. Given that it is impossible for a particular ESP-IDF version to foresee all future chip revisions, the maximum chip revision is usually set to maximum supported MAJOR version + 99. The "Ignore Maximum Revision" eFuse can be set to bypass the maximum revision limitation. However, the software is not guaranteed to work if the maximum revision is ignored.

The eFuse block revision is similar to the chip revision, but it mainly affects the coefficients that are specified in the eFuse (e.g. ADC calibration coefficients).

Below is the information about troubleshooting when the chip revision fails the compatibility check. Then there are technical details of the checking and software behavior on earlier version of ESP-IDF.

Troubleshooting

  1. If the second stage bootloader is run on a chip revision smaller than minimum revision specified in the image (i.e., the application), a reboot occurs. The following message will be printed:

Image requires chip rev >= v3.0, but chip is v1.0

To resolve this issue,

  • Use a chip with the required minimum revision or higher.

  • Lower the CONFIG_ESP32C61_REV_MIN value and rebuild the image so that it is compatible with the chip revision being used.

  1. If application does not match minimum and maximum chip revisions, a reboot occurs. The following message will be printed:

Image requires chip rev <= v2.99, but chip is v3.0

To resolve this issue, update ESP-IDF to a newer version that supports the chip's revision (CONFIG_ESP32C61_REV_MAX_FULL). Alternatively, set the Ignore maximal revision bit in eFuse or use a chip revision that is compatible with the current version of ESP-IDF.

Representing Revision Requirements of a Binary Image

For the chip revision, the second stage bootloader and the application binary images contain the esp_image_header_t header, which stores information specifying the chip revisions that the image is permitted to run on. This header has 3 fields related to the chip revisions:

  • min_chip_rev - Minimum chip MAJOR revision required by image (but for ESP32-C3 it is MINOR revision). Its value is determined by CONFIG_ESP32C61_REV_MIN.

  • min_chip_rev_full - Minimum chip MINOR revision required by image in format: major * 100 + minor. Its value is determined by CONFIG_ESP32C61_REV_MIN.

  • max_chip_rev_full - Maximum chip revision required by image in format: major * 100 + minor. Its value is determined by CONFIG_ESP32C61_REV_MAX_FULL. It can not be changed by user. Only Espressif can change it when a new version will be supported in ESP-IDF.

For the eFuse revision, the requirements are stored in esp_app_desc_t, which is contained in the application binary image. We only check the application image because the eFuse block revision mostly affects the ADC calibration, which does not really matter in the bootloader. There are 2 fields related to eFuse block revisions:

  • min_efuse_blk_rev_full - Minimum eFuse block MINOR revision required by image in format: major * 100 + minor. Its value is determined by CONFIG_ESP_EFUSE_BLOCK_REV_MIN_FULL.

  • max_efuse_blk_rev_full - Maximum eFuse block MINOR revision required by image in format: major * 100 + minor. Its value is determined by CONFIG_ESP_EFUSE_BLOCK_REV_MAX_FULL. It reflects whether the current IDF version supports this efuse block format or not, and should not be changed by the user.

Maximum And Minimum Revision Restrictions

The order for checking the minimum and maximum revisions during application boot up is as follows:

  1. The first stage (ROM) bootloader does not check minimum and maximum revision fields from esp_image_header_t before running the 2nd stage bootloader.

  2. The initialization phase of the second stage bootloader checks that the second stage bootloader itself can be launched on the chip of this revision. It extracts the minimum revision from the header of the bootloader image and checks against the chip revision from eFuses. If the chip revision is less than the minimum revision, the bootloader refuses to boot up and aborts. The maximum revision is not checked at this phase.

  3. Then the second stage bootloader checks the revision requirements of the application. It extracts the minimum and maximum revisions of the chip from the application image header, and the eFuse block from the segment header. Then the bootloader checks these versions against the chip and eFuse block revision from eFuses. If the these revisions are less than their minimum revision or higher than the maximum revision, the bootloader refuses to boot up and aborts. However, if the ignore maximum revision bit is set, the maximum revision constraint can be ignored. The ignore bits are set by the customer themselves when there is confirmation that the software is able to work with this chip revision or eFuse block revision.

  4. Furthermore, at the OTA update stage, the running application checks if the new software matches the chip revision and eFuse block revision. It extracts the minimum and maximum chip revisions from the header of the new application image and the eFuse block constraints from the application description to check against the these revisions from eFuses. It checks for revisions matching in the same way that the bootloader does, so that the chip and eFuse block revisions are between their min and max revisions (logic of ignoring max revision also applies).

Backward Compatibility with Bootloaders Built by Older ESP-IDF Versions

Please check the chip version using esptool chip_id command.

References

API Reference

Header File

Functions

void efuse_hal_get_mac(uint8_t *mac)

get factory mac address

uint32_t efuse_hal_chip_revision(void)

Returns chip version.

Returns

Chip version in format: Major * 100 + Minor

uint32_t efuse_hal_blk_version(void)

Return block version.

Returns

Block version in format: Major * 100 + Minor

bool efuse_hal_flash_encryption_enabled(void)

Is flash encryption currently enabled in hardware?

Flash encryption is enabled if the FLASH_CRYPT_CNT efuse has an odd number of bits set.

Returns

true if flash encryption is enabled.

bool efuse_hal_get_disable_wafer_version_major(void)

Returns the status of whether the bootloader (and OTA) will check the maximum chip version or not.

Returns

true - Skip the maximum chip version check.

bool efuse_hal_get_disable_blk_version_major(void)

Returns the status of whether the app start-up (and OTA) will check the efuse block version or not.

Returns

true - Skip the efuse block version check.

uint32_t efuse_hal_get_major_chip_version(void)

Returns major chip version.

uint32_t efuse_hal_get_minor_chip_version(void)

Returns minor chip version.

uint32_t efuse_hal_get_chip_ver_pkg(void)

Returns the chip package version.

void efuse_hal_set_ecdsa_key(int efuse_key_blk)

Set the efuse block that should be used as ECDSA private key.

Note

The efuse block must be burnt with key purpose ECDSA_KEY

Parameters

efuse_key_blk -- Efuse key block number (Must be in [EFUSE_BLK_KEY0...EFUSE_BLK_KEY_MAX - 1] range)

Was this page helpful?