Merge branch 'feature/check_efuse_blk_after_ota_v5.3' into 'release/v5.3'

feat(bootloader): support to check efuse block revision (v5.3)

See merge request espressif/esp-idf!33136

components/esp_hw_support/port/esp32/Kconfig.hw_support

@@ -66,3 +66,20 @@ config ESP32_REV_MAX_FULL
 config ESP_REV_MAX_FULL
     int
     default ESP32_REV_MAX_FULL
+
+config ESP_EFUSE_BLOCK_REV_MIN_FULL
+    int "Minimum Supported ESP32 eFuse Block Revision"
+    default 0
+    help
+        Required minimum eFuse Block revision. ESP-IDF will check it at the 2nd bootloader stage
+        whether the current image can work correctly for this eFuse Block revision.
+        So that to avoid running an incompatible image on a SoC that contains breaking change in the eFuse Block.
+        If you want to update this value to run the image that not compatible with the current eFuse Block revision,
+        please contact to Espressif's business team for details:
+        https://www.espressif.com.cn/en/contact-us/sales-questions
+
+config ESP_EFUSE_BLOCK_REV_MAX_FULL
+    int
+    default 99
+    comment "Maximum Supported ESP32 eFuse Block Revision (eFuse Block Rev v0.99)"
+    # The revision in the comment must correspond to the default value of ESP_EFUSE_BLOCK_REV_MAX_FULL

components/esp_hw_support/port/esp32c2/Kconfig.hw_support

@@ -50,3 +50,21 @@ config ESP_REV_MAX_FULL
 config ESP32C2_REV2_DEVELOPMENT
     bool "Develop on ESP32-C2 v2.0 (Preview)"
     default y if IDF_CI_BUILD
+
+config ESP_EFUSE_BLOCK_REV_MIN_FULL
+    int "Minimum Supported ESP32-C2 eFuse Block Revision"
+    default 0
+    help
+        Required minimum eFuse Block revision. ESP-IDF will check it at the 2nd bootloader stage
+        whether the current image can work correctly for this eFuse Block revision.
+        So that to avoid running an incompatible image on a SoC that contains breaking change in the eFuse Block.
+        If you want to update this value to run the image that not compatible with the current eFuse Block revision,
+        please contact to Espressif's business team for details:
+        https://www.espressif.com.cn/en/contact-us/sales-questions
+
+
+config ESP_EFUSE_BLOCK_REV_MAX_FULL
+    int
+    default 99
+    comment "Maximum Supported ESP32-C2 eFuse Block Revision (eFuse Block Rev v0.99)"
+    # The revision in the comment must correspond to the default value of ESP_EFUSE_BLOCK_REV_MAX_FULL

components/esp_hw_support/port/esp32c3/Kconfig.hw_support

@@ -54,3 +54,20 @@ config ESP32C3_REV_MAX_FULL
 config ESP_REV_MAX_FULL
     int
     default ESP32C3_REV_MAX_FULL
+
+config ESP_EFUSE_BLOCK_REV_MIN_FULL
+    int "Minimum Supported ESP32-C3 eFuse Block Revision"
+    default 0
+    help
+        Required minimum eFuse Block revision. ESP-IDF will check it at the 2nd bootloader stage
+        whether the current image can work correctly for this eFuse Block revision.
+        So that to avoid running an incompatible image on a SoC that contains breaking change in the eFuse Block.
+        If you want to update this value to run the image that not compatible with the current eFuse Block revision,
+        please contact to Espressif's business team for details:
+        https://www.espressif.com.cn/en/contact-us/sales-questions
+
+config ESP_EFUSE_BLOCK_REV_MAX_FULL
+    int
+    default 199
+    comment "Maximum Supported ESP32-C3 eFuse Block Revision (eFuse Block Rev v1.99)"
+    # The revision in the comment must correspond to the default value of ESP_EFUSE_BLOCK_REV_MAX_FULL

components/esp_hw_support/port/esp32c5/Kconfig.hw_support

@@ -39,3 +39,20 @@ config ESP32C5_REV_MAX_FULL
 config ESP_REV_MAX_FULL
     int
     default ESP32C5_REV_MAX_FULL
+
+config ESP_EFUSE_BLOCK_REV_MIN_FULL
+    int "Minimum Supported ESP32-C5 eFuse Block Revision"
+    default 0
+    help
+        Required minimum eFuse Block revision. ESP-IDF will check it at the 2nd bootloader stage
+        whether the current image can work correctly for this eFuse Block revision.
+        So that to avoid running an incompatible image on a SoC that contains breaking change in the eFuse Block.
+        If you want to update this value to run the image that not compatible with the current eFuse Block revision,
+        please contact to Espressif's business team for details:
+        https://www.espressif.com.cn/en/contact-us/sales-questions
+
+config ESP_EFUSE_BLOCK_REV_MAX_FULL
+    int
+    default 99
+    comment "Maximum Supported ESP32-C5 eFuse Block Revision (eFuse Block Rev v0.99)"
+    # The revision in the comment must correspond to the default value of ESP_EFUSE_BLOCK_REV_MAX_FULL

components/esp_hw_support/port/esp32c6/Kconfig.hw_support

@@ -42,3 +42,20 @@ config ESP32C6_REV_MAX_FULL
 config ESP_REV_MAX_FULL
     int
     default ESP32C6_REV_MAX_FULL
+
+config ESP_EFUSE_BLOCK_REV_MIN_FULL
+    int "Minimum Supported ESP32-C6 eFuse Block Revision"
+    default 0
+    help
+        Required minimum eFuse Block revision. ESP-IDF will check it at the 2nd bootloader stage
+        whether the current image can work correctly for this eFuse Block revision.
+        So that to avoid running an incompatible image on a SoC that contains breaking change in the eFuse Block.
+        If you want to update this value to run the image that not compatible with the current eFuse Block revision,
+        please contact to Espressif's business team for details:
+        https://www.espressif.com.cn/en/contact-us/sales-questions
+
+config ESP_EFUSE_BLOCK_REV_MAX_FULL
+    int
+    default 99
+    comment "Maximum Supported ESP32-C6 eFuse Block Revision (eFuse Block Rev v0.99)"
+    # The revision in the comment must correspond to the default value of ESP_EFUSE_BLOCK_REV_MAX_FULL

components/esp_hw_support/port/esp32c61/Kconfig.hw_support

@@ -39,3 +39,20 @@ config ESP32C61_REV_MAX_FULL
 config ESP_REV_MAX_FULL
     int
     default ESP32C61_REV_MAX_FULL
+
+config ESP_EFUSE_BLOCK_REV_MIN_FULL
+    int "Minimum Supported ESP32-C61 eFuse Block Revision"
+    default 0
+    help
+        Required minimum eFuse Block revision. ESP-IDF will check it at the 2nd bootloader stage
+        whether the current image can work correctly for this eFuse Block revision.
+        So that to avoid running an incompatible image on a SoC that contains breaking change in the eFuse Block.
+        If you want to update this value to run the image that not compatible with the current eFuse Block revision,
+        please contact to Espressif's business team for details:
+        https://www.espressif.com.cn/en/contact-us/sales-questions
+
+config ESP_EFUSE_BLOCK_REV_MAX_FULL
+    int
+    default 99
+    comment "Maximum Supported ESP32-C61 eFuse Block Revision (eFuse Block Rev v0.99)"
+    # The revision in the comment must correspond to the default value of ESP_EFUSE_BLOCK_REV_MAX_FULL

components/esp_hw_support/port/esp32h2/Kconfig.hw_support

@@ -45,3 +45,20 @@ config ESP32H2_REV_MAX_FULL
 config ESP_REV_MAX_FULL
     int
     default ESP32H2_REV_MAX_FULL
