A RetroSearch Logo

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Search Query:

Showing content from https://docs.espressif.com/projects/esp-at/en/release-v3.3.0.0/esp32c3/AT_Binary_Lists/index.html below:

Website Navigation


AT Binary Lists - ESP32-C3

AT Binary Lists

[中文]

This document covers the following sections:

Note

To download AT firmware for other chip series, please go to the drop-down list on the upper left corner of this page and select a chip series to navigate to the documentation of that chip for downloading.

Brief Introduction to AT Firmware

The ESP-AT firmware package contains several binary files for specific functionalities:

build
├── at_customize.bin        // Secondary partition table (user partition table, listing the start address and size of the mfg_nvs partition and fatfs partition)
├── bootloader
│   └── bootloader.bin      // Bootloader
├── customized_partitions
│   └── mfg_nvs.bin         // Factory configuration parameters, parameter values are listed in the mfg_nvs.csv file in the same directory
├── esp-at.bin              // AT application firmware
├── factory
│   └── factory_xxx.bin     // Collection of binary files for specific functionalities. You can burn only this file to the flash space with a starting address of 0, or burn several binary files to the flash space corresponding to the starting address according to the information in the download.config file.
├── partition_table
│   └── partition-table.bin // Primary partition table (system partition table)
└── ota_data_initial.bin    // OTA data initialization file
Which Type of Firmware Shall I Choose?

ESP-AT firmware has the following types. Among them, the workload of downloading or preparing firmware increases from top to bottom, and so does the number of supported module types.

Officially Released Firmware (Recommended)

Officially released firmware, also known as “released firmware”, “official firmware” or “default firmware”, is tested and periodically released by Espressif’s official team according to the internal development plan. It can be upgraded directly based on the Espressif OTA server. If it fully matches your project needs, it is recommended to choose it over the other types of firmware. If it does not support your module, you can select a firmware that has a similar hardware configuration to your module according to Hardware Differences for testing and verification.

GitHub Temporary Firmware

GitHub temporary firmware is compiled by GitHub whenever code is pushed to GitHub and yet does not reach the firmware release cycle. In other words, it is the firmware in development, including the temporary versions of officially released firmware and supported firmware that is not planned for release. The former can be upgraded directly based on the Espressif OTA server.

Firmware with Updated Parameters

The firmware with updated parameters is generated by updating the parameter area and you do not need to compile the firmware. It is suitable for the case where the firmware function meets the project requirements, but only some parameters do not, such as the factory baud rate and UART IO pins. This type of firmware can be directly upgraded based on the Espressif OTA server.

Self-Compiled Firmware

When you need to conduct secondary development, you can compile the firmware by yourself. To support the OTA function, you need to deploy your own OTA server.

After Getting Firmware, What Next?

After you get the firmware, please refer to Hardware Connection and Firmware Downloading and Flashing Guide to connect the PC and ESP device and flash the firmware to the device.

Provide feedback about this document


RetroSearch is an open source project built by @garambo | Open a GitHub Issue

Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo

HTML: 3.2 | Encoding: UTF-8 | Version: 0.7.4