ARM-software / CMSIS-Driver

Repository of microcontroller peripheral driver implementing the CMSIS-Driver API specification

Home Page:https://arm-software.github.io/CMSIS-Driver/

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

ESP32 baud rate change with AT 2.1

xennex22 opened this issue · comments

The board rate change logic does not work with the ESP32 AT firmware 2.0 or 2.1

The reason is that the AT command to test if communications are good at the current baud rate may return an ERROR from a previous AT command at the wrong baud rate. Since if we are just trying to sync baud rates ERROR is as good as OK.

if (ex == AT_RESP_OK) {

Change to

/* response might be OK or ERROR (from last bad baud attempt) */
if ((ex == AT_RESP_OK) || (ex == AT_RESP_ERROR)) {

Hi,
thanks for reporting this. Unfortunately the driver was not yet validated with any of AT 2.x firmware because we have seen instabilities in ESP32 transfer functions.
Currently the driver is only validated for use with AT 1.2.0.0 which passed the socket transfer validation tests:

This test report was produced with following configuration:
- Hardware: NXP MIMXRT1064-EVK board with ESP32-WROOM-32D on SparkFun ESP32 Thing Plus
- Firmware: AT Command Set 1.2.0.0
- Interface: UART at 115200 bps
Packs used for test:
- ARM::CMSIS 5.7.0
- ARM::CMSIS-Driver 2.6.0
- ARM::CMSIS-Driver_Validation 2.0.0
- Keil::ARM_Compiler 1.6.2
- NXP MIMXRT1064_DFP 12.1.0
- NXP EVK-MIMXRT1064_BSP 12.1.0
AT Version Information (AT+GMR):
- AT version:1.2.0.0(6fe4345 - Jun 27 2019 05:39:23)
- SDK version:v3.2-127-gddbce78
- compile time:Jun 27 2019 12:08:01
- Bin version:1.2.0(WROOM-32)

We will take this issue into account and check what needs to be done in order to get the driver running with ESP32 AT 2.x firmware.

Thank you. If I can find AT 1.2.0.0 I will re-test on that version.

If you asked me 30 years again when I was working on AT commands for modems that I would still be using the AT commands in 2021 I would have quit and become a carpenter.

The firmware is listed under releases here https://github.com/espressif/esp-at/releases (last release before V2.0).

The driver has been updated - the fix you suggested was added and I also tested the driver with ESP32 AT 2.1.0.0 which now passes our validation suite without any failed tests.

The recommended firmware version is now ESP32 AT 2.1.0.0 since it behaves very stable (definitively more stable that 2.0.0.0). Although you maybe already flashed your ESP32 to AT 1.2.0.0 I would now recommend going back to 2.1.0.0.

Thank you.