ESP32 Forum

Hi All,
Using Wroom32 devkitc with default configuration(menuconfigs) for esp-at firmware. Using UART1 for at interface with default GPIO pins(Rx-16,Tx-17). Seems while flashed with at firmware , hangs? with following output.

E (1944) phy_init: PHY data partition validated
I (1975) phy: phy_version: 329, Feb 22 2017, 15:58:07, 0, 0
I (1976) wifi: Init ampdu: 1
I (1976) wifi: mode : softAP (24:0a:c4:xx:xx:xx)
I (1980) wifi: Init ampdu: 1
I (1980) wifi: mode : sta (24:0a:c4:xx:xx:xx) + softAP (24:0a:c4:xx:xx:xx)
I (1987) wifi: mode : softAP (24:0a:c4:xx:xx:xx)

Also , whilst the uart-usb converter is plugged to PC, with specific to Tx-17 , fails to boot with repeated warnings

rst:0x10 (RTCWDT_RTC_RESET),boot:0x13 (SPI_FAST_FLASH_BOOT)
flash read err, 1000
Falling back to built-in command interpreter.
OK
>ets Jun 8 2016 00:22:57

Is there something missing or extra setting required?

Noting , AT would be only interface to communicate through host through UART1 for wifi, is there alternative not using AT and setup wifi ?

Any help greatly appreciated..

Update about issue :
Repeated warnings when converter is plugged in to PC is now resolved by changing interface seems.
But main issue still persists (hang?) .

Also , it seems can't use updated esp-idf in the esp-at firmware since it is tied to particular checkin.

Could it be the issue?

If esp-idf is taken from latest (how?) could it fix the issue as if I update only that , esp-at library itself will not be built.

You need to use the exact submodule version of ESP-IDF specified in the AT repository. It won't work otherwise.

Thanks ESP_igrr,
I reckon the same ,
Are there any known issues with at firmware(latest) presently or if you have the uart0 output of the same (working)?

As far as i can see from the log you have posted, UART0 output is working. By default, AT communication happens on UART1. You can go into 'make menuconfig' and configure UART peripheral used for AT commands, and the pin numbers for TX and RX.

Thanks ESP_igrr,
I tried with redirecting AT output to UART0 , but since both redirect to same COM , AT commands were not working after seeing Ready. Hence needed seperate COM with UART1 and GPIO RX16 and TX17 as output , but still then not seeing any activity on UART1.

There is similar post on the hang issue:
viewtopic.php?f=13&t=1628

but seems no concrete solution at the end..

This seems to be fixed by latest firmware with AT routed on UART0 (same as debug) and sending CR+LF on enter of the command.
Thanks.