| /hal_espressif-3.4.0/components/esptool_py/esptool/esptool/ |
| D | cmds.py | 160 image = LoadFirmwareImage(esp.CHIP_NAME, args.filename)
163 for seg in image.segments:
178 print("All segments done, executing at %08x" % image.entrypoint)
179 esp.mem_finish(image.entrypoint)
225 def _update_image_flash_params(esp, address, args, image): argument
227 Modify the flash mode & size bytes if this looks like an executable bootloader image
229 if len(image) < 8:
230 return image # not long enough to be a bootloader image
232 # unpack the (potential) image header
233 magic, _, flash_mode, flash_size_freq = struct.unpack("BBBB", image[:4])
[all …]
|
| D | bin_image.py | 40 Load a firmware image. Can be for any supported SoC.
65 else: # Otherwise, ESP8266 so look at magic to determine the image type
73 raise FatalError("Invalid image magic number: %d" % magic)
82 """Wrapper class for a segment in an ESP image
118 def get_memory_type(self, image): argument
125 for map_range in image.ROM_LOADER.MEMORY_MAP
134 """Wrapper class for a section in an ELF image, has a section
149 """ Base class with common firmware image functions """
168 raise FatalError("Invalid firmware image magic=0x%x" % (magic))
179 """Load the next segment from the image file"""
[all …]
|
| /hal_espressif-3.4.0/components/bootloader_support/include/ |
| D | esp_image_format.h | 21 /* Support for app/bootloader image parsing
27 /* Structure to hold on-flash image metadata */
29 uint32_t start_addr; /* Start address of image */
30 esp_image_header_t image; /* Header for entire image */ member
33 uint32_t image_len; /* Length of image on flash, in bytes */
38 …ESP_IMAGE_VERIFY, /* Verify image contents, not load to memory, load metadata. Print er…
39 …ESP_IMAGE_VERIFY_SILENT, /* Verify image contents, not load to memory, load metadata. Don't pr…
41 …ESP_IMAGE_LOAD, /* Verify image contents, load to memory, load metadata. Print errors…
42 …ESP_IMAGE_LOAD_NO_VALIDATE, /* Not verify image contents, load to memory, load metadata. Print er…
75 * @brief Verify an app image.
[all …]
|
| /hal_espressif-3.4.0/docs/en/security/ |
| D | secure-boot-v2.rst | 34 …ticular application image, the application's RSA-PSS signature is verified. If the verification is…
53 - Same image format and signature verification method is applied for applications and software boot…
63 …image and application binary images using a dedicated *signature block*. Each image has a separate…
67 Only one signature block can be appended to the bootloader or application image in ESP32 ECO3.
71 …Up to 3 signature blocks can be appended to the bootloader or application image in {IDF_TARGET_NAM…
73 Each signature block contains a signature of the preceding image as well as the corresponding RSA-3…
75 …image is not only verified on every boot but also on each over the air (OTA) update. If the curren…
83 3. The ROM code verifies the bootloader image using the raw image data, its corresponding signature…
87 5. The bootloader verifies the application image's signature block (:ref:`verify_signature-block`).…
89 …image using the raw image data, its corresponding signature blocks and the eFuse (:ref:`verify_ima…
[all …]
|
| D | secure-boot-v1.rst | 37 …image is built by esp-idf with secure boot support enabled and the public key (signature verificat…
41 … and a secure digest. The digest is derived from the key, an IV, and the bootloader image contents.
44 …e bootloader then becomes protected (the chip will only boot a bootloader image if the digest matc…
65 …g key" is a standard ECDSA public/private key pair (see :ref:`secure-boot-image-signing-algorithm`…
67 …ader and used to verify the second stage of booting (partition table, app image) before booting co…
101 …h`` to build and flash the partition table and the just-built app image. The app image will be sig…
105 …tloader will enable secure boot on the chip, and then it verifies the app image signature and boot…
107 .. note:: Secure boot won't be enabled until after a valid partition table and app image have been …
111 …en the software bootloader will verify the signed partition table and app image (using the public …
155 .. _remote-sign-image:
[all …]
|
| /hal_espressif-3.4.0/docs/en/api-reference/storage/ |
| D | spiffs.rst | 33 - **image_size**: size of the partition onto which the created SPIFFS image will be flashed.
34 - **base_dir**: directory for which the SPIFFS image needs to be created.
35 - **output_file**: SPIFFS image output file.
37 There are also other arguments that control image generation. Documentation on these arguments can …
41 …orrespond to a possible SPIFFS build configuration. To generate the right image, please make sure …
43 When the image is created, it can be flashed using ``esptool.py`` or ``parttool.py``.
57 …image is valid for that build. An example of this is while the *image_size* is required for the st…
64 Optionally, user can opt to have the image automatically flashed together with the app binaries, pa…
75 If FLASH_IN_PROJECT/SPIFFS_IMAGE_FLASH_IN_PROJECT is not specified, the image will still be generat…
77 …EPENDS/SPIFFS_IMAGE_DEPENDS to specify targets that should be executed before generating the image.
[all …]
|
| /hal_espressif-3.4.0/components/esp_https_ota/include/ |
| D | esp_https_ota.h | 34 …bool partial_http_download; /*!< Enable Firmware image to be downloaded over mu…
45 * reads image data from HTTP stream and writes it to OTA partition and
56 * successfully, esp_restart() must be called to boot from the new firmware image.
62 * - ESP_ERR_OTA_VALIDATE_FAILED: Invalid app image
97 * @brief Read image data from HTTP stream and write it to OTA partition
99 * This function reads image data from HTTP stream and writes it to OTA partition. This function
111 * - ESP_ERR_OTA_VALIDATE_FAILED: Invalid app image
121 … be called just before esp_https_ota_finish() to validate if the complete image was indeed receive…
136 * new firmware image.
139 * boot from the new firmware image
[all …]
|
| /hal_espressif-3.4.0/docs/en/api-guides/tools/ |
| D | idf-docker-image.rst | 2 IDF Docker Image
7 IDF Docker image (``espressif/idf``) is intended for building applications and libraries with speci…
9 The image contains:
17 The image entrypoint sets up ``PATH`` environment variable to point to the correct version of tools…
19 The image can also be used as a base for custom images, if additional utilities are required.
24 Multiple tags of this image are maintained:
32 …eased before this feature was introduced do not have corresponding Docker image versions. You can …
40 Before using the ``espressif/idf`` Docker image locally, make sure you have Docker installed. Follo…
42 If using the image in CI environment, consult the documentation of your CI service on how to specif…
54 - ``docker run``: runs a Docker image. It is a shorter form of the command ``docker container run``.
[all …]
|
| /hal_espressif-3.4.0/components/bootloader_support/src/ |
| D | esp_image_format.c | 82 /* Verify the main image header */
83 static esp_err_t verify_image_header(uint32_t src_addr, const esp_image_header_t *image, bool silen…
117 bool do_load = false; // Can't load the image in app mode in image_load()
122 // checksum the image a word at a time. This shaves 30-40ms per MB of image size in image_load()
213 for (int i = 0; i < data->image.segment_count; i++) { in image_load()
297 static esp_err_t verify_image_header(uint32_t src_addr, const esp_image_header_t *image, bool silen… in verify_image_header() argument
301 ESP_LOGD(TAG, "image header: 0x%02x 0x%02x 0x%02x 0x%02x %08x", in verify_image_header()
302 image->magic, in verify_image_header()
303 image->segment_count, in verify_image_header()
304 image->spi_mode, in verify_image_header()
[all …]
|
| /hal_espressif-3.4.0/components/esptool_py/ |
| D | project_include.cmake | 61 # Flash size detection updates the image header which would invalidate the appended
97 COMMENT "Generating binary image from built executable"
119 … # for locally signed secure boot image, add a signing step to get from unsigned app to signed app
123 … COMMAND ${CMAKE_COMMAND} -E echo "Generated signed binary image ${build_dir}/${PROJECT_BIN}"
128 COMMENT "Generating signed binary image"
222 # Retrieve the offset for the partition to flash the image on
232 # If the image should not be encrypted, we pass the option
238 # The image name is also the partition name
244 # its name states, it marks whether the image should be flashed as plain text or
246 # this parameter is provided, then the image will be flahsed as plain text
[all …]
|
| /hal_espressif-3.4.0/components/bootloader_support/src/secure_boot_v1/ |
| D | secure_boot.c | 38 * @inputs: image_len - length of image to calculate digest for
43 const uint32_t *image; in secure_boot_generate() local
46 …image length. The additional data should all be 0xFF (or the appended SHA, if it falls in the same… in secure_boot_generate()
62 /* generate digest from image contents */ in secure_boot_generate()
63 image = bootloader_mmap(ESP_BOOTLOADER_OFFSET, image_len); in secure_boot_generate()
64 if (!image) { in secure_boot_generate()
69 ets_secure_boot_hash(&image[i/sizeof(uint32_t)]); in secure_boot_generate()
71 bootloader_munmap(image); in secure_boot_generate()
107 ESP_LOGE(TAG, "bootloader image appears invalid! error %d", err); in esp_secure_boot_generate_digest()
132 if(bootloader_data.image.hash_appended) { in esp_secure_boot_generate_digest()
[all …]
|
| /hal_espressif-3.4.0/examples/storage/spiffsgen/ |
| D | README.md | 1 # SPIFFS Image Generation on Build Example
5 This example demonstrates how to use the SPIFFS image generation tool [spiffsgen.py](../../../compo…
6 filesystem image from the contents of a host folder during build, with an option of
7 automatically flashing the created image on invocation of `idf.py -p PORT flash`.
12 1. There is a directory `spiffs_image` from which the SPIFFS filesystem image will be created.
14 2. The function `spiffs_create_partition_image` is used to specify that a SPIFFS image
16 … Make, from the [project Makefile](./Makefile). `FLASH_IN_PROJECT` specifies that the created image
18 For both build systems, the image is created on the example's build directory with the output filen…
|
| /hal_espressif-3.4.0/zephyr/esp_shared/include/boot/mcuboot_config/ |
| D | mcuboot_config.h | 39 * The default is to support A/B image swapping with rollback. Other modes
40 * with simpler code path, which only supports overwriting the existing image
41 * with the update image or running the newest image directly from its flash
53 * to install the new image, rather than the entire image slot. */
81 * Always check the signature of the image in the primary slot before booting,
107 /* Default maximum number of flash sectors per image slot; change
159 * When a serial recovery process is receiving the image data, this option
161 * default behavior that is erasing whole image size of flash area after
|
| /hal_espressif-3.4.0/docs/en/api-guides/ |
| D | core_dump_internals.rst | 3 Anatomy of core dump image
14 :alt: Core dump image format
17 Core dump ELF image format
21 :alt: Core dump binary image format
24 Core dump binary image format
26 Note: The format of image file showed on the above pictures represents current version of image and…
|
| /hal_espressif-3.4.0/components/app_update/include/ |
| D | esp_ota_ops.h | 24 #define OTA_SIZE_UNKNOWN 0xffffffff /*!< Used for esp_ota_begin() if new image size is unknown */
25 #define OTA_WITH_SEQUENTIAL_WRITES 0xfffffffe /*!< Used for esp_ota_begin() if new image size is un…
30 …A_VALIDATE_FAILED (ESP_ERR_OTA_BASE + 0x03) /*!< Error if OTA app image is invalid */
33 …on state (ESP_OTA_IMG_PENDING_VERIFY), essentially first boot of firmware image post upgrade and h…
65 * The specified partition is erased to the specified image size.
67 * If image size is not yet known, pass OTA_SIZE_UNKNOWN which will
78 …* @param image_size Size of new OTA app image. Partition will be erased in order to receive this s…
108 * - ESP_ERR_OTA_VALIDATE_FAILED: First byte of image contains invalid app image magic byte.
131 * - ESP_ERR_OTA_VALIDATE_FAILED: First byte of image contains invalid app image magic byte.
138 * @brief Finish OTA update and validate newly written app image.
[all …]
|
| /hal_espressif-3.4.0/components/esptool_py/esptool/docs/en/esptool/ |
| D | basic-commands.rst | 47 …eeded as the default is to keep the flash mode and size from the ``.bin`` image file. See the :ref…
91 Flashing an Incompatible Image
94 …shing. If a valid firmware image is detected, the ``Chip ID`` and ``Minimum chip revision`` fields…
95 …If the image turns out to be incompatible with the chip in use or requires a newer chip revision, …
110 …If ``write_flash`` updated the boot image's :ref:`flash mode and flash size <flash-modes>` during …
168 .. _elf-2-image:
181 …ch can be used to set the default values in the image header. This is important when generating an…
182 … skip appending a SHA256 digest after the image. The SHA256 digest would be invalidated by rewriti…
190 …image file suitable for use with a software bootloader stub such as `rboot <https://github.com/rab…
198 …For {IDF_TARGET_NAME}, elf2image produces a single output binary "image file". By default this has…
[all …]
|
| D | advanced-commands.rst | 32 …image (offset {IDF_TARGET_BOOTLOADER_OFFSET} for {IDF_TARGET_NAME}) then any ``--flash_mode``, ``-…
51 The ``load_ram`` command allows the loading of an executable binary image (created with the ``elf2i…
59 …image must only contain IRAM- and DRAM-resident segments. Any SPI flash mapped segments will not l…
138 .. _make-image:
140 Assemble a Firmware Image: make_image
143 …``make_image`` allows you to manually assemble a firmware image from binary segments (such as thos…
153 …In general, it is better to create an ELF image (including any binary data as part of the ELF, by …
|
| /hal_espressif-3.4.0/components/app_update/ |
| D | Kconfig.projbuild | 8 …structure. If not set, time/date stamp will be excluded from app image. This can be useful for get…
9 same binary image files made from the same source, but at different times.
12 bool "Exclude PROJECT_VER from firmware image"
15 The PROJECT_VER variable from the build system will not affect the firmware image.
19 bool "Exclude PROJECT_NAME from firmware image"
22 The PROJECT_NAME variable from the build system will not affect the firmware image.
|
| /hal_espressif-3.4.0/examples/system/ota/ |
| D | README.md | 13 An application on "ESP-Dev-Board" may be upgraded at runtime by downloading a new image via Wi-Fi o…
24 …oad the image contained on the `factory` partition (i.e. the example image). This firmware trigger…
48 …on. The format should be `https://<host-ip-address>:<host-port>/<firmware-image-filename>`, e.g. `…
74 …d close the connection prematurely thus preventing the OTA client from receiving a complete image).
92 2. Connects to the HTTPS server and downloads the new image
93 3. Writes the image to flash, and instructs the bootloader to boot from this image after the next r…
110 This feature allows you to roll back to a previous firmware if new image is not useable. The menuco…
120 …ns are downloaded. Version checking is performed after the first firmware image package containing…
134 …), by running the command `curl -v https://<host-ip-address>:<host-port>/<firmware-image-filename>`
147 - Execute `python -m http.server 8070` in the directory with the firmware image
[all …]
|
| /hal_espressif-3.4.0/docs/en/api-reference/system/ |
| D | app_image_format.rst | 1 App Image Format
4 An application image consists of the following structures:
7 …ta with a length of ``data_len``. The data offset for each segment in the image is calculated in t…
16 To get the list of your image segments, please run the following command:
25 Image version: 1
69 3. The image has a single checksum byte after the last segment. This byte is written on a sixteen b…
71 …f:`CONFIG_SECURE_SIGNED_APPS_SCHEME` is set to ECDSA then the application image will have addition…
95 …e opportunity to have similar structure with a fixed offset relative to the beginning of the image.
96 The following pattern can be used to add a custom structure to your image:
104 To guarantee that the custom structure is located in the image even if it is not used, you need to …
|
| /hal_espressif-3.4.0/examples/system/ota/advanced_https_ota/ |
| D | example_test.py | 115 2. Fetch OTA image over HTTPS
116 3. Reboot with the new OTA image
161 3. Fetch OTA image over HTTPS
170 …# Size of truncated file to be grnerated. This value can range from 288 bytes (Image header size) …
201 dut1.expect('Image validation failed, image is corrupted', timeout=30)
214 3. Fetch OTA image over HTTPS
223 …# Size of truncated file to be grnerated. This value should be less than 288 bytes (Image header s…
265 2. Generate random binary image
266 3. Fetch OTA image over HTTPS
316 2. Fetch OTA image over HTTPS
[all …]
|
| /hal_espressif-3.4.0/components/esp_rom/include/ |
| D | esp_rom_tjpgd.h | 36 JDR_MEM1, /* 3: Insufficient memory pool for the image */
71 …rectangular varies from 1x1 to 16x16 depends on clipping, scaling and sampling factor of the image.
78 * @param rect Specifies rectangular region in the image to output the RGB bitmap
96 uint32_t width, height; /* Size of the input image (pixel) */
117 …c requires upto 3092 bytes of work area depends on the built-in parameter tables of the JPEG image.
126 * - JDR_MEM1 Insufficient work area for this JPEG image.
127 * - JDR_MEM2 Insufficient input buffer for this JPEG image. JD_SZBUF may be too small.
130 * - JDR_FMT2 Right format but not supported. May be a grayscale image.
131 * - JDR_FMT3 Not supported JPEG standard. May be a progressive JPEG image.
136 * @brief Decompress the JPEG image and output it as RGB data.
[all …]
|
| /hal_espressif-3.4.0/examples/system/ota/advanced_https_ota/main/ |
| D | advanced_https_ota_example.c | 62 … * Secure version check from firmware image header prevents subsequent download and flash write of in validate_image_header()
63 * entire firmware image. However this is optional because it is also taken care in API in validate_image_header()
105 ESP_LOGE(TAG, "Configuration mismatch: wrong firmware upgrade image url"); in advanced_ota_example_task()
138 ESP_LOGE(TAG, "image header verification failed"); in advanced_ota_example_task()
148 … the status of OTA upgrade by calling esp_https_ota_get_image_len_read, which gives length of image in advanced_ota_example_task()
150 ESP_LOGD(TAG, "Image bytes read: %d", esp_https_ota_get_image_len_read(https_ota_handle)); in advanced_ota_example_task()
154 …// the OTA image was not completely received and user can customise the response to this situation. in advanced_ota_example_task()
164 ESP_LOGE(TAG, "Image validation failed, image is corrupted"); in advanced_ota_example_task()
203 * process and mark newly updated firmware image as active. For production cases, in app_main()
|
| /hal_espressif-3.4.0/components/esptool_py/esptool/docs/en/espsecure/ |
| D | index.rst | 24 ….html#signing-using-an-external-hsm>`_ to generate a Secure Boot V2 format unsigned firmware image.
26 The following command should be used to get an image signed using an external HSM. ::
30 …s a signature for an image using the HSM, and then creates a signature block and appends it to the…
36 Verifying the Signed Image
39 Once the signed image is generated, we can verify it using the following command: ::
|
| /hal_espressif-3.4.0/components/spiffs/test_spiffsgen/ |
| D | test_spiffsgen.py | 21 an image is generated (there is no exception), and the image size
61 image = spiffs.to_binary()
62 self.assertEqual(len(image), image_size)
64 # config, and verify that the image is parsed correctly.
|
