espressif/esp-idf
1
0
Fork 1
mirror of https://github.com/espressif/esp-idf.git synced 2026-05-19 23:45:28 +02:00
Code Issues Packages Projects Releases Wiki Activity

Merge branch 'feature/qemu_doc_guide_updates' into 'master'

Browse Source 
docs: misc updates to qemu guide, now enabled for ESP32-S3

See merge request espressif/esp-idf!33854
This commit is contained in:
Mahavir Jain
2024-10-08 12:45:23 +08:00
parent 1662e28718 757fa4d72c
commit 27bcb047b4
12 changed files with 91 additions and 9 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/en/api-guides/bootloader.rst
+1 -1
View File
@@ -6,7 +6,7 @@ Bootloader
The ESP-IDF Software Bootloader performs the following functions:
1. Minimal initial configuration of internal modules;
2. Initialize :doc:`/security/flash-encryption` and/or :doc:`Secure </security/secure-boot-v2>` features, if configured;
2. Initialize :doc:`/security/flash-encryption` and/or :doc:`Secure Boot </security/secure-boot-v2>` features, if configured;
3. Select the application partition to boot, based on the partition table and ota_data (if any);
4. Load this image to RAM (IRAM & DRAM) and transfer management to the image that was just loaded.
docs/en/api-guides/tools/index.rst
+1 -1
View File
@@ -12,4 +12,4 @@ Tools
idf-clang-tidy
idf-tools
idf-size
:esp32 or esp32c3: qemu
:TARGET_SUPPORT_QEMU: qemu
docs/en/api-guides/tools/qemu.rst
+28 -2
View File
@@ -1,6 +1,8 @@
QEMU Emulator
=============
{IDF_TARGET_CRYPT_CNT:default="SPI_BOOT_CRYPT_CNT",esp32="FLASH_CRYPT_CNT"}
:link_to_translation:`zh_CN:[中文]`
Espressif maintains a `fork <https://github.com/espressif/qemu>`_ of the QEMU emulator with support for {IDF_TARGET_NAME}. This fork implements emulation of the CPU, memory, and several peripherals of {IDF_TARGET_NAME}. For more information about QEMU for {IDF_TARGET_NAME}, see the `QEMU README documentation <https://github.com/espressif/esp-toolchain-docs/blob/main/qemu/README.md>`_.
@@ -119,13 +121,37 @@ QEMU supports emulation of eFuses. This can be a convenient way to test security
You can use :doc:`idf.py<idf-py>` eFuse-related commands to program eFuses. When you run any of these commands together with ``qemu`` command, the eFuses are programmed in QEMU, and the ``qemu_efuse.bin`` file is updated. For example,
.. only:: not SOC_FLASH_ENCRYPTION_XTS_AES
.. code-block:: console
idf.py qemu efuse-burn {IDF_TARGET_CRYPT_CNT} 1
idf.py qemu efuse-burn-key flash_encryption my_flash_encryption_key.bin
.. only:: SOC_FLASH_ENCRYPTION_XTS_AES
.. code-block:: console
idf.py qemu efuse-burn {IDF_TARGET_CRYPT_CNT} 1
idf.py qemu efuse-burn-key BLOCK my_flash_encryption_key.bin KEYPURPOSE
For details regarding the ``BLOCK`` and ``KEYPURPOSE``, please refer to the :doc:`../../security/flash-encryption` guide.
To dump the eFuse summary, please use the following command:
.. code-block:: console
idf.py qemu efuse-burn FLASH_CRYPT_CNT 1
idf.py qemu efuse-summary
By default, the values of eFuses are read from and written to the ``qemu_efuse.bin`` file in the build directory. You can specify a different file using the ``--efuse-file`` option. For example,
.. code-block:: console
idf.py qemu --efuse-file my_efuse.bin efuse-burn FLASH_CRYPT_CNT 1
idf.py qemu --efuse-file my_efuse.bin efuse-burn {IDF_TARGET_CRYPT_CNT} 1
idf.py qemu --efuse-file my_efuse.bin monitor
Emulating Secure Boot
~~~~~~~~~~~~~~~~~~~~~
QEMU supports emulation of secure boot v2 scheme. Please keep :ref:`CONFIG_SECURE_BOOT_FLASH_BOOTLOADER_DEFAULT` enabled to include signed bootloader image into the QEMU image artifact.