-
Notifications
You must be signed in to change notification settings - Fork 215
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
esp32s3 usb_serial.rs example not working #495
Comments
Regarding the problems compiling it: You probably didn't run the example inside the repo? There is a breaking change regarding the TimerGroup initialization It definitely worked before but I can confirm it stopped working We need to check which commit broke it |
Correct i have used the template generator tool to make a new project and then copied the code to the generated project |
the compiling issue was introduced with this pr: #463 |
@MabezDev this is a Rust compiler issue apparently .... it works (even with current main) with the Xtensa-enabled Rust compiler 1.65 and 1.66 but not with 1.67, 1.68 or 1.69 👻 |
I also think that there is a problem with the crate, i can see in you example that you point directly to github and that you do not just let cargo get it from the crates registry |
Yes, at the time of writing that example we haven't had a release of esp-hal including usb-device support yet |
When i try to setup the usb_serial.rs example it first of all do not compile.
I have to modify the arguments given to TimerGroup::new. I have to remove third argument: &mut system.peripheral_clock_control,
When i then build it and flash it and plug it into my pc the usb port is not showing up and i get a lot of usb errors.
When looking a bit more in the code it looks like the usb_dp and usb_dm are swapped, im using a T-Displat-S3 from Lilygo, but it also looks like the esp32-s3-devkit-c is having the same pinout: https://docs.espressif.com/projects/esp-idf/en/latest/esp32s3/hw-reference/esp32s3/user-guide-devkitc-1.html
Can anyone help me figure out how to fix the issue?
The text was updated successfully, but these errors were encountered: