AT Command Introduction
This specification presents guidelines for software engineers that use Feasycom’s dual-mode(Data+Audio) series of modules.
The AT Command described here supports the modules listed in the table below.
1.1 Terms
{ } ：Content between {…} is optional
1.2 HW Interface
| ♦ | GPIO | |
| ♦ | PWM | |
| ♦ | UART | |
| ♦ | I2C Master/Slave | |
| ♦ | I2S Master/Slave | |
| ♦ | Analog Input/Output |
1.3 Supported Bluetooth Profile
| Profile | Supported Role | |
| SPP | Serial Port Profile | |
| GATT | Generic Attribute Profile | Server, Client |
| HFP | Hans-Free Profile | Sink |
| A2DP | Advanced Audio Distribution Profile | Sink |
| AVRCP | Audio/Video Distribution Profile | Controller, Target |
| HID | Human Interface Profile | Keyboard |
| PBAP | PBAP | Server |
1.4 Command Format
AT+ Command {=Param1{, Param2{, Param3…}}} <CR><LF>
| ♦ | All commands start with “AT”, end with <CR><LF> |
| ♦ | <CR> stands for “carriage return”, corresponding hex is 0x0D |
| ♦ | <LF> stands for “line feed”, corresponding hex is 0x0A |
| ♦ | If command has parameter, parameter keep behind “=” |
| ♦ | If command has multiple parameters, parameter must be separated by “,” |
| ♦ | If command has response, response start with <CR><LF>, end with <CR><LF> |
| ♦ | Module will always report command’s execution result using “OK” for success or “ERROR” for failure |
1.5 Indication Format
<CR><LF>+ Indication {=Param1{, Param2{, Param3…}}} <CR><LF>
| ♦ | All indications start with <CR><LF>, end with <CR><LF> |
| ♦ | If indication has parameter, parameter keep behind “=” |
| ♦ | If indication has multiple parameters, the parameter must be separated by “,” |
| ♦ | Hex value <FF> will be used instead of “,” in some special indications |
1.6 Default Settings
| Items | Default Settings |
| Pin Code | 0000 |
| Secure Simple Pairing Mode | On |
| UART Baud rate | 115200bps/8/N/1 |
