This document mainly introduces how to choose the right Espressif hardware product, AT software solution, and the initial preparation for your project.
Important
If you have any questions regarding the selection of Espressif hardware products or AT software solutions, please contact Espressif Sales or Technical Support.
Hardware SelectionïBefore using ESP-AT, you need to select a suitable Espressif chip to integrate into your product, empowering it with wireless capabilities. Hardware selection is a complex process that requires consideration of various factors such as functionality, power consumption, cost, size, etc. Please read the following content to help you choose the hardware.
Product Selector Tool can help you understand the hardware differences of different Espressif products.
Datasheets can help you understand the hardware capabilities supported by the chip/module.
Board Selection Guide can help you compare the differences between chips, modules, and development boards and provide selection guidance.
Note
The datasheets indicate the maximum hardware capabilities and do not represent the capabilities of the AT software. For example, the ESP32-C6 chip supports Zigbee 3.0 and Thread 1.3, but the existing AT software solutions do not support these two wireless protocols.
AT Software Solution SelectionïAT software solution is the AT firmwares provided by Espressif for different chips, which can help you quickly implement wireless functionality.
If you want to know the detailed AT software capabilities of ESP32 chip, please refer to the AT Command Set.
If you want to compare the different AT firmware functionalities of ESP32 chip, please refer to the ESP-AT Firmware Differences.
The table below shows a brief comparison of the AT firmware for different chips.
Chip
Wireless
AT Firmware
Description
ESP32-C6
Wi-Fi 6 + BLE 5.0
ESP32-C3
Wi-Fi 4 + BLE 5.0
ESP32-C2
Wi-Fi 4 (or BLE 5.0)
ESP32
Wi-Fi 4 + BLE v4.2 (+ BT)
ESP32-S2
Wi-Fi 4
It is recommended to use the more cost-effective ESP32-C series.
(or BLE 5.0) indicates that Bluetooth LE functionality is supported in the AT software solution, but it is not included in the released firmware.
(+ BT) indicates that Classic Bluetooth functionality is supported in the AT software solution, but it is not included in the released firmware.
Note
The modules or chips from the factory are not preloaded with AT firmware. If you have mass production requirements, please contact the corresponding business personnel or sales@espressif.com in a timely manner, and we will provide customized production.
Which Type of AT 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, also known as âreleased firmwareâ, âofficial firmwareâ or âdefault firmwareâ, has passed testing 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.
How to obtain firmware: ESP32 AT firmware
Pros:
Stable
Reliable
Small workload of obtaining firmware
Cons:
Long update cycle
A limited number of supported modules
Reference documentation:
For which chip series are supported and unsupported by ESP-AT firmware, please refer to ESP-AT GitHub home page readme.md
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.
How to obtain firmware: Please refer to How to Download the Latest Temporary Version of AT Firmware from GitHub.
Pros:
Real-time integration of new features and bug fixes.
Covering some unofficially released firmware, such as firmware based on SDIO communication and firmware based on SPI communication.
Small workload of obtaining firmware.
Cons: As the firmware compiled based on commits that are not for official release has not been thoroughly tested, there may be some risks. You need to do a complete test by yourself.
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 UART baud rate and UART GPIO pins. This type of firmware can be directly upgraded based on the Espressif OTA server.
For how to modify those parameters, please refer to at.py Tool.
Pros:
No need to recompile the firmware.
The firmware is stable and reliable.
Cons: Requiring modification to released firmware, long update cycle, and a limited number of supported modules.
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.
For how to compile the firmware by yourself, please refer to Compile ESP-AT Project Locally.
Pros: You can control functions and cycles.
Cons: You need to set up the compilation environment.
If stability is your priority, it is recommended to develop your AT firmware based on the latest released version corresponding to the chip. If you want more new features, it is recommended to develop your AT firmware based on the master branch.
Initial Project PreparationïDuring the initial project preparation phase, it is strongly recommended that you choose Espressif development boards to start your project. In the early stages of the project, it can help you quickly validate prototypes, evaluate hardware and software capabilities, and reduce project risks. In the middle stages of the project, it can help you quickly integrate and verify functions, optimize performance, and improve development efficiency. In the later stages of the project, it can help you quickly simulate and locate issues, and achieve rapid product iteration.
If you are using Self-Compiled Firmware, it is recommended to prioritize using Linux as the development environment.
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