ESP32-S3 with ESP-IDF and TinyUSB UAC in VS-code/PlatformIO #3128
Replies: 1 comment 1 reply
-
Hi @MartijnElzinga4, usually, when the registers contain zeroes, there is a possibility that peripheral wasn't powered up (or in other words, usb phy wasn't enabled). Check whether you did it. To power it up, you need to add lines, as there are lines in the board support here |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Hello, i'm quite new to the github dicussion forum and hope I'm in the right section. I have not found anyone with the same issues and cannot seem to solve the error codes with the help of google/copilot so I'm giving this a try.
I'm trying to create a USB Audio device with a custom board with an ESP32-S3-WROOM-U1 device using the TinyUSB library. First I tried to do this in the Arduino framework until I found multiple cases online in which this was not the correct framework, which could not handle this, and I should use the ESP-IDF framework.
I need my device to communicate with a smartphone over USB-C for connecting to an external speaker/MIC and a PTT button. Currently i only have a Micro-USB connector available on my custom test board. But i have a USB-A to USB-C adapter board with 5.1Kohm resistors available to simulate the USB-C interface to the smartphone.
I found a "simple" example online and am trying to make it work in the PlatformIO environment in VS-Code. After a couple of days/weeks of trying, I can finally get the code to compile and upload to the board. But it looks like the combined USB interface does not seem to start. I get the following error codes:
check_dwc2 163: ASSERT FAILED dwc2_core_init 201: ASSERT FAILED dcd_init 410: ASSERT FAILED tud_rhport_init 504: ASSERT FAILED tusb_rhport_init 71: ASSERT FAILED
The check_dwc2 seems to be a hardware issue error. But I can connect my custom board to the desktop with the Micro-USB cable and can see a combined USB-interface in the USBlyser tool. This consists of a serial port(COMx) and USB/JTAG debug unit. This means the USB connection(D+/D-) is connected correcty.(I also tried reversing the wires, but I get the message that the USB device could not be detected).
The co-pilot in PlatformIO suggest it could be an issue of the VBUS detection. The ESP32 does not have a VBUS input and does not seem to have a VBUS detection. I even searched for anything in the lower-level codes but got lost.
` platform.ini
`
` main.cpp
}
`
` usb_descriptors.h
`
` usb_descriptors.cpp
}
`
The entire console output is as follows:
` console output:
`
After this the code seem to be stuck in the tud_task() and does not loop in the while.
Maybe someone has had a similar issue and could point me in the right direction. Any help would be much appreciated.
Beta Was this translation helpful? Give feedback.
All reactions