From 5ab2bb87cd2bd2c8e755f0045db83167e0ec5421 Mon Sep 17 00:00:00 2001 From: "harshal.patil" Date: Mon, 10 Aug 2026 16:57:26 +0530 Subject: [PATCH] docs(examples): Fix the broken Key Manager peripheral link in the example readme --- examples/security/flash_encryption/README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/examples/security/flash_encryption/README.md b/examples/security/flash_encryption/README.md index fc0faf2a587..03e75bcf738 100644 --- a/examples/security/flash_encryption/README.md +++ b/examples/security/flash_encryption/README.md @@ -71,7 +71,7 @@ FATFS encryption example uses two additional partitions in the partition table. > **Note:** This feature is only available on targets with the Key Manager peripheral: **ESP32-C5** and **ESP32-P4**. -On supported targets, the Flash Encryption key can be deployed into and managed by the [Key Manager](https://docs.espressif.com/projects/esp-idf/en/latest/esp32c5/api-reference/peripherals/key_manager.html) peripheral instead of an eFuse block. This means the plaintext key material is never stored in eFuses, RAM, or flash - it is bound to the device's Hardware Unique Key (HUK) and accessible only to hardware peripherals. +On supported targets, the Flash Encryption key can be deployed into and managed by the [Key Manager](../../../docs/en/api-reference/peripherals/key_manager.rst) peripheral instead of an eFuse block. This means the plaintext key material is never stored in eFuses, RAM, or flash - it is bound to the device's Hardware Unique Key (HUK) and accessible only to hardware peripherals. For the full workflow (key deployment, eFuse programming, and boot sequence), refer to the [Flash Encryption documentation](https://docs.espressif.com/projects/esp-idf/en/latest/esp32c5/security/flash-encryption.html).