You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
- Added http new errno
- Added single/multiple connection notes for related commands
- Added AT+CIPDINFO query command doc
- Added blufi support notes for ESP32
- Added one note for ESP32-WROVER
- Updated AT+CIPRECVMODE notes about link closed
- Updated ESP32-C3 released time
- Fixed wrong response of AT+CWDHCP query command
- Closesespressif#576
Copy file name to clipboardExpand all lines: README.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -30,7 +30,7 @@ The AT command firmware allows for rapid integration by providing:
30
30
- The [esp-at forum](https://www.esp32.com/viewforum.php?f=42) is a place to ask questions and find community resources.
31
31
32
32
# Project Roadmap
33
-
1. The next version of ESP-AT firmware (v2.3.0.0) is planned to be released in October 2021. At present, only ESP32-C3 series firmware is planned to be released, and ESP32-C3 firmware would support Bluetooth LE.
33
+
1. The next version of ESP-AT firmware (v2.4.0.0) is planned to be released in March 2022. At present, only ESP32-C3 series firmware is planned to be released, and ESP32-C3 firmware would support Bluetooth LE 5.0.
Copy file name to clipboardExpand all lines: docs/en/AT_Command_Set/BLE_AT_Commands.rst
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -5,7 +5,7 @@ Bluetooth® Low Energy AT Commands
5
5
6
6
:link_to_translation:`zh_CN:[中文]`
7
7
8
-
Currently, both ESP32 and ESP32-C3 support Bluetooth LE commands. AT firmware for ESP32 series supports `Bluetooth® Core Specification Version 4.2 <https://www.bluetooth.com/specifications/specs/core-specification-4-2/>`_, and AT firmware for ESP32-C3 supports `Bluetooth® Core Specification Version 5.0 <https://www.bluetooth.com/specifications/specs/core-specification-5/>`_.
8
+
Currently, both ESP32 and ESP32-C3 support Bluetooth LE commands. AT firmware for ESP32 series and ESP32-C3 series supports `Bluetooth® Core Specification Version 4.2 <https://www.bluetooth.com/specifications/specs/core-specification-4-2/>`_. Next AT firmware for ESP32-C3 will support `Bluetooth® Core Specification Version 5.0 <https://www.bluetooth.com/specifications/specs/core-specification-5/>`_.
9
9
10
10
- :ref:`AT+BLEINIT <cmd-BINIT>`: Bluetooth LE initialization.
11
11
- :ref:`AT+BLEADDR <cmd-BADDR>`: Query/Set Bluetooth LE device address.
- ``<len>`` is the total length of socket data in the buffer.
2063
2132
- You should read data by running :ref:`AT+CIPRECVDATA <cmd-CIPRECVDATA>` once there is a ``+IPD`` reported. Otherwise, the next ``+IPD`` will not be reported to the host MCU until the previous ``+IPD`` has been read.
2064
-
- In case of disconnection, the buffered socket data will still be there and can be read by the MCU until you send :ref:`AT+CIPCLOSE <cmd-CLOSE>`. In other words, if ``+IPD`` has been reported, the message ``CLOSED`` of this connection will never come until you send :ref:`AT+CIPCLOSE <cmd-CLOSE>` or read all data by command :ref:`AT+CIPRECVDATA <cmd-CIPRECVDATA>`.
2133
+
- In case of disconnection, the buffered socket data will still be there and can be read by the MCU until you send :ref:`AT+CIPCLOSE <cmd-CLOSE>` (AT as client) or :ref:`AT+CIPSERVER=0,1 <cmd-SERVER>` (AT as server). In other words, if ``+IPD`` has been reported, the message ``CLOSED`` of this connection will never come until you send :ref:`AT+CIPCLOSE <cmd-CLOSE>` or :ref:`AT+CIPSERVER=0,1 <cmd-SERVER>` or read all data by command :ref:`AT+CIPRECVDATA <cmd-CIPRECVDATA>`.
0 commit comments