Yeah that's my concern: that once I take over the internal USB PHY for the TinyUSB usage, then I won't be able to easily give it back to the usb-serial-jtag (and vice versa).

So your question is actually if/how a BREAK can be detected when using the USB-JTAG serial? Ideally I think I'd get access to all standard UART interrupts, like single byte received, FIFO overflow, break, etc. Thinking further about it now though, I think I can get by with just the BREAK, handling ...

I would like to use the USB-serial-JTAG component of the S3 modules to process data coming in from the serial port, but not standard ASCII text UART. It is a protocol where I need to align on the packets to make sure i'm receiving the full set of data. The suggested way to receive data with this com...

Well good news and bad news I guess. The good news is that I assembled a 3rd board today and really took care on the stencil/placement, and also verified all connections under a microscope afterwards, and everything works as expected on bringup. The ESP enumerates as a standard serial port over USB,...

Sorry, didn't get a notification for the reply. I also had a thought about the TVS doing funky things, or maybe just being soldered 180 degrees. Unfortunately there is normal continuity between the expected pin pairings. I also pulled it off of the board and checked the ESP D+/D- lines again to see ...

Popped off the 0ohms and I see both lines from the ESP-side are floating. D- around 0V6-0V7, D+ around 0V3 to 0V4. I also gave the USB connector another hit of flux and the soldering iron to double check that nothing dodgy was happening with pins there but that did not help.

I've checked 10 times that I didn't flip them but I still could be missing something obvious. I'm not seeing any issues with the schematic or layout (and I've done this basic USB C 2.0 sub circuit multiple times before), but I've attached both for others to take a look. I redacted a lot of the layou...

I'm having this exact same issue, and unfortunately my main IC pad is already confirmed connected to ground. I know the chip is running properly because I can flash both a bootloader and bootloader+basic application firmware over UART. All voltages look good, except I don't see any output on VDD_SPI...

I know this is not an active thread, and i know it's related to the simultaneous use of wifi + ethernet, but I wanted to drop a different solution here in case anyone else was having the same problem as me. I also was seeing odd behaviour with link up / down repeatedly. When connected directly to a ...