When using sdio-at at esp32, the AT commands sent did not respond.

[Misanic]

When I used sdio-at on the esp32, after my host computer sent the AT command to the esp32, the esp32 did not respond. Only at the very beginning could I receive the "ready" message sent by the esp32.

I am using the esp32-wroom-32e n16r2 postage module. The firmware I burned is the latest v4.2.0.0-dev (unknown), and the esp-idf version is 5.5.1. The upper-level device is my own development board.

I have an older esp32_devkitc_v4 board, with the version 2.0 AT firmware burned onto it. I independently developed an SDIO AT WiFi driver for controlling the esp32. It worked fine on the old development board, but encountered this issue on the new esp32 module.

The startup log of the esp32 is as follows:
rst:0x1 (POWERON_RESET),boot:0x13 (SPI_FAST_FLASH_BOOT)
configsip: 153911750, SPIWP:0xee
clk_drv:0x00,q_drv:0x00,d_drv:0x00,cs0_drv:0x00,hd_drv:0x00,wp_drv:0x00
mode:DIO, clock div:2
load:0x3fff0030,len:6268
ho 0 tail 12 room 4
load:0x40078000,len:16132
load:0x40080400,len:4
--- 0x40080400: _init at ??:?
load:0x40080404,len:3612
entry 0x40080608
I (32) boot: ESP-IDF v5.4.1-643-g8ad0d3d8f2-dirty 2nd stage bootloader
I (32) boot: compile time Dec 12 2025 09:08:42
W (32) boot: Unicore bootloader
I (35) boot: chip revision: v3.1
I (38) boot.esp32: SPI Speed : 40MHz
I (41) boot.esp32: SPI Mode : DIO
I (45) boot.esp32: SPI Flash Size : 16MB
I (49) boot: Enabling RNG early entropy source...
I (53) boot: Partition Table:
I (56) boot: ## Label Usage Type ST Offset Length
I (62) boot: 0 phy_init RF data 01 01 0000f000 00001000
I (69) boot: 1 otadata OTA data 01 00 00010000 00002000
I (75) boot: 2 nvs WiFi data 01 02 00012000 0000e000
I (82) boot: 3 at_customize unknown 40 00 00020000 000e0000
I (88) boot: 4 ota_0 OTA app 00 10 00100000 00200000
I (95) boot: 5 ota_1 OTA app 00 11 00300000 00200000
I (101) boot: End of partition table
I (104) esp_image: segment 0: paddr=00100020 vaddr=3f400020 size=29870h (170096) map
I (170) esp_image: segment 1: paddr=00129898 vaddr=3ff80064 size=0001ch ( 28) load
I (170) esp_image: segment 2: paddr=001298bc vaddr=3ffbdb60 size=05e60h ( 24160) load
I (183) esp_image: segment 3: paddr=0012f724 vaddr=40080000 size=008f4h ( 2292) load
I (184) esp_image: segment 4: paddr=00130020 vaddr=400d0020 size=13eb88h (1305480) map
I (635) esp_image: segment 5: paddr=0026ebb0 vaddr=400808f4 size=1a6a4h (108196) load
I (677) esp_image: segment 6: paddr=0028925c vaddr=400c0000 size=00064h ( 100) load
I (691) boot: Loaded app from partition at offset 0x100000
I (691) boot: Disabling RNG early entropy source...
I (954) at-init: at param mode: 1
I (1072) at-init: module_name: ESP32-SDIO
I (1074) at-init: max tx power=78, ret=0
I (1076) at-init: v4.2.0.0-dev (unknown)
E (1077) at-sdio: invalid data:0 or len:-1

The AT commands sent by the host computer for initializing the ESP driver are as follows:
[09:48:02.223]发→◇esp_reg
□
[09:48:02.572]收←◆esp_reg
[I/DBG] esp register ......

[I/DBG] read function enable state:0

[I/DBG] read function ready state:2, cnt=0

[I/DBG] esp wifi function number is 1

[I/DBG] [esp32_read_reg]--1--cur_cmd_type: 0
[I/DBG] [esp32_read_reg]--2--cur_cmd_type: 0
[I/DBG] [esp32_read_reg]--1--cur_cmd_type: 0
[I/DBG] [esp32_read_reg]--2--cur_cmd_type: 0
[D/DBG] Send AT cmd: ATE0

[I/DBG] [esp32_read_reg]--1--cur_cmd_type: 1
[I/DBG] [esp32_read_reg]--1--cur_cmd_type: 0
[I/DBG] [esp32_read_reg]--2--cur_cmd_type: 0
[D/DBG] [esp_get_rx_data_size]esp32_read_reg return size: 9
[I/DBG] [rt_esp32_func1_interrupt]read rx data size get read len: 9
[D/DBG] [esp32_new_handle_response]--handle get data:
ready

esp station ready...
[I/DBG] [esp32_read_reg]--2--cur_cmd_type: 0
[I/DBG] first got blk num=10
[I/DBG] [esp32_read_reg]--1--cur_cmd_type: 0
[I/DBG] [esp32_read_reg]--2--cur_cmd_type: 0
[I/DBG] [esp32_read_reg]--1--cur_cmd_type: 0
[I/DBG] [esp32_read_reg]--2--cur_cmd_type: 0
[I/DBG] [esp32_read_reg]--1--cur_cmd_type: 0
[I/DBG] [esp32_read_reg]--2--cur_cmd_type: 0
[I/DBG] [esp32_read_reg]--1--cur_cmd_type: 0
[I/DBG] [esp32_read_reg]--2--cur_cmd_type: 0
[I/DBG] [esp32_read_reg]--1--cur_cmd_type: 0
[I/DBG] [esp32_read_reg]--2--cur_cmd_type: 0
[I/DBG] [esp32_read_reg]--1--cur_cmd_type: 0
[I/DBG] [esp32_read_reg]--2--cur_cmd_type: 0
[I/DBG] [esp32_read_reg]--1--cur_cmd_type: 0
[I/DBG] [esp32_read_reg]--2--cur_cmd_type: 0
[I/DBG] [esp32_read_reg]--1--cur_cmd_type: 0
[I/DBG] [esp32_read_reg]--2--cur_cmd_type: 0
[I/DBG] [esp32_read_reg]--1--cur_cmd_type: 0
[I/DBG] [esp32_read_reg]--2--cur_cmd_type: 0
[I/DBG] [esp32_read_reg]--1--cur_cmd_type: 0
[I/DBG] [esp32_read_reg]--2--cur_cmd_type: 0
[I/DBG] [esp32_read_reg]--1--cur_cmd_type: 0
[I/DBG] [esp32_read_reg]--2--cur_cmd_type: 0
[I/DBG] [esp32_read_reg]--1--cur_cmd_type: 0
[I/DBG] [esp32_read_reg]--2--cur_cmd_type: 0
[I/DBG] [esp32_read_reg]--1--cur_cmd_type: 0
[I/DBG] [esp32_read_reg]--2--cur_cmd_type: 0
[I/DBG] [esp32_read_reg]--1--cur_cmd_type: 0
[I/DBG] [esp32_read_reg]--2--cur_cmd_type: 0
[I/DBG] [esp32_read_reg]--1--cur_cmd_type: 0
[I/DBG] [esp32_read_reg]--2--cur_cmd_type: 0
[I/DBG] [esp32_read_reg]--1--cur_cmd_type: 0
[I/DBG] [esp32_read_reg]--2--cur_cmd_type: 0
[I/DBG] [esp32_read_reg]--1--cur_cmd_type: 0
[I/DBG] [esp32_read_reg]--2--cur_cmd_type: 0
[I/DBG] [esp32_read_reg]--1--cur_cmd_type: 0
[I/DBG] [esp32_read_reg]--2--cur_cmd_type: 0
[I/DBG] [esp32_read_reg]--1--cur_cmd_type: 0
[I/DBG] [esp32_read_reg]--2--cur_cmd_type: 0
[I/DBG] [esp32_read_reg]--1--cur_cmd_type: 0
[I/DBG] [esp32_read_reg]--2--cur_cmd_type: 0
[I/DBG] [esp32_read_reg]--1--cur_cmd_type: 0
[I/DBG] [esp32_read_reg]--2--cur_cmd_type: 0
[I/DBG] [esp32_read_reg]--1--cur_cmd_type: 0
[I/DBG] [esp32_read_reg]--2--cur_cmd_type: 0
[I/DBG] [esp32_read_reg]--1--cur_cmd_type: 0
[I/DBG] [esp32_read_reg]--2--cur_cmd_type: 0
[I/DBG] [esp32_read_reg]--1--cur_cmd_type: 0
[I/DBG] [esp32_read_reg]--2--cur_cmd_type: 0
[I/DBG] [esp32_read_reg]--1--cur_cmd_type: 0
[I/DBG] [esp32_read_reg]--2--cur_cmd_type: 0
[I/DBG] [esp32_read_reg]--1--cur_cmd_type: 0
[I/DBG] [esp32_read_reg]--2--cur_cmd_type: 0
[I/DBG] [esp32_read_reg]--1--cur_cmd_type: 0
[I/DBG] [esp32_read_reg]--2--cur_cmd_type: 0
[I/DBG] [esp32_read_reg]--1--cur_cmd_type: 0
[I/DBG] [esp32_read_reg]--2--cur_cmd_type: 0
[I/DBG] [esp32_read_reg]--1--cur_cmd_type: 0
[I/DBG] [esp32_read_reg]--2--cur_cmd_type: 0
[I/DBG] [esp32_read_reg]--1--cur_cmd_type: 0
[I/DBG] [esp32_read_reg]--2--cur_cmd_type: 0
[I/DBG] [esp32_read_reg]--1--cur_cmd_type: 0
[I/DBG] [esp32_read_reg]--2--cur_cmd_type: 0
[I/DBG] [esp32_read_reg]--1--cur_cmd_type: 0
[I/DBG] [esp32_read_reg]--2--cur_cmd_type: 0
[I/DBG] [esp32_read_reg]--1--cur_cmd_type: 0
[I/DBG] [esp32_read_reg]--2--cur_cmd_type: 0
[I/DBG] [esp32_read_reg]--1--cur_cmd_type: 0
[I/DBG] [esp32_read_reg]--2--cur_cmd_type: 0
[I/DBG] [esp32_read_re
[09:48:02.798]收←◆g]--1--cur_cmd_type: 0
[I/DBG] [esp32_read_reg]--2--cur_cmd_type: 0
[I/DBG] [esp32_read_reg]--1--cur_cmd_type: 0
[I/DBG] [esp32_read_reg]--2--cur_cmd_type: 0
[I/DBG] [esp32_read_reg]--1--cur_cmd_type: 0
[I/DBG] [esp32_read_reg]--2--cur_cmd_type: 0
[I/DBG] [esp32_read_reg]--1--cur_cmd_type: 0
[I/DBG] [esp32_read_reg]--2--cur_cmd_type: 0
[I/DBG] [esp32_read_reg]--1--cur_cmd_type: 0
[I/DBG] [esp32_read_reg]--2--cur_cmd_type: 0
[I/DBG] [esp32_read_reg]--1--cur_cmd_type: 0
[I/DBG] [esp32_read_reg]--2--cur_cmd_type: 0
[I/DBG] [esp32_read_reg]--1--cur_cmd_type: 0
[I/DBG] [esp32_read_reg]--2--cur_cmd_type: 0
[I/DBG] [esp32_read_reg]--1--cur_cmd_type: 0
[I/DBG] [esp32_read_reg]--2--cur_cmd_type: 0
[I/DBG] [esp32_read_reg]--1--cur_cmd_type: 0
[I/DBG] [esp32_read_reg]--2--cur_cmd_type: 0
[I/DBG] [esp32_read_reg]--1--cur_cmd_type: 0
[I/DBG] [esp32_read_reg]--2--cur_cmd_type: 0
[I/DBG] [esp32_read_reg]--1--cur_cmd_type: 0
[I/DBG] [esp32_read_reg]--2--cur_cmd_type: 0
[I/DBG] [esp32_read_reg]--1--cur_cmd_type: 0
[I/DBG] [esp32_read_reg]--2--cur_cmd_type: 0
[I/DBG] [esp32_read_reg]--1--cur_cmd_type: 0
[I/DBG] [esp32_read_reg]--2--cur_cmd_type: 0
[I/DBG] [esp32_read_reg]--1--cur_cmd_type: 0
[I/DBG] [esp32_read_reg]--2--cur_cmd_type: 0
[I/DBG] [esp32_read_reg]--1--cur_cmd_type: 0
[I/DBG] [esp32_read_reg]--2--cur_cmd_type: 0
[I/DBG] [esp32_read_reg]--1--cur_cmd_type: 0
[I/DBG] [esp32_read_reg]--2--cur_cmd_type: 0
[I/DBG] [esp32_read_reg]--1--cur_cmd_type: 0
[I/DBG] [esp32_read_reg]--2--cur_cmd_type: 0
[I/DBG] [esp32_read_reg]--1--cur_cmd_type: 0
[I/DBG] [esp32_read_reg]--2--cur_cmd_type: 0
[I/DBG] [esp32_read_reg]--1--cur_cmd_type: 0
[I/DBG] [esp32_read_reg]--2--cur_cmd_type: 0
[I/DBG] [esp32_read_reg]--1--cur_cmd_type: 0
[I/DBG] [esp32_read_reg]--2--cur_cmd_type: 0
[I/DBG] [esp32_read_reg]--1--cur_cmd_type: 0
[I/DBG] [esp32_read_reg]--2--cur_cmd_type: 0
[I/DBG] [esp32_read_reg]--1--cur_cmd_type: 0
[I/DBG] [esp32_read_reg]--2--cur_cmd_type: 0
[I/DBG] [esp32_read_reg]--1--cur_cmd_type: 0
[I/DBG] [esp32_read_reg]--2--cur_cmd_type: 0
[I/DBG] [esp32_read_reg]--1--cur_cmd_type: 0
[I/DBG] [esp32_read_reg]--2--cur_cmd_type: 0
[I/DBG] [esp32_read_reg]--1--cur_cmd_type: 0
[I/DBG] [esp32_read_reg]--2--cur_cmd_type: 0
[E/DBG] [esp32_wait_blks] wait buffer=20 timeout
[E/DBG] [esp32_write_packet2] wait blks error
[E/DBG] ATE0 error -17

[E/DBG] register esp32 failed

Since I was able to receive the "ready" message sent by the ESP32, I believe there is no problem with my SDIO communication. So, is it the result of version updates that the AT commands applicable to the old version no longer work with the new version of the AT firmware?

[Jacques-Zhao]

1. Since you have received "ready", this indicates that the SDIO communication is functioning properly.
2. The data sent by SDIO includes certain procedures. Have you noticed any error messages?
3. What SDIO mode are you currently using? Is it possible to use 1bit 20M for testing?

[Misanic]

@Jacques-Zhao

1. The Log indicates that the SDIO has timed out waiting for a response, and there are no other error messages.
2. My SDIO mode is 4-bit SDR12, which is feasible when communicating with my old version AT firmware-based ESP32 development board.
3. There are some issues with the triggering of the SDIO interrupt in the 1-bit mode, so debugging cannot be performed in this mode.

[ustccw]

@Misanic Hi, esp32 should use esp-idf ~v5.4.2, not v5.5.1, could you please check if changed this?
btw, you can Enable AT Interface Function Debugging to see what happened.

[Jacques-Zhao]

The reason why I suggest you use 1-bit is that 4-bit is more sensitive to timing. Especially when using DuPont cables for connection, even very short wires can easily cause communication errors. And often, just like you mentioned, the "ready" signal may be received, but the subsequent data transmission may be abnormal.

[Misanic]

@Misanic Hi, esp32 should use esp-idf ~v5.4.2, not v5.5.1, could you please check if changed this? btw, you can Enable AT Interface Function Debugging to see what happened.

Thank you for your suggestion! I tried changing the idf version to 5.4.2, but the problem still persisted. I started the AT Interface Function Debugging. It seems that for some reason, after I sent an SDIO message to the esp32, the main thread of the esp32 firmware ended. Here is the detailed log content:

[18:16:01.263]收←◆蔱ts Jul 29 2019 12:21:46
ts Jul 29 2019 12:21:46

rst:0x1 (POWERON_RESET),boot:0x3f (SPI_FAST_FLASH_BOOT)
configsip: 153911750, SPIWP:0xee
clk_drv:0x00,q_drv:0x00,d_drv:0x00,cs0_drv:0x00,hd_drv:0x00,wp_drv:0x00
mode:DIO, clock div:2
load:0x3fff0030,len:6268
ho 0 tail 12 room 4
load:0x40078000,len:16132
load:0x40080400,len:4
load:0x40080404,len:3616
entry 0x40080608
I (32) boot: ESP-IDF v5.4.1-643-g8ad0d3d8f2-dirty 2nd stage bootloader
I (32) boot: compile time Dec 18 2025 15:45:14
W (32) boot: Unicore bootloader
I (35) boot: chip revision: v3.1
I (38) boot.esp32: SPI Speed : 40MHz
I (41) boot.esp32: SPI Mode : DIO
I (45) boot.esp32: SPI Flash Size : 16MB
I (49) boot: Enabling RNG early entropy source...
I (53) boot: Partition Table:
I (56) boot: ## Label Usage Type ST Offset Length
I (62) boot: 0 phy_init RF data 01 01 0000f000 00001000
I (69) boot: 1 otadata OTA data 01 00 00010000 00002000
I (75) boot: 2 nvs WiFi data 01 02 00012000 0000e000
I (82) boot: 3 at_customize unknown 40 00 00020000 000e0000
I (88) boot: 4 ota_0 OTA app 00 10 00100000 00200000
I (95) boot: 5 ota_1 OTA app 00 11 00300000 00200000
I (101) boot: End of partition table
I (104) esp_image: segment 0: paddr=00100020 vaddr=3f400020 size=36900h (223488) map

[18:16:01.462]收←◆I (188) esp_image: segment 1: paddr=00136928 vaddr=3ff80064 size=0001ch ( 28) load
I (189) esp_image: segment 2: paddr=0013694c vaddr=3ffbdb60 size=05eech ( 24300) load
I (201) esp_image: segment 3: paddr=0013c840 vaddr=40080000 size=037d8h ( 14296) load
I (207) esp_image: segment 4: paddr=00140020 vaddr=400d0020 size=143e1ch (1326620) map

[18:16:01.934]收←◆I (661) esp_image: segment 5: paddr=00283e44 vaddr=400837d8 size=17958h ( 96600) load

[18:16:01.971]收←◆I (698) esp_image: segment 6: paddr=0029b7a4 vaddr=400c0000 size=00064h ( 100) load
I (712) boot: Loaded app from partition at offset 0x100000
I (712) boot: Disabling RNG early entropy source...
I (722) cpu_start: Unicore app
D (722) cpu_start: Pro cpu up
I (722) cpu_start: Single core mode
D (723) clk: waiting for 32k oscillator to start up

[18:16:02.081]收←◆D (807) clk: waiting for 32k oscillator to start up

[18:16:02.160]收←◆W (887) clk: 32 kHz XTAL not found, switching to internal 150 kHz oscillator
D (894) clk: RTC_SLOW_CLK calibration value: 3033446
D (901) cpu_start: calling init function: 0x400d2c90 on core: 0
D (901) cpu_start: calling init function: 0x400d31a0 on core: 0
I (903) cpu_start: Pro cpu start user code
I (907) cpu_start: cpu freq: 240000000 Hz
D (911) cpu_start: calling init function: 0x400d2bd0 on core: 0
I (916) app_init: Application information:
I (920) app_init: Project name: esp-at
I (924) app_init: App version: v4.2.0.0-dev
I (928) app_init: Compile time: Dec 18 2025 15:45:11
I (933) app_init: ELF file SHA256: da9d9dea8...
I (938) app_init: ESP-IDF: v5.4.1-643-g8ad0d3d8f2-dirty
D (943) cpu_start: calling init function: 0x400d2ca4 on core: 0
I (949) efuse_init: Min chip rev: v0.0
I (953) efuse_init: Max chip rev: v3.99
I (957) efuse_init: Chip rev: v3.1
D (961) cpu_start: calling init function: 0x400d4854 on core: 0
D (966) memory_layout: Checking 12 reserved memory ranges:
D (972) memory_layout: Reserved memory range 0x3ff80000 - 0x3ff80080
D (978) memory_layout: Reserved memory range 0x3ff82000 - 0x3ff82000
D (984) memory_layout: Reserved memory range 0x3ffae000 - 0x3ffae6e0
D (990) memory_layout: Reserved memory range 0x3ffae6e0 - 0x3ffaff10
D (996) memory_layout: Reserved memory range 0x3ffb0000 - 0x3ffb6388
D (1002) memory_layout: Reserved memory range 0x3ffb8000 - 0x3ffb9a20
D (1008) memory_layout: Reserved memory range 0x3ffbdb28 - 0x3ffbdb5c
D (1014) memory_layout: Reserved memory range 0x3ffbdb60 - 0x3ffcdb70
D (1020) memory_layout: Reserved memory range 0x3ffe0000 - 0x3ffe0440
D (1027) memory_layout: Reserved memory range 0x40070000 - 0x40078000
D (1033) memory_layout: Reserved memory range 0x40080000 - 0x4009b130
D (1039) memory_layout: Reserved memory range 0x50001fe8 - 0x50002000
D (1045) memory_layout: Building list of available memory regions:
D (1051) memory_layout: Available memory region 0x3ffaff10 - 0x3ffb0000
D (1057) memory_layout: Available memory region 0x3ffb6388 - 0x3ffb8000
D (1064) memory_layout: Available memory region 0x3ffb9a20 - 0x3ffbdb28
D (1070) memory_layout: Available memory region 0x3ffcdb70 - 0x3ffce000
D (1076) memory_layout: Available memory region 0x3ffce000 - 0x3ffd0000
D (1083) memory_layout: Available memory region 0x3ffd0000 - 0x3ffd2000
D (1089) memory_layout: Available memory region 0x3ffd2000 - 0x3ffd4000
D (1095) memory_layout: Available memory region 0x3ffd4000 - 0x3ffd6000
D (1102) memory_layout: Available memory region 0x3ffd6000 - 0x3ffd8000
D (1108) memory_layout: Available memory region 0x3ffd8000 - 0x3ffda000
D (1114) memory_layout: Available memory region 0x3ffda000 - 0x3ffdc000
D (1121) memory_layout: Available memory region 0x3ffdc000 - 0x3ffde000
D (1127) memory_layout: Available memory region 0x3ffde000 - 0x3ffe0000
D (1133) memory_layout: Available memory region 0x3ffe0440 - 0x3ffe4000
D (1140) memory_layout: Available memory region 0x3ffe4000 - 0x3ffe8000
D (1146) memory_layout: Available memory region 0x3ffe8000 - 0x3fff0000
D (1152) memory_layout: Available memory region 0x3fff0000 - 0x3fff8000
D (1159) memory_layout: Available memory region 0x3fff8000 - 0x3fffc000
D (1165) memory_layout: Available memory region 0x3fffc000 - 0x40000000
D (1171) memory_layout: Available memory region 0x40078000 - 0x40080000
D (1178) memory_layout: Available memory region 0x4009b130 - 0x4009c000
D (1184) memory_layout: Available memory region 0x4009c000 - 0x4009e000
D (1190) memory_layout: Available memory region 0x4009e000 - 0x400a0000
D (1197) memory_layout: Available memory region 0x3ff80080 - 0x3ff82000
I (1203) heap_init: Initializing. RAM available for dynamic allocation:
D (1210) heap_init: New heap initialised at 0x3ffaff10
I (1214) heap_init: At 3FFAFF10 len 000000F0 (0 KiB): DRAM
D (1219) heap_init: New heap initialised at 0x3ffb6388
I (1224) heap_init: At 3FFB6388 len 00001C78 (7 KiB): DRAM
D (1229) heap_init: New heap initialised at 0x3ffb9a20
I (1234) heap_init: At 3FFB9A20 len 00004108 (16 KiB): DRAM
D (1240) heap_init: New heap initialised at 0x3ffcdb70
I (1244) heap_init: At 3FFCDB70 len 00012490 (73 KiB): DRAM
I (1250) heap_init: At 3FFE0440 len 0001FBC0 (126 KiB): D/IRAM
D (1255) heap_init: New heap initialised at 0x40078000
I (1260) heap_init: At 40078000 len 00008000 (32 KiB): IRAM
D (1266) heap_init: New heap initialised at 0x4009b130
I (1270) heap_init: At 4009B130 len 00004ED0 (19 KiB): IRAM
D (1276) heap_init: New heap initialised at 0x3ff80080
I (1281) heap_init: At 3FF80080 len 00001F80 (7 KiB): RTCRAM
D (1286) cpu_start: calling init function: 0x400d8c14 on core: 0
D (1292) cpu_start: calling init function: 0x400d84e0 on core: 0
D (1298) cpu_start: calling init function: 0x400d31e4 on core: 0
D (1303) intr_alloc: Connected src 46 to int 1 (cpu 0)
D (1308) cpu_start: calling init function: 0x400d31f0 on core: 0
D (1314) cpu_start: calling init function: 0x400d9794 on core: 0
D (1320) cpu_start: calling init function: 0x400db07c on core: 0
D (1325) cpu_start: calling init function: 0x400d9a84 on core: 0
D (1331) cpu_start: calling init function: 0x400d855c on core: 0
D (1337) cpu_start: calling init function: 0x400d31fc on core: 0
D (1342) spi_flash: trying chip: issi
D (1346) spi_flash: trying chip: gd
D (1349) spi_flash: trying chip: mxic
D (1352) spi_flash: trying chip: winbond
D (1356) spi_flash: trying chip: generic
I (1360) spi_flash: detected chip: generic
I (1363) spi_flash: flash io: dio
D (1367) cpu_start: calling init function: 0x400d2d30 on core: 0
D (1372) cpu_start: calling init function: 0x401d90ec
D (1377) cpu_start: calling init function: 0x401d8010
D (1382) cpu_start: calling init function: 0x40210d94
D (1387) cpu_start: calling init function: 0x4014a8a4
W (1391) ADC: legacy driver is deprecated, please migrate to esp_adc/adc_oneshot.h
D (1399) cpu_start: calling init function: 0x4014a85c
W (1404) i2s(legacy): legacy i2s driver is deprecated, please migrate to use driver/i2s_std.h, driver/i2s_pdm.h or driver/i2s_tdm.h
D (1415) cpu_start: calling init function: 0x401497dc
D (1420) cpu_start: calling init function: 0x40092a10
D (1425) cpu_start: calling init function: 0x400d3660
D (1430) cpu_start: calling init function: 0x402102c4 on core: 0
D (1436) intr_alloc: Connected src 17 to int 2 (cpu 0)
D (1440) cpu_start: calling init function: 0x40200c34 on core: 0
D (1446) cpu_start: calling init function: 0x400d76b0 on core: 0
I (1451) sleep_gpio: Configure to isolate all GPIO pins in sleep state
I (1458) sleep_gpio: Enable automatic switching of GPIO sleep configuration
D (1464) cpu_start: calling init function: 0x400d3224 on core: 0
D (1481) cpu_start: calling init function: 0x400d3230 on core: 0
I (1482) coexist: coex firmware version: 88dafd1
D (1482) cpu_start: calling init function: 0x400d3248 on core: 0
D (1488) intr_alloc: Connected src 24 to int 3 (cpu 0)
D (1493) app_start: Starting scheduler on CPU0
I (1497) main_task: Started on CPU0
D (1500) heap_init: New heap initialised at 0x3ffe0440
D (1505) intr_alloc: Connected src 16 to int 5 (cpu 0)
I (1509) main_task: Calling app_main()
I (1513) at-workaround: no external 32k oscillator, disable it now.
D (1519) at-workaround: at main pre-process done
D (1541) esp_netif_lwip: LwIP stack has been initialized
D (1541) esp_netif_lwip: esp-netif has been successfully initialized
D (1542) event: running task for loop 0x3ffbd5cc
D (1546) event: created task for loop 0x3ffbd5cc
D (1550) event: created event loop 0x3ffbd5cc
I (1586) at-init: at param mode: 1
D (1586) esp_netif_lwip: check: remote, if=0x3ffba9b0 fn=0x40167820
D (1586) esp_netif_objects: esp_netif_add_to_list_unsafe netif added successfully (total netifs: 1)
D (1593) esp_netif_lwip: call api in lwip: ret=0x0, give sem
D (1599) esp_netif_lwip: check: remote, if=0x3ffba9b0 fn=0x40167820
D (1604) esp_netif_objects: esp_netif_add_to_list_unsafe netif added successfully (total netifs: 2)
D (1613) esp_netif_lwip: call api in lwip: ret=0x0, give sem
D (1619) nvs: nvs_open_from_partition misc 1
I (1624) wifi:wifi driver task: 3ffd1c68, prio:23, stack:6144, core=0
D (1629) efuse: BLK0 REG2 [8-15], len=8 bits
D (1632) efuse: BLK0 REG2 [0-7], len=8 bits
D (1636) efuse: BLK0 REG1 [24-31], len=8 bits
D (1640) efuse: BLK0 REG1 [16-23], len=8 bits
D (1644) efuse: BLK0 REG1 [8-15], len=8 bits
D (1648) efuse: BLK0 REG1 [0-7], len=8 bits
D (1652) efuse: BLK0 REG2 [16-23], len=8 bits
D (1657) nvs: nvs_open_from_partition nvs.net80211 1
D (1661) nvs: nvs_get opmode 1
D (1664) nvs: nvs_get_str_or_blob sta.ssid
D (1667) nvs: nvs_get sta.authmode 1
D (1671) nvs: nvs_get_str_or_blob sta.pswd
D (1674) nvs: nvs_get_str_or_blob sta.pmk
D (1678) nvs: nvs_get sta.chan 1
D (1681) nvs: nvs_get auto.conn 1
D (1684) nvs: nvs_get bssid.set 1
D (1687) nvs: nvs_get_str_or_blob sta.bssid
D (1691) nvs: nvs_get sta.lis_intval 2
D (1694) nvs: nvs_get sta.phym 1
D (1697) nvs: nvs_get sta.phybw 1
D (1700) nvs: nvs_get_str_or_blob sta.apsw
D (1704) nvs: nvs_get_str_or_blob sta.apinfo
D (1708) nvs: nvs_get sta.scan_method 1
D (1712) nvs: nvs_get sta.sort_method 1
D (1715) nvs: nvs_get sta.minrssi 1
D (1718) nvs: nvs_get sta.minauth 1
D (1722) nvs: nvs_get sta.pmf_e 1
D (1725) nvs: nvs_get sta.pmf_r 1
D (1728) nvs: nvs_get sta.btm_e 1
D (1731) nvs: nvs_get sta.rrm_e 1
D (1734) nvs: nvs_get sta.mbo_e 1
D (1737) nvs: nvs_get_str_or_blob ap.ssid
D (1740) nvs: nvs_get_str_or_blob ap.passwd
D (1744) nvs: nvs_get_str_or_blob ap.pmk
D (1748) nvs: nvs_get ap.chan 1
D (1751) nvs: nvs_get ap.authmode 1
D (1754) nvs: nvs_get ap.hidden 1
D (1757) nvs: nvs_get ap.max.conn 1
D (1760) nvs: nvs_get bcn.interval 2
D (1763) nvs: nvs_get ap.phym 1
D (1766) nvs: nvs_get ap.phybw 1
D (1769) nvs: nvs_get ap.sndchan 1
D (1772) nvs: nvs_get ap.pmf_e 1
D (1775) nvs: nvs_get ap.pmf_r 1
D (1778) nvs: nvs_get ap.p_cipher 1
D (1781) nvs: nvs_get lorate 1
D (1784) nvs: nvs_get_str_or_blob country
D (1788) nvs: nvs_get ap.ftm_r 1
D (1791) nvs: nvs_get sta.ft 1
D (1793) nvs: nvs_get sta.owe 1
D (1796) nvs: nvs_get sta.trans_d 1
D (1799) nvs: nvs_get sta.sae_h2e 1
D (1803) nvs: nvs_get sta.sae_pk_mode 1
D (1806) nvs: nvs_get sta.bss_retry 1
D (1810) nvs: nvs_get_str_or_blob sta.owe_data
D (1814) nvs: nvs_get sta.he_dcm 1
D (1817) nvs: nvs_get sta.he_dcm_c_tx 1
D (1820) nvs: nvs_get sta.he_dcm_c_rx 1
D (1824) nvs: nvs_get sta.he_mcs9_d 1
D (1827) nvs: nvs_get sta.he_su_b_d 1
D (1831) nvs: nvs_get sta.he_su_b_f_d 1
D (1834) nvs: nvs_get sta.he_mu_b_f_d 1
D (1838) nvs: nvs_get sta.he_cqi_f_d 1
D (1841) nvs: nvs_get_str_or_blob sta.sae_h2e_id
D (1845) nvs: nvs_get ap.sae_h2e 1
D (1849) nvs: nvs_get_str_or_blob ap.pmk_info
D (1853) nvs: nvs_get nan.phym 1
D (1856) nvs: nvs_get sta.pwr_reset 1
D (1859) nvs: nvs_get band_mode 1
D (1862) nvs: nvs_get sta.phym5g 1
D (1865) nvs: nvs_get ap.phym5g 1
D (1868) nvs: nvs_get sta.phybw5g 1
D (1871) nvs: nvs_get ap.phybw5g 1
D (1874) nvs: nvs_get ap.sndchan5g 1
D (1878) nvs: nvs_get ap.chan5g 1
D (1881) nvs: nvs_get ap.chanisset 1
D (1884) nvs: nvs_get ap.chan5gisset 1
D (1887) nvs: nvs_get sta.lowrate 1
D (1891) nvs: nvs_get ap.lowrate 1
D (1894) nvs: nvs_get sta.rssi_5g_adj 1
D (1897) nvs: nvs_get ap.csa_count 1
D (1900) nvs: nvs_get ap.dtim_period 1
D (1904) nvs: nvs_get ap.trans_d 1
D (1907) nvs: nvs_set ap.sndchan 1 1
I (1911) wifi:wifi firmware version: 71d995a31
I (1914) wifi:wifi certification version: v7.0
I (1919) wifi:config NVS flash: enabled
I (1922) wifi:config nano formatting: enabled
I (1926) wifi:Init data frame dynamic rx buffer num: 32
I (1931) wifi:Init static rx mgmt buffer num: 5
I (1935) wifi:Init management short buffer num: 32
I (1940) wifi:Init dynamic tx buffer num: 32
I (1944) wifi:Init static rx buffer size: 1600
I (1948) wifi:Init static rx buffer num: 10
I (1952) wifi:Init dynamic rx buffer num: 32
D (1956) wifi:Reset scan defaults in ms : min,max,passive,chan_dwell :(0,120,360,30)
I (1964) wifi_init: rx ba win: 6
I (1966) wifi_init: accept mbox: 6
I (1969) wifi_init: tcpip mbox: 32
I (1972) wifi_init: udp mbox: 6
I (1975) wifi_init: tcp mbox: 6
I (1978) wifi_init: tcp tx win: 5760
I (1981) wifi_init: tcp rx win: 5760
I (1985) wifi_init: tcp mss: 1440
I (1988) wifi_init: WiFi SLP IRAM OP enabled
D (1992) adc_share_hw_ctrl: Wi-Fi takes adc2 lock.
I (1996) phy_init: phy_version 4860,6b7a6e5,Feb 6 2025,14:47:07
D (2002) phy_init: loading PHY init data from application binary
D (2007) nvs: nvs_open_from_partition phy 0
D (2012) nvs: nvs_get cal_version 4
D (2015) nvs: nvs_get_str_or_blob cal_mac
D (2019) efuse: BLK0 REG2 [8-15], len=8 bits
D (2022) efuse: BLK0 REG2 [0-7], len=8 bits
D (2026) efuse: BLK0 REG1 [24-31], len=8 bits
D (2030) efuse: BLK0 REG1 [16-23], len=8 bits
D (2034) efuse: BLK0 REG1 [8-15], len=8 bits
D (2038) efuse: BLK0 REG1 [0-7], len=8 bits
D (2042) efuse: BLK0 REG2 [16-23], len=8 bits
D (2046) nvs: nvs_get_str_or_blob cal_data
D (2051) nvs: nvs_close 3
D (2052) efuse: BLK0 REG2 [8-15], len=8 bits
D (2056) efuse: BLK0 REG2 [0-7], len=8 bits
D (2060) efuse: BLK0 REG1 [24-31], len=8 bits
D (2064) efuse: BLK0 REG1 [16-23], len=8 bits
D (2068) efuse: BLK0 REG1 [8-15], len=8 bits
D (2072) efuse: BLK0 REG1 [0-7], len=8 bits
D (2076) efuse: BLK0 REG2 [16-23], len=8 bits

[18:16:03.413]收←◆I (2139) phy_init: Saving new calibration data due to checksum failure or outdated calibration data, mode(0)
D (2139) nvs: nvs_open_from_partition phy 1
D (2142) nvs: nvs_set_blob cal_data 1904
D (2157) efuse: BLK0 REG2 [8-15], len=8 bits
D (2158) efuse: BLK0 REG2 [0-7], len=8 bits
D (2158) efuse: BLK0 REG1 [24-31], len=8 bits
D (2159) efuse: BLK0 REG1 [16-23], len=8 bits
D (2163) efuse: BLK0 REG1 [8-15], len=8 bits
D (2167) efuse: BLK0 REG1 [0-7], len=8 bits
D (2171) efuse: BLK0 REG2 [16-23], len=8 bits
D (2175) nvs: nvs_set_blob cal_mac 6
D (2179) nvs: nvs_set cal_version 4 4860
D (2182) nvs: nvs_close 4
D (2186) wifi:filter: set rx policy=0
I (2189) wifi:mode : softAP (ec:e3:34:58:27:fd)
D (2192) wifi:filter: set rx policy=9
I (2196) wifi:Total power save buffer number: 16
I (2200) wifi:Init max length of beacon: 752/752
I (2205) wifi:Init max length of beacon: 752/752
D (2209) event: no handlers have been registered for event WIFI_EVENT:43 posted to loop 0x3ffbd5cc
D (2217) event: running post WIFI_EVENT:12 with handler 0x4017c904 and context 0x3ffcf830 on loop 0x3ffbd5cc
D (2226) wifi_init_default: wifi_start esp-netif:0x3ffcf8c4 event-id12
D (2233) wifi_init_default: WIFI mac address: ec e3 34 58 27 fd
D (2239) esp_netif_lwip: check: remote, if=0x3ffcf8c4 fn=0x40166b7c
D (2244) esp_netif_lwip: call api in lwip: ret=0x0, give sem
D (2250) esp_netif_handlers: esp_netif action has started with netif0x3ffcf8c4 from event_id=12
D (2258) esp_netif_lwip: check: remote, if=0x3ffcf8c4 fn=0x40167a48
D (2264) esp_netif_lwip: esp_netif_start_api 0x3ffcf8c4
D (2269) esp_netif_lwip: esp_netif_internal_dhcpc_cb lwip-netif:0x3ffcf950
D (2275) esp_netif_lwip: if0x3ffcf8c4 ip unchanged
D (2280) esp_netif_lwip: esp_netif_get_hostname esp_netif:0x3ffcf8c4
D (2286) esp_netif_lwip: esp_netif_start_api Setting the lwip netif0x3ffcf950 UP
I (2293) esp_netif_lwip: DHCP server started on interface WIFI_AP_DEF with IP: 192.168.4.1
D (2301) esp_netif_lwip: check: local, if=0x3ffcf8c4 fn=0x40168240
D (2307) esp_netif_lwip: esp_netif_update_default_netif_lwip 0x3ffcf8c4
D (2314) esp_netif_lwip: call api in lwip: ret=0x0, give sem
D (2320) intr_alloc: Connected src 10 to int 9 (cpu 0)
D (2325) nvs: nvs_open_from_partition factory_param 0
D (2328) nvs: nvs_get_str_or_blob module_name
D (2333) nvs: nvs_close 5
I (2335) at-init: module_name: ESP32-SDIO
D (2338) nvs: nvs_open_from_partition factory_param 0
D (2343) nvs: nvs_get max_tx_power 1
I (2347) at-init: max tx power=78, ret=0
D (2350) nvs: nvs_get start_channel 1
D (2353) nvs: nvs_get channel_num 1
D (2356) nvs: nvs_get_str_or_blob country_code
I (2361) wifi:(2.4G)set country: cc=CN\0 schan=1 nchan=13 policy=1

D (2367) nvs: nvs_close 6
D (2369) at-init: at wifi init done
I (2372) at-init: v4.2.0.0-dev (unknown)
I (2376) at-init: AT version:4.2.0.0-dev(3258eee - ESP32 - Nov 17 2025 09:58:48)
SDK version:v5.4.1-643-g8ad0d3d8f2-dirty
compile time(aa9963e):Dec 18 2025 15:45:36
Bin version:v4.2.0.0-dev(ESP32-SDIO)

E (2394) at-sdio: invalid data:0 or len:-1
D (2398) at-init: at module init done
D (2401) nvs: nvs_open_from_partition factory_param 0
D (2406) nvs: nvs_get sys_store 1
D (2409) nvs: nvs_open_from_partition NVM_012 0
D (2413) at-cmd-register: esp_at_base_cmd_regist success
I (2419) wifi:mode : sta (ec:e3:34:58:27:fc) + softAP (ec:e3:34:58:27:fd)
I (2425) wifi:enable tsf
D (2427) wifi:filter: set rx policy=1
D (2430) wifi:connect status 0 -> 0
D (2434) event: running post WIFI_EVENT:2 with handler 0x4017c91c and context 0x3ffcf770 on loop 0x3ffbd5cc
D (2443) wifi_init_default: wifi_start esp-netif:0x3ffcf558 event-id2
D (2449) wifi_init_default: WIFI mac address: ec e3 34 58 27 fc
D (2455) esp_netif_lwip: check: remote, if=0x3ffcf558 fn=0x40166b7c
D (2460) esp_netif_lwip: call api in lwip: ret=0x0, give sem
D (2466) esp_netif_handlers: esp_netif action has started with netif0x3ffcf558 from event_id=2
D (2474) esp_netif_lwip: check: remote, if=0x3ffcf558 fn=0x40167a48
D (2480) esp_netif_lwip: esp_netif_start_api 0x3ffcf558
D (2485) esp_netif_lwip: esp_netif_get_hostname esp_netif:0x3ffcf558
D (2491) esp_netif_lwip: call api in lwip: ret=0x0, give sem
D (2496) esp_netif_lwip: check: remote, if=0x3ffba950 fn=0x40166b68
D (2502) esp_netif_lwip: call api in lwip: ret=0x0, give sem
D (2508) esp_netif_lwip: check: remote, if=0x3ffba950 fn=0x40166b68
D (2513) esp_netif_lwip: call api in lwip: ret=0x0, give sem
D (2519) nvs: nvs_open_from_partition NVM_004 0
D (2523) nvs: nvs_open_from_partition NVM_003 0
D (2527) nvs: nvs_open_from_partition NVM_017 0
D (2532) nvs: nvs_open_from_partition NVM_022 1
D (2536) nvs: nvs_get wac 1
D (2539) nvs: nvs_close 8
D (2541) nvs: nvs_open_from_partition NVM_024 0
D (2545) nvs: nvs_open_from_partition NVM_013 0
D (2549) esp_netif_lwip: check: remote, if=0x3ffba930 fn=0x40166b68
D (2555) esp_netif_lwip: call api in lwip: ret=0x0, give sem
D (2560) esp_netif_lwip: check: remote, if=0x3ffcf558 fn=0x401671a8
D (2566) esp_netif_lwip: esp_netif_dhcpc_stop_api esp_netif:0x3ffcf558
D (2572) esp_netif_lwip: dhcp client stop successfully
D (2577) esp_netif_lwip: call api in lwip: ret=0x0, give sem
D (2583) esp_netif_lwip: check: remote, if=0x3ffba930 fn=0x40166b68
D (2589) esp_netif_lwip: call api in lwip: ret=0x0, give sem
D (2594) esp_netif_lwip: check: remote, if=0x3ffcf8c4 fn=0x40167100
D (2600) esp_netif_lwip: esp_netif_dhcps_stop_api esp_netif:0x3ffcf8c4
D (2606) esp_netif_lwip: dhcp server stop successfully
D (2611) esp_netif_lwip: call api in lwip: ret=0x0, give sem
D (2616) nvs: nvs_open_from_partition NVM_002 0
D (2621) nvs: nvs_open_from_partition NVM_021 0
D (2625) nvs: nvs_open_from_partition NVM_001 0
D (2629) nvs: nvs_open_from_partition NVM_007 0
D (2633) nvs: nvs_open_from_partition NVM_006 0
D (2637) esp_netif_lwip: check: remote, if=0x3ffba930 fn=0x40166b68
D (2643) esp_netif_lwip: call api in lwip: ret=0x0, give sem
D (2649) esp_netif_lwip: check: remote, if=0x3ffcf558 fn=0x40167298
D (2655) esp_netif_lwip: esp_netif_dhcpc_start_api esp_netif:0x3ffcf558
D (2661) esp_netif_lwip: dhcp client re init
D (2665) esp_netif_lwip: call api in lwip: ret=0x0, give sem
D (2670) esp_netif_lwip: check: remote, if=0x3ffba930 fn=0x40166b68
D (2676) esp_netif_lwip: call api in lwip: ret=0x0, give sem
D (2682) esp_netif_lwip: check: remote, if=0x3ffcf8c4 fn=0x40166f78
D (2688) esp_netif_lwip: esp_netif_dhcps_start_api esp_netif:0x3ffcf8c4
D (2694) esp_netif_lwip: DHCP server started successfully
D (2699) esp_netif_lwip: call api in lwip: ret=0x0, give sem
D (2705) wifi:connect status 0 -> 0
D (2707) wifi:Start wifi disconnect
D (2711) wifi:connect status 0 -> 0
D (2714) wifi:filter: set rx policy=8
D (2717) wifi:filter: set rx policy=2
D (2721) wifi:clear scan ap list
D (2724) wifi:clear blacklist
D (2726) wifi:clear rc list
I (2729) wifi:mode : softAP (ec:e3:34:58:27:fd)
D (2734) event: running post WIFI_EVENT:3 with handler 0x4017c7e8 and context 0x3ffcf7a0 on loop 0x3ffbd5cc
D (2742) esp_netif_handlers: esp_netif action stopped with netif0x3ffcf558 from event_id=3
D (2750) esp_netif_lwip: check: remote, if=0x3ffcf558 fn=0x40167c00
D (2757) esp_netif_lwip: call api in lwip: ret=0x5002, give sem
D (2763) at-cmd-register: esp_at_wifi_cmd_regist success
D (2767) at-cmd-register: esp_at_smartconfig_cmd_regist success
D (2772) at-cmd-register: esp_at_wps_cmd_regist success
D (2777) at-cmd-register: esp_at_mdns_cmd_regist success
D (2783) nvs: nvs_open_from_partition NVM_020 0
D (2787) nvs: nvs_open_from_partition NVM_020 0
D (2791) nvs: nvs_open_from_partition NVM_020 0
D (2795) nvs: nvs_open_from_partition NVM_020 0
D (2799) nvs: nvs_open_from_partition NVM_020 0
D (2806) esp_netif_lwip: check: remote, if=0x3ffba920 fn=0x40166b68
D (2809) esp_netif_lwip: call api in lwip: ret=0x0, give sem
D (2815) nvs: nvs_open_from_partition NVM_008 1
D (2819) nvs: nvs_get dns_ser0 4
D (2822) nvs: nvs_get dns_ser1 4
D (2825) nvs: nvs_get dns_ser2 4
D (2828) nvs: nvs_get_str_or_blob dns_svr0
D (2832) nvs: nvs_close 9
D (2834) esp_netif_lwip: check: remote, if=0x3ffcf558 fn=0x40167484
D (2840) esp_netif_lwip: esp_netif_set_dns_info: if=0x3ffcf558 type=0 dns=dede43d0
D (2847) esp_netif_lwip: call api in lwip: ret=0x0, give sem
D (2853) esp_netif_lwip: check: remote, if=0x3ffcf558 fn=0x40167484
D (2858) esp_netif_lwip: esp_netif_set_dns_info: if=0x3ffcf558 type=1 dns=72727272
D (2866) esp_netif_lwip: call api in lwip: ret=0x0, give sem
D (2871) esp_netif_lwip: check: remote, if=0x3ffcf558 fn=0x40167484
D (2877) esp_netif_lwip: esp_netif_set_dns_info: if=0x3ffcf558 type=2 dns=8080808
D (2884) esp_netif_lwip: call api in lwip: ret=0x0, give sem
D (2890) nvs: nvs_open_from_partition NVM_009 1
D (2894) nvs: nvs_get maxlink 1
D (2897) nvs: nvs_open_from_partition NVM_009 0
D (2901) nvs: nvs_get auth0 1
D (2903) nvs: nvs_open_from_partition NVM_009 0
D (2908) nvs: nvs_get auth1 1
D (2910) nvs: nvs_open_from_partition NVM_009 0
D (2915) nvs: nvs_get auth2 1
D (2917) nvs: nvs_open_from_partition NVM_009 0
D (2922) nvs: nvs_get auth3 1
D (2924) nvs: nvs_open_from_partition NVM_009 0
D (2929) nvs: nvs_get auth4 1
D (2931) nvs: nvs_open_from_partition NVM_018 0
D (2935) nvs: nvs_open_from_partition NVM_005 1
D (2940) nvs: nvs_get enable 1
D (2942) nvs: nvs_close 16
D (2945) at-cmd-register: esp_at_net_cmd_regist success
D (2950) at-cmd-register: esp_at_ping_cmd_regist success
D (2955) at-cmd-register: esp_at_mqtt_cmd_regist success
D (2960) at-cmd-register: esp_at_http_cmd_regist success
D (2965) nvs: nvs_open_from_partition NVM_005 1
D (2969) nvs: nvs_get enable 1
D (2972) nvs: nvs_close 17
D (2974) nvs: nvs_open_from_partition NVM_015 0
D (2978) nvs: nvs_get ble_name_en 1
D (2982) nvs: nvs_get_str_or_blob name
D (2985) nvs: nvs_get adv_param_en 1
D (2988) nvs: nvs_get adv_int_min 4
D (2991) nvs: nvs_get adv_int_max 4
D (2995) nvs: nvs_get adv_type 1
D (2998) nvs: nvs_get own_addr_type 1
D (3001) nvs: nvs_get channel_map 1
D (3004) nvs: nvs_get adv_filter 1
D (3007) nvs: nvs_get peer_addr_type 1
D (3011) nvs: nvs_get_str_or_blob peer_addr
D (3015) nvs: nvs_get adv_data_en 1
D (3018) nvs: nvs_get_str_or_blob adv_data
D (3021) nvs: nvs_get adv_ex_en 1
D (3025) nvs: nvs_get_str_or_blob uuid
D (3029) nvs: nvs_get_str_or_blob manf_data
D (3032) nvs: nvs_get inc_power 1
D (3035) nvs: nvs_get scan_rsp_en 1
D (3038) nvs: nvs_get_str_or_blob scan_rsp_data
D (3042) nvs: nvs_get mac_en 1
D (3045) nvs: nvs_get_str_or_blob ble_mac
D (3049) nvs: nvs_get_str_or_blob remote_mac
D (3053) nvs: nvs_get scan_param_en 1
D (3056) nvs: nvs_get scan_type 1
D (3059) nvs: nvs_get scan_filter 1
D (3062) nvs: nvs_get scan_interval 4
D (3066) nvs: nvs_get scan_interval 1
D (3069) nvs: nvs_get scan_window 4
D (3072) nvs: nvs_get scan_window 1
D (3075) nvs: nvs_close 18
D (3078) at-cmd-register: esp_at_ble_cmd_regist success
D (3083) nvs: nvs_open_from_partition NVM_023 0
D (3087) at-cmd-register: esp_at_ble_hid_cmd_regist success
D (3092) nvs: nvs_open_from_partition NVM_019 0
D (3096) at-cmd-register: esp_at_blufi_cmd_regist success
D (3101) at-cmd-register: esp_at_fact_cmd_regist success
D (3107) at-cmd-register: esp_at_user_cmd_regist success
D (3112) BTDM_INIT: Release DRAM [0x3ffb2730] - [0x3ffb6388]
I (3119) intf-tx: 0x3f403940 0d 0a 72 65 61 64 79 0d 0a |..ready..|
D (3125) SDIO_HAL: restart new send: 0x3ffd9070->0x3ffd9070, pkt_len: 9

[18:16:35.276]收←◆D (34003) at-init: esp_at_init done
I (34003) main_task: Returned from app_main()

[Misanic]

The reason why I suggest you use 1-bit is that 4-bit is more sensitive to timing. Especially when using DuPont cables for connection, even very short wires can easily cause communication errors. And often, just like you mentioned, the "ready" signal may be received, but the subsequent data transmission may be abnormal.

Thank you very much for your further suggestion!
I made a conversion board for the esp32. The esp32 postage module was directly soldered onto the conversion board, and the conversion board was inserted into the SD card slot of my embedded device for communication. This way, communication-related errors were minimized as much as possible.
I once conducted tests using the SDIO 1-bit mode, but found that my embedded device couldn't receive any interrupts in the SDIO 1-bit mode. Therefore, I believe I may not be able to attempt to communicate using the 1-bit mode. But I will try again to see if the SDIO 1-bit mode is usable. Thank you!

[ustccw]

restart new send: 0x3ffd9070->0x3ffd9070, pkt_len: 9

From the logs, it seems that AT sends "ready" string to MCU (intf-tx: 0x3f403940 0d 0a 72 65 61 64 79 0d 0a |..ready..|), and doesn't receive any AT commands from MCU.

I think you can double check your SDIO related software and hardware.

[Misanic]

restart new send: 0x3ffd9070->0x3ffd9070, pkt_len: 9

From the logs, it seems that AT sends "ready" string to MCU (intf-tx: 0x3f403940 0d 0a 72 65 61 64 79 0d 0a |..ready..|), and doesn't receive any AT commands from MCU.

I think you can double check your SDIO related software and hardware.

Thank you for your suggestion! After numerous comparisons and attempts, I finally identified the problem. When I set the SDIO buffer number to 40 (the default is 10), my device could communicate normally with the esp32. I don't know why this is the case. This is so strange. I never thought it was this that was the problem.

[ustccw]

Thank you for the feedback, and for taking the time to investigate this further.

Just to help us better understand your setup, when you mention the "SDIO buffer number", is this configuration applied on the MCU (host) side or on the ESP32 side?

It's good to know that increasing this value makes the communication work as expected. This information is very helpful for us to understand similar cases in the future.

[Misanic]

Thank you for the feedback, and for taking the time to investigate this further.

Just to help us better understand your setup, when you mention the "SDIO buffer number", is this configuration applied on the MCU (host) side or on the ESP32 side?

It's good to know that increasing this value makes the communication work as expected. This information is very helpful for us to understand similar cases in the future.

The "SDIO buffer number" is applied on ESP32 side. In menuconfig->Component config->AT->communicate method for AT command (AT through SDIO)->AT SDIO settings->SDIO buffer number

[ustccw]

@Misanic Thank you for the feedback regarding the SDIO buffer number.

We have tried testing with both 10 and 40 "SDIO buffer number" on our side, and in our setup, both configurations seem to work well. It is indeed quite unusual that setting it to 10 causes communication issues on your device, especially considering that each buffer has 512 bytes - more than enough to carry AT commands. In theory, using 10 or 40 buffers should have the same effect.

To ensure the reliability of your product, we would suggest investigating this issue further. For example:

1. Using a logic analyzer to verify whether the MCU is actually sending the AT commands when the buffer number is set to 10.
2. If necessary, consider contacting our technical support team and sending the device to us so we can perform further diagnostics.

Understanding this behavior thoroughly will help prevent potential issues in production and ensure stable operation.