Grove - Wio-E5 stopped responding to AT commands after sending AT+UART=TIMEOUT,0

Products & Technology LoRa
1

Hello Guys,

Need some help,
I was successfully communicating with the Grove - Wio-E5 module by u usb/serial convertor and using MicroRidge ComtestSerial as terminal software.

The Grove - Wio-E5 answered as expected until I did send the AT+UART=TIMEOUT,0 command.
How can I set the timeout back to 300?

Thanks in advance,
Michel

2

Hi,
have you find a way to solve your problem ? I’ve the same !

Thanks.

3

Hi there,

This is Terrible PITA, :face_with_hand_over_mouth: the designers should have thought this through better IMO. Yes — this is a common issue when working with Grove Wio-E5 modules via AT commands.

The AT+UART=TIMEOUT,<value> command configures the UART receive timeout. Unfortunately, if you set TIMEOUT to 0, it disables the internal RX timeout — and in some firmware versions, this may cause the module to stop responding to input entirely (especially in MCU-controlled or USB-to-serial setups).

I ran it through AL and came with these suggestions. YMMV.
With Capt. Obvious warnings ,etc…

First let’s start by preface, the WiKi… You know this part first.
1. Factroy AT Firmare

Wio-E5 series has a built-in AT command firmware, which supports LoRaWAN® Class A/B/C protocol and a wide frequency plan: EU868/US915/AU915/AS923/KR920/IN865. With this AT command firmware, developers can easily and quickly build their prototype or application.

The AT command firmware contains a bootloader for DFU and the AT application. The “PB13/SPI_SCK/BOOT” pin is used to control Wio-E5 to stay in the bootloader or jump to the AT application. When PB13 is HIGH, the module will jump to AT application after reset, with a default baud rate of 9600. When PB13 is LOW (press the “Boot” button on Wio-E5 mini/ Wio-E5 Development Kit), the module will stay in the bootloader, and keep transmitting “C” character every 1S at baud rate 115200.

note

  • Factory AT Firmware is programmed with RDP(Read Protection) Level 1, developers need to remove RDP first with STM32Cube Programmer. Note that regression RDP to level 0 will cause a flash memory mass to erase and the Factory AT Firmware can’t be restored again.
  • The “PB13/SPI_SCK/BOOT” pin on the Wio-E5 module is just a normal GPIO, not the “BOOT0” pin of the MCU. This “PB13/SPI_SCK/BOOT” pin is used in the bootloader of the Factory AT firmware, to decide to jump to APP or stay in bootloader(for DFU). The real “BOOT0” pin doesn’t pinout to the module, so users need to be careful when developing the low-power applications.

Seems insane the Factory Image , or bin is NOT Available… Someone should really address that and work to resolve it. (soapbox=off) :mega:

the restore AT command would be , " AT+UART=TIMEOUT,300 " but since it is already set to “0” it’s not responding.

Long shot but try this:

1. Power Cycle and Retry Quickly

  • Disconnect power.
  • Reconnect.
  • Immediately send AT+UART=TIMEOUT,300\r\n before the timeout mechanism locks things up.

Some versions resume a default timeout after reset, giving a small window. it’s worth a shot, it’s like a glitch if you get it timed right. :crossed_fingers:

other methods are enter bootloader mode , and reflash ,but can’t do that without a bin or hex factory. would be good if we even knew which location to patch to get them back?
Maybe someone from seeed dream team can comment or better yet provide the firmware file :grin: :bow:

HTH
GL :slight_smile: PJ :v:

maybe putting it in Bootloader mode and reset might reset it, worth a try as well.

BOOT Recovery Wiring (for STM32 Bootloader)

Wio-E5 Pin Connect To
Pin 1 (VCC) 3.3V power
Pin 2 (GND) GND
Pin 7 (TX) RX of USB-UART
Pin 8 (RX) TX of USB-UART
Pin 9 (BOOT) GND (pull low)

:warning: Make sure to connect BOOT to GND before powering the module.
check the WikI for more…

4

Even if the terminal seems unresponsive, try sending:

AT+UART=TIMEOUT,300

Type it manually and hit Enter — the command might still be accepted despite no echo or response.

5

Thank you for answers. Problem was with minicom software, but, with serial communication with python it’s ok, I could change the timeout…

1 Like
6

Hi there…

That’s Great…and Lucky :crossed_fingers: …Still makes me pause but I see there are 3rd party “AT” type functional libs out in the wild, so there’s that. :grin:

GL :slight_smile: PJ :v: