esp32-at app hangs after boot

[johnabel]

I cloned the latest release of esp32-at, compiled without any change and flashed to the ESP-WROOM32, it boots.... but hangs with this as last text on the terminal:
I (6233) wifi: wifi power manager task: 0x3ffc83b8 prio: 21 stack: 2560
I (6240) wifi: wifi timer task: 3ffc9438, prio:22, stack:3584
E (6245) phy_init: PHY data partition validated
I (6269) phy: phy_version: 329, Feb 22 2017, 15:58:07, 0, 0
I (6270) wifi: Init ampdu: 1
I (6270) wifi: mode : softAP (30:ae:a4:02:92:9d)
I (6274) wifi: Init ampdu: 1
I (6275) wifi: mode : sta (30:ae:a4:02:92:9c) + softAP (30:ae:a4:02:92:9d)
I (6281) wifi: mode : softAP (30:ae:a4:02:92:9d)

I tried a number of times with the same result. I have nothing extra attached to any pin, I'm using a DevKitC just connected with a USB cable to a PC. Any clues about what could be.

[WiFive]

You may need to reconfigure serial port to use uart 0 via menuconfig if you are trying to use at commands over USB port.

[johnabel]

After boot there is that text (and more) on the terminal, I believe the micro is using that uart and baud rate.
Also, menuconfig only shows me one uart to choose.
I tried different releases of IDF and got a 'Meditation Guru's Panic' and continuous reboot.

[WiFive]

No I mean the port the at interface uses

https://github.com/espressif/esp32-at/b ... faults#L44

[johnabel]

menuconfig doesn't allow me to choose another uart.
Do you mean changing the sdkconfig.defaults file?

[WiFive]

I think that's not a real option, format error?

Try changing port number and/or pins below that

[johnabel]

I prefer a more analytical approach.
From the DevKitC schematics the CD2102 has its RXD-TXD pins connected to TXD0-RXD0 in the ESP-WROOM32 module (pins 35 and 34, respectively). According to the module pinout, these are related to UART0 in the chip.
Looking at the module schematics, those pins are connected to GPIO16 and GPIO14 in the chip, that matches with the default selection in menuconfig (see pic attached).
The only mismatch I see is there is UART1 in the menuconfig then it uses UART0, but anyway I'm getting an output through whatever UART uses that is connected to the USB. My problem is that before it hang at the beginning and now, after changing the IDF, it is rebooting.

[WiFive]

UART0 is gpio 1 & 3.

Yes you are getting debug/stdout output but not at interface.

You may also need to build against a specific commit of esp-idf

[johnabel]

I think I'm having an issue already reported. The github repository for the esp-at application mentions 'fix(tw10591): Fix restart problem after boot-strap' and contains an esp-idf folder (to replace the original IDF for that bug?). Can anyone clarify why is there an esp-idf folder inside of esp-at repository?

[WiFive]

Yes because at firmware is matched to a specific commit of IDF it is included as a submodule so you have to do git submodule update --init --recursive and set IDF_PATH to the folder inside esp32-at like the instructions. But you will still also have to fix the UART settings.