+
+config ESP_EFUSE_BLOCK_REV_MIN_FULL
+    int "Minimum Supported ESP32-H2 eFuse Block Revision"
+    default 0
+    help
+        Required minimum eFuse Block revision. ESP-IDF will check it at the 2nd bootloader stage
+        whether the current image can work correctly for this eFuse Block revision.
+        So that to avoid running an incompatible image on a SoC that contains breaking change in the eFuse Block.
+        If you want to update this value to run the image that not compatible with the current eFuse Block revision,
+        please contact to Espressif's business team for details:
+        https://www.espressif.com.cn/en/contact-us/sales-questions
+
+config ESP_EFUSE_BLOCK_REV_MAX_FULL
+    int
+    default 99
+    comment "Maximum Supported ESP32-H2 eFuse Block Revision (eFuse Block Rev v0.99)"
+    # The revision in the comment must correspond to the default value of ESP_EFUSE_BLOCK_REV_MAX_FULL

components/esp_hw_support/port/esp32p4/Kconfig.hw_support

@@ -42,3 +42,20 @@ config ESP32P4_REV_MAX_FULL
 config ESP_REV_MAX_FULL
     int
     default ESP32P4_REV_MAX_FULL
+
+config ESP_EFUSE_BLOCK_REV_MIN_FULL
+    int "Minimum Supported ESP32-P4 eFuse Block Revision"
+    default 0
+    help
+        Required minimum eFuse Block revision. ESP-IDF will check it at the 2nd bootloader stage
+        whether the current image can work correctly for this eFuse Block revision.
+        So that to avoid running an incompatible image on a SoC that contains breaking change in the eFuse Block.
+        If you want to update this value to run the image that not compatible with the current eFuse Block revision,
+        please contact to Espressif's business team for details:
+        https://www.espressif.com.cn/en/contact-us/sales-questions
+
+config ESP_EFUSE_BLOCK_REV_MAX_FULL
+    int
+    default 99
+    comment "Maximum Supported ESP32-P4 eFuse Block Revision (eFuse Block Rev v0.99)"
+    # The revision in the comment must correspond to the default value of ESP_EFUSE_BLOCK_REV_MAX_FULL

components/esp_hw_support/port/esp32s2/Kconfig.hw_support

@@ -42,3 +42,20 @@ config ESP32S2_REV_MAX_FULL
 config ESP_REV_MAX_FULL
     int
     default ESP32S2_REV_MAX_FULL
+
+config ESP_EFUSE_BLOCK_REV_MIN_FULL
+    int "Minimum Supported ESP32-S2 eFuse Block Revision"
+    default 0
+    help
+        Required minimum eFuse Block revision. ESP-IDF will check it at the 2nd bootloader stage
+        whether the current image can work correctly for this eFuse Block revision.
+        So that to avoid running an incompatible image on a SoC that contains breaking change in the eFuse Block.
+        If you want to update this value to run the image that not compatible with the current eFuse Block revision,
+        please contact to Espressif's business team for details:
+        https://www.espressif.com.cn/en/contact-us/sales-questions
+
+config ESP_EFUSE_BLOCK_REV_MAX_FULL
+    int
+    default 99
+    comment "Maximum Supported ESP32-S2 eFuse Block Revision (eFuse Block Rev v0.99)"
+    # The revision in the comment must correspond to the default value of ESP_EFUSE_BLOCK_REV_MAX_FULL

components/esp_hw_support/port/esp32s3/Kconfig.hw_support

@@ -45,3 +45,20 @@ config ESP32S3_REV_MAX_FULL
 config ESP_REV_MAX_FULL
     int
     default ESP32S3_REV_MAX_FULL
+
+config ESP_EFUSE_BLOCK_REV_MIN_FULL
+    int "Minimum Supported ESP32-S3 eFuse Block Revision"
+    default 0
+    help
+        Required minimum eFuse Block revision. ESP-IDF will check it at the 2nd bootloader stage
+        whether the current image can work correctly for this eFuse Block revision.
+        So that to avoid running an incompatible image on a SoC that contains breaking change in the eFuse Block.
+        If you want to update this value to run the image that not compatible with the current eFuse Block revision,
+        please contact to Espressif's business team for details:
+        https://www.espressif.com.cn/en/contact-us/sales-questions
+
+config ESP_EFUSE_BLOCK_REV_MAX_FULL
+    int
+    default 199
+    comment "Maximum Supported ESP32-S3 eFuse Block Revision (eFuse Block Rev v1.99)"
+    # The revision in the comment must correspond to the default value of ESP_EFUSE_BLOCK_REV_MAX_FULL