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
github-actionsbot
changed the title
Watchdog timeout in oc-cli example when configured with CONFIG_OPENTHREAD_CONSOLE_TYPE_USB_SERIAL_JTAG=y
Watchdog timeout in oc-cli example when configured with CONFIG_OPENTHREAD_CONSOLE_TYPE_USB_SERIAL_JTAG=y (IDFGH-14818)
Mar 10, 2025
Hi, @nicolas-christe I don't think this is a bug. On the ESP32-C6 devkit boards, there are two ports on the devkit boards.
If you connect the UART port, blue block shown in the picture, you should enable CONFIG_OPENTHREAD_CONSOLE_TYPE_UART, and if you changed to use USB port, green block shown in the picture, the CONFIG_OPENTHREAD_CONSOLE_TYPE_USB_SERIAL_JTAG should be enabled.
if I compile oc_cli example with CONFIG_OPENTHREAD_CONSOLE_TYPE_UART=y and connect to the blue port everything works fine, I have the log and can interact with openthread command line.
if I compile oc_cli example with CONFIG_OPENTHREAD_CONSOLE_TYPE_USB_SERIAL_JTAG=y and connect to the green port, I can run the app, on the console I have the log and few seconds after starting the watchdog time out error.
It's not a big issue for me because I can work with the UART port, but I was expecting the sample to also work with the USB port.
Answers checklist.
IDF version.
v5.4-690-gd4aa25a38e
Espressif SoC revision.
ESP32-C6 (QFN40) (revision v0.0)
Operating System used.
macOS
How did you build your project?
Command line with Make
If you are using Windows, please specify command line type.
None
Development Kit.
ESP32-C6-DevKitC-1
Power Supply used.
USB
What is the expected behavior?
I expect the example code to run without error
What is the actual behavior?
The sample code fail with a watchdog timeout error
Steps to reproduce.
Debug Logs.
More Information.
Example work fine when configured to use the UART for the openthread console (CONFIG_OPENTHREAD_CONSOLE_TYPE_UART=y)
The text was updated successfully, but these errors were encountered: