RAK11160 BLE/WIFI AT commands problem

OS:Windows 11
Module: RAK11160

USB/UART connected to 40, 41 (ST_UART2)

I can program STM32 using Arduino IDE and also restore default firmware: RAK11160_latest_final.hex (ST LINK, STM32CubeProgrammer)
RAK11160_latest.bin (RAK_Device_Firmware_Upgrade_Tool_v1.4)

I can not use BLE or WIFI by AT commands:
AT+VER=?
AT+VER=RUI_4.2.2_RAK11160
AT+BLEINIT?
AT_COMMAND_NOT_FOUND
AT
OK
AT+CWINIT?
AT_COMMAND_NOT_FOUND
AT
OK

Can you advise how to solve the above problem?

Welcome to RAK forum @Dzony

RAK11160 has ESP32C2 inside which has limited memory space. By default, the FW in it only works on WiFi functionality. I am still checking with the team the compatible BLE but take note that you cannot make them work simultaneously, the Espressif FW for ESP32C2 has one dedicated for WiFi functionality and one for BLE.

If you need both WiFi and BLE simultaneously in your usecase, a more powerful chip might be needed, the ESP32S3 inside RAK3112.

Please reread my post. I don’t want to use them simultaneously. I want to use one of them. Both failed to respond to the AT command as described above. Could you help?

Hi @Dzony ,

You can pass-thru an AT command to the ESP32C2 by sending AT+ESP=1.

To ensure that it is active, you can send AT+ESPPOWER=1. The latter command pull down the reset pin of internally if the value is 0 making the ESP32C2 in inactive state.

Hi @carlrowan,

below is the result of my last attempt 40,41 (ST_PA2/ST_UART2_TX, ST_PA3/ST_UART2_RX):

AT
OK
AT+VER=?
AT+VER=RUI_4.2.2_RAK11160
OK
AT+ESP=1
OK
ready

Unfortunately, after the AT+ESP=1 command, the device stopped responding. I tried sending the AT+ESPOWER=1 command, but received no response.

I rewired UART to 30, 31 (ESP_GPIO19/ESP_UART_RX, ESP_GPIO20/ESP_UART_TX) when I changed PA0=LOW → PA0=HIGH I get the following response (30,31) at baud=74880:

ESP-ROM:esp8684-api2-20220127
Build:Jan 27 2022
rst:0x1 (POWERON),boot:0x8 (SPI_FAST_FLASH_BOOT)
SPIWP:0xee
mode:DIO, clock div:1
load:0x3fcd5d20,len:0x18c4
load:0x403acb70,len:0xa00
load:0x403aeb70,len:0x28e8
load:0x403ba000,len:0x22c0
entry 0x403acb70

Hi @Dzony ,

When you sent AT+ESP=1, you got a ready reply which coming from the ESP32C2 inside RAK11160. This means AT commands of RUI3 will not work anymore but the AT commands of ESP32. To go back to RUI3 AT Commands, you need to send AT+ESP=0.

I tried sending AT commands of ESP32 (Basic AT Commands - ESP32-C2 - — ESP-AT User Guide latest documentation):
AT
AT+GMR
I also tried sending the AT+ESP=0 command, but I always got no response.

Currently, does it reply to RUI3 AT commands? But not on ESP32? Or it does not reply to any commands at all? AT+ESP=0 should allow RUI3 AT commands at 115200 baudrate. Also, please ensure that the UART wirings are stable.

After power restart it reply to RUI3 AT commands. After AT+ESP=1 it responds
OK
ready
After that it does not respond to any commands at all (regardless of the baud rate).

UART connection is perfectly stable.

Hi Dzony,

That’s strange. Hmm.

  1. It will be good if you can try to reupload the FW via STM32CubeProgrammer. Flash erase as well. Just to be sure that we are dealing with a fresh module without any custom FW modifcation.
  2. When you receive ready, it is now in ESP32 passthru so you can only send AT commands compatible to ESP32. This guide might be a good reference.

I have already programmed RUI firmware (from the RAK webside) via STlink. That didn’t solve the problems. Maybe there is problem with ESP module?

Hi @Dzony ,

That’s possible. For replacement, please reach out to [email protected]. You can mention that you already discuss the issue with Carl Rowan in the RAK forum.

Maybe you are missing the “=” sign in your command?

No missing.

wt., 13 sty 2026, 17:39 użytkownik Ricky Chang via RAKwireless Forum <[email protected]> napisał:

Could you provide ESP firmware? I could try reprogram it.

Hi @Dzony ,

The FW and guide are here - https://dl.espressif.com/esp-at/firmwares/esp32c2/ESP32-C2-2MB-AT-V4.1.1.0.zip

On our first batches of RAK11160, we got v3.3.x.x but now, modules have v4.1.1.0.