Differences

This shows you the differences between two versions of the page.

--- en:iot-open:espressif_at [2023/11/23 11:51] – pczekalski
+++ en:iot-open:espressif_at [2024/05/27 10:33] (current) – [ESP AT Networking] pczekalski
@@ Line 4: / Line 4: @@
 <figure esp_at>
-{{ :en:iot-open:getting_familiar_with_your_hardware_rtu_itmo_sut:esp:esp_at.png?nolink&200 | ESP8266 as a modem}}
+{{ :en:iot-open:getting_familiar_with_your_hardware_rtu_itmo_sut:esp:esp_at.png?250 | ESP8266 as a modem}}
 <caption>ESP8266 as a modem</caption>
 </figure>
 <note>
-AT commands were developed to control telephony modems. They are often used to control modules connected via a serial port. This includes GPS receivers, GSM/LTE modems, network modules and others.
+AT commands were developed to control telephony modems. They are often used to control modules connected via a serial port, including GPS receivers, GSM/LTE modems, network modules, and others.
 </note>
@@ Line 22: / Line 22: @@
   * Download the latest AT release from ((https://bbs.espressif.com/viewforum.php?f=46))
 The newest version of Espressif firmware is not compatible with ESP8266 SoCs. In the case of using ESP8266-based boards, download older AiThinker firmware available on GitHub ((http://www.electrodragon.com/w/ESP8266_AT-Command_firmware)).
-The firmware can come in different versions. It can be a set of binary files which must be uploaded at specific memory addresses or as a combined single binary file. Note that a single file is prepared for a particular flash memory size.
+The firmware can come in different versions. It can be a set of binary files that must be uploaded to specific memory addresses or as a combined single binary file. Note that a single file is prepared for a particular flash memory size.
 ==Flashing Procedure with single binary file==
@@ Line 28: / Line 28: @@
 <figure AT_flash>
-{{ :en:iot-open:getting_familiar_with_your_hardware_rtu_itmo_sut:esp:readd1.jpg?nolink&400 | Programming ESP8266 - detected parameters}}
+{{ :en:iot-open:getting_familiar_with_your_hardware_rtu_itmo_sut:esp:readd1.jpg?400 | Programming ESP8266 - detected parameters}}
 <caption>Programming ESP8266 - detected parameters</caption>
 </figure>
@@ Line 36: / Line 36: @@
 <figure AT_load>
-{{ :en:iot-open:getting_familiar_with_your_hardware_rtu_itmo_sut:esp:flashd1.jpg?nolink&400 | Programming ESP8266 - setting proper image file}}
+{{ :en:iot-open:getting_familiar_with_your_hardware_rtu_itmo_sut:esp:flashd1.jpg?400 | Programming ESP8266 - setting proper image file}}
 <caption>Programming ESP8266 - setting proper image file</caption>
 </figure>
@@ Line 46: / Line 46: @@
 <figure AT_flash1>
-{{ :en:iot-open:getting_familiar_with_your_hardware_rtu_itmo_sut:esp:readd1.jpg?nolink&400 | Programming ESP8266 - detected parameters}}
+{{ :en:iot-open:getting_familiar_with_your_hardware_rtu_itmo_sut:esp:readd1.jpg?400 | Programming ESP8266 - detected parameters}}
 <caption>Programming ESP8266 - detected parameters</caption>
 </figure>
@@ Line 86: / Line 86: @@
   * Indicate -- correct for your ESP8266 flash size -- firmware files & addresses. The firmware is broken down into several files. They must be provided to the ESP Flash Download Tool and the corresponding addresses in the readme.txt file above. For our ESP8266 example, it should look like in figure {{ref>AT_reflash}}.
 <figure AT_reflash>
-{{ :en:iot-open:getting_familiar_with_your_hardware_rtu_itmo_sut:esp:reflashd2.jpg?nolink&600 | Programming ESP8266 - reflashing settings}}
+{{ :en:iot-open:getting_familiar_with_your_hardware_rtu_itmo_sut:esp:reflashd2.jpg?600 | Programming ESP8266 - reflashing settings}}
 <caption>Programming ESP8266 - reflashing settings</caption>
 </figure>

en/iot-open/espressif_at.1700740316.txt.gz · Last modified: 2023/11/23 11:51 by pczekalski