You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have updated my IDF 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.
General issue report
I compiled the example that illustrates the use of the console component (esp-idf/examples/system/console/advanced/) to create an interactive shell on an ESP chip. It compiles without problem and loads (flash) to the microcontroller without problem. But when I try to connect with idf.py monitor gets stuck. When I connect with Putty it doesn't show anything. I'm using ESP-IDF v5.3.1. and ESP-IDE development environment.
I've already searched and tried possible solutions but everything is still the same. Any ideas or suggestions? Thank you very much.
This is the message I get with idf.py:
idf.py monitor
Executing action: monitor
Serial port COM8
Connecting...
Detecting chip type... ESP32-C6
Running idf_monitor in directory C:\Users\Consola\myCLI\advanced
Executing "C:\Espressif\python_env\idf5.3_py3.11_env\Scripts\python.exe C:\Espressif\frameworks\esp-idf-v5.3.1\tools/idf_monitor.py -p COM8 -b 115200 --toolchain-prefix riscv32-esp-elf- --target esp32c6 --revision 0 --decode-panic backtrace C:\Users\Consola\myCLI\advanced\build\console.elf --force-color -m 'C:\Espressif\python_env\idf5.3_py3.11_env\Scripts\python.exe' 'C:\Espressif\frameworks\esp-idf-v5.3.1\tools\idf.py'"...
--- Warning: GDB cannot open serial ports accessed as COMx
--- Using \.\COM8 instead...
--- esp-idf-monitor 1.5.0 on \.\COM8 115200
--- Quit: Ctrl+] | Menu: Ctrl+T | Help: Ctrl+T followed by Ctrl+H
ESP-ROM:esp32c6-20220919
Build:Sep 19 2022
rst:0x15 (USB_UART_HPSYS),boot:0x18 (SPI_FAST_FLASH_BOOT)
Saved PC:0x40022ef0
--- 0x40022ef0: uart_rx_readbuff in ROM
SPIWP:0xee
mode:DIO, clock div:2
load:0x40875720,len:0x1338
load:0x4086c110,len:0xc70
load:0x4086e610,len:0x2c14
entry 0x4086c110
I (228) cpu_start: Unicore app
I (237) cpu_start: Pro cpu start user code
I (237) cpu_start: cpu freq: 160000000 Hz
I (238) app_init: Application information:
I (240) app_init: Project name: console
I (245) app_init: App version: 1
I (249) app_init: Compile time: Nov 22 2024 10:30:12
I (255) app_init: ELF file SHA256: b575dabdc...
I (260) app_init: ESP-IDF: HEAD-HASH-NOTFOUND
I (266) efuse_init: Min chip rev: v0.0
I (271) efuse_init: Max chip rev: v0.99
I (276) efuse_init: Chip rev: v0.0
I (281) heap_init: Initializing. RAM available for dynamic allocation:
I (288) heap_init: At 408253A0 len 00057270 (348 KiB): RAM
I (294) heap_init: At 4087C610 len 00002F54 (11 KiB): RAM
I (300) heap_init: At 50000064 len 00003F84 (15 KiB): RTCRAM
I (307) spi_flash: detected chip: generic
I (311) spi_flash: flash io: dio
I (315) sleep: Configure to isolate all GPIO pins in sleep state
I (322) sleep: Enable automatic switching of GPIO sleep configuration
The text was updated successfully, but these errors were encountered:
Hi @UlissesUy
Which console output did you select in menuconfig before build? And which port are you monitoring? Also, which devkit are you using?
It looks like, you have flashed the console example for USB-UART console (which is the default for this example), you are monitoring JTAG port and using a devkit with only one port, being JTAG.
Hi Peter, thanks for your reply.
I am using FireBeetle 2 ESP32-C6 IoT Development Board. It has only one USB port. In menuconfig I used UART number 0. All settings are default.
Thanks a lot.
Looking at the dev board you are using, it seems there is no usb-uart converter, so just select JTAG console in menuconfig, and the example shall work just fine.
Either this, or, if you want to use JTAG port for debugging while running console application, you can implement a custom usb-uart console, by connecting an external UAB-UART converter to UART pins on you dev board and set the menuconfig accordingly, to which UART peripheral you have connected your external converter.
Answers checklist.
General issue report
I compiled the example that illustrates the use of the console component (esp-idf/examples/system/console/advanced/) to create an interactive shell on an ESP chip. It compiles without problem and loads (flash) to the microcontroller without problem. But when I try to connect with idf.py monitor gets stuck. When I connect with Putty it doesn't show anything. I'm using ESP-IDF v5.3.1. and ESP-IDE development environment.
I've already searched and tried possible solutions but everything is still the same. Any ideas or suggestions? Thank you very much.
This is the message I get with idf.py:
idf.py monitor
Executing action: monitor
Serial port COM8
Connecting...
Detecting chip type... ESP32-C6
Running idf_monitor in directory C:\Users\Consola\myCLI\advanced
Executing "C:\Espressif\python_env\idf5.3_py3.11_env\Scripts\python.exe C:\Espressif\frameworks\esp-idf-v5.3.1\tools/idf_monitor.py -p COM8 -b 115200 --toolchain-prefix riscv32-esp-elf- --target esp32c6 --revision 0 --decode-panic backtrace C:\Users\Consola\myCLI\advanced\build\console.elf --force-color -m 'C:\Espressif\python_env\idf5.3_py3.11_env\Scripts\python.exe' 'C:\Espressif\frameworks\esp-idf-v5.3.1\tools\idf.py'"...
--- Warning: GDB cannot open serial ports accessed as COMx
--- Using \.\COM8 instead...
--- esp-idf-monitor 1.5.0 on \.\COM8 115200
--- Quit: Ctrl+] | Menu: Ctrl+T | Help: Ctrl+T followed by Ctrl+H
ESP-ROM:esp32c6-20220919
Build:Sep 19 2022
rst:0x15 (USB_UART_HPSYS),boot:0x18 (SPI_FAST_FLASH_BOOT)
Saved PC:0x40022ef0
--- 0x40022ef0: uart_rx_readbuff in ROM
SPIWP:0xee
mode:DIO, clock div:2
load:0x40875720,len:0x1338
load:0x4086c110,len:0xc70
load:0x4086e610,len:0x2c14
entry 0x4086c110
I (228) cpu_start: Unicore app
I (237) cpu_start: Pro cpu start user code
I (237) cpu_start: cpu freq: 160000000 Hz
I (238) app_init: Application information:
I (240) app_init: Project name: console
I (245) app_init: App version: 1
I (249) app_init: Compile time: Nov 22 2024 10:30:12
I (255) app_init: ELF file SHA256: b575dabdc...
I (260) app_init: ESP-IDF: HEAD-HASH-NOTFOUND
I (266) efuse_init: Min chip rev: v0.0
I (271) efuse_init: Max chip rev: v0.99
I (276) efuse_init: Chip rev: v0.0
I (281) heap_init: Initializing. RAM available for dynamic allocation:
I (288) heap_init: At 408253A0 len 00057270 (348 KiB): RAM
I (294) heap_init: At 4087C610 len 00002F54 (11 KiB): RAM
I (300) heap_init: At 50000064 len 00003F84 (15 KiB): RTCRAM
I (307) spi_flash: detected chip: generic
I (311) spi_flash: flash io: dio
I (315) sleep: Configure to isolate all GPIO pins in sleep state
I (322) sleep: Enable automatic switching of GPIO sleep configuration
The text was updated successfully, but these errors were encountered: