Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

AT port unresponsive #911

Open
3 tasks done
readysteadygo2006 opened this issue Feb 26, 2025 · 1 comment
Open
3 tasks done

AT port unresponsive #911

readysteadygo2006 opened this issue Feb 26, 2025 · 1 comment

Comments

@readysteadygo2006
Copy link

Answers checklist

  • I have read the documentation ESP-AT Programming Guide and the issue is not addressed there.
  • I have used the latest released firmware or have updated my ESP-AT branch (master or release) to the latest version and checked that the issue is present there.
  • I have searched the issue tracker for a similar issue and not found a similar issue.

AT+GMR

can not provide

ESP-AT Firmware Source

https://github.com/espressif/esp-at

Hardware Information

esp32-wroom-32

Power Supply used

USB

What is the expected behavior?

After booting the esp32 with the AT firmware, I get the standard log on the log console (UART0)
I get "ready" echoed to the AT uart (UART1)

I would expect to type a command and get a response on the at command console

What is the actual behavior?

If I type a command on the at command console, what I type gets echoed, but I get not response

Probability of recurrence

All the time

AT+SYSRAM?

not possible

Steps to reproduce

  1. Step
  2. Step
  3. Step
    ...

AT command port output

ready
AT+CMD

AT log port output

rst:0x1 (POWERON_RESET),boot:0x13 (SPI_FAST_FLASH_BOOT)
configsip: 0, SPIWP:0xee
clk_drv:0x00,q_drv:0x00,d_drv:0x00,cs0_drv:0x00,hd_drv:0x
00,wp_drv:0x00
mode:DIO, clock div:2
load:0x3fff0030,len:5916
ho 0 tail 12 room 4
load:0x40078000,len:15844
load:0x40080400,len:3548
entry 0x40080600
I (29) boot: ESP-IDF v5.0.6-dirty 2nd stage bootloader
I (29) boot: compile time 04:45:59
W (29) boot: Unicore bootloader
I (32) boot: chip revision: v1.0
I (35) boot.esp32: SPI Speed      : 40MHz
I (40) boot.esp32: SPI Mode       : DIO
I (45) boot.esp32: SPI Flash Size : 4MB
I (49) boot: Enabling RNG early entropy source...
I (55) boot: Partition Table:
I (58) boot: ## Label            Usage          Type ST O
ffset   Length
I (65) boot:  0 phy_init         RF data          01 01 0
000f000 00001000
I (73) boot:  1 otadata          OTA data         01 00 0
0010000 00002000
I (80) boot:  2 nvs              WiFi data        01 02 0
0012000 0000e000
I (88) boot:  3 at_customize     unknown          40 00 0
0020000 000e0000
I (95) boot:  4 ota_0            OTA app          00 10 0
0100000 00180000
I (103) boot:  5 ota_1            OTA app          00 11
00280000 00180000
I (110) boot: End of partition table
I (115) esp_image: segment 0: paddr=00100020 vaddr=3f4000
20 size=1a114h (106772) map
I (162) esp_image: segment 1: paddr=0011a13c vaddr=3ff800
63 size=00008h (     8) load
I (162) esp_image: segment 2: paddr=0011a14c vaddr=3ffbdb
60 size=050d0h ( 20688) load
I (176) esp_image: segment 3: paddr=0011f224 vaddr=400800
00 size=00df4h (  3572) load
I (178) esp_image: segment 4: paddr=00120020 vaddr=400d00
20 size=129b5ch (1219420) map
I (625) esp_image: segment 5: paddr=00249b84 vaddr=40080d
f4 size=1ee10h (126480) load
I (677) esp_image: segment 6: paddr=0026899c vaddr=400c00
00 size=00064h (   100) load
I (694) boot: Loaded app from partition at offset 0x10000
0
I (694) boot: Disabling RNG early entropy source...
no external 32k oscillator, disable it now.
at param mode: 1

More Information.

I've enabled debug, at can see debug messages of the characters I am typing on both the console and the at command console, so I'm confident that the uart is correctly configured.

@readysteadygo2006
Copy link
Author

Additionally, I see the same behaviour if I download the prebuilt esp-at (ESP32-WROOM-32-AT-V3.4.0.0)

I've tried using PUTTY and minicom as serial terminals

Are there any special setting required for the serial terminal?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant