I planned to connect ESP32 with SIM7600 GSM module, that supports up to 50Mbit/s in 'upload'. SIM7600 goes concept, that supposes grabbing data from SD card or USB (SIM7600 provides USB-HS for high speed download data). But ESP32-S3 not. I'm not too familiar with the SIM7600 GSM. But if it's a USB2...

Do you think it is an option from the host side to "tell" the device "we are FS only" and thanks to this we can get FS descriptors? USB2.0 actually operates on the opposite logic. All HS capable devices start out as FS by default. The device must indicate to the host/hub the need to switch to HS by...

Hi @Axent1987, we're aware that USB-HS is something we don't have right now and we are looking into the possibility of including it in future chips. But unfortunately we don't have anything concrete to announce at this point. I tried to implement ULPI in ESP32 with some other ways, but it requires 6...

@marbalon Devices are supposed to return the valid descriptors corresponding to their current speed. So, if your high-speed capable device is connected to an FS only Host, then the device should only return FS descriptors. Quote from USB2.0 specification section "9.2.6.6 Speed Dependent Descriptors"...

@Flatland. Could you automatically launch GDB stub when crashing (via the CONFIG_ESP_SYSTEM_PANIC_GDBSTUB menuconfig option). Once the assertion fails inside hcd_urb_enqueue(), could you use GDB to dump the current values of the "urb" object? Those values could give use some clues as to what's curre...

Are you submitting a transfer again before it has completed (i.e., before the transfer's callback has been called). Each transfer (i.e., URB) internally keeps a state variable "hcd_var", that check is checking that the URB is indeed idle (i.e., has not be submitted yet) before trying to enqueue it f...

Looks like the level 1 interrupt entry code is hitting a bad stack pointer (_xt_lowint1), thus why it's jumping a double exception vector. When the stack pointer itself is corrupted, there isn't really a way to recover the rest of the stack due to xtensa's windowed ABI (previous stack frame's stack ...

VincentChan wrote: The output console displays CAN message failed to queue for transmission. Can anyone help? Thank you.

Can you check what the error code is?

@ CraftyMyner

If you're on the ESP32, could you check that you have enabled all of the TWAI driver's Hardware Errata workarounds in menuconfig?

If I wanted to treat the USB port as a typical dev board serial port (like a UART) I don't think I'm understanding you correctly. Do you want the ESP32-S3 USB port to act as a USB Device or a USB Host? Typically if you want you to transfer serial data from the ESP32-S3 to a PC via the USB port, the...