-
Notifications
You must be signed in to change notification settings - Fork 7.2k
-
Notifications
You must be signed in to change notification settings - Fork 7.2k
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
example system/console/advanced_usb_cdc not working (IDFGH-11281) #12437
Comments
In addition to the plain example, I added this code.
Debug output:
|
@aircable I could reproduce your issue. It seems that the example only runs on ESP32-S2. We'll take a look to see what's wrong here. |
Hi @0xjakob, thanks for looking into it. If I can help you with anything, please let me know. I'm keen on using the VFS with esp_vfs_dev_cdcacm_register(). |
Hi @aircable, sorry about the issue. When I have initially added support for USB_OTG CDC console on ESP32-S3, I was using a development board with PHY_SEL efuse burned — which made USB_OTG peripheral connected to the internal USB PHY by default. However by default, this efuse is not burned, and a different peripheral (USB_SERIAL_JTAG) is connected to the USB PHY. |
@igrr, thank you for looking into it. I was able to get the console working, but not without modification of the example.
after setting the line endings and also had to remove the dumb mode on the console:
to get the command line working nicely on the USB. In dumb mode, flush does not work. Otherwise your fix worked. |
On ESP32-S3 with the default efuse settings, USB PHY is connected to the USB_SERIAL_JTAG peripheral. If USB OTG peripheral is used for the console, we need to additionally switch the PHY to USB OTG, otherwise we won't get any output. Closes #12437
On ESP32-S3 with the default efuse settings, USB PHY is connected to the USB_SERIAL_JTAG peripheral. If USB OTG peripheral is used for the console, we need to additionally switch the PHY to USB OTG, otherwise we won't get any output. Closes #12437
On ESP32-S3 with the default efuse settings, USB PHY is connected to the USB_SERIAL_JTAG peripheral. If USB OTG peripheral is used for the console, we need to additionally switch the PHY to USB OTG, otherwise we won't get any output. Closes #12437
On ESP32-S3 with the default efuse settings, USB PHY is connected to the USB_SERIAL_JTAG peripheral. If USB OTG peripheral is used for the console, we need to additionally switch the PHY to USB OTG, otherwise we won't get any output. Closes espressif#12437
On ESP32-S3 with the default efuse settings, USB PHY is connected to the USB_SERIAL_JTAG peripheral. If USB OTG peripheral is used for the console, we need to additionally switch the PHY to USB OTG, otherwise we won't get any output. Closes #12437
On ESP32-S3 with the default efuse settings, USB PHY is connected to the USB_SERIAL_JTAG peripheral. If USB OTG peripheral is used for the console, we need to additionally switch the PHY to USB OTG, otherwise we won't get any output. Closes espressif#12437
Answers checklist.
IDF version.
release/v5.0 and master
Espressif SoC revision.
ESP32-S3-PICO-1
Operating System used.
Linux
How did you build your project?
Command line with idf.py
If you are using Windows, please specify command line type.
None
Development Kit.
ESP32-S3-WROOM-1
Power Supply used.
USB
What is the expected behavior?
As the description says: show up with a command prompt and allow enter commands.
What is the actual behavior?
Connection is only through the internal USB port.
The example is flashed and monitored with the IDF command
Steps to reproduce.
In the example directory console/advanced_usb_cdc
Debug Logs.
I (728) esp_psram: Adding pool of 8178K of PSRAM memory to heap allocator
I (739) spi_flash: detected chip: gd
I (739) spi_flash: flash io: qio
I (739) sleep: Configure to isolate all GPIO pins in sleep state
I (739) sleep: Enable automatic switching of GPIO sleep configuration
I (742) esp_psram: Reserving pool of 32K of internal memory for DMA/internal allocations
The text was updated successfully, but these errors were encountered: