Hi,
I bought the HD3SS460EVM and I am looking at the user guide sllu214b.pdf
Can I get the full schematic for the TI HD3SS460EVM?
The User’s guide has a partial schematic, but it’s not the actual schematic.
What’s missing is how the APU_DP_TX?N/APU_DP_TX?P signals get routed to the ML?N/ML?P nets
Essentially the right half of U2 (middle right hand box) is presented really bad. That’s not how a real schematic should look. It’s really odd because outside of that it’s a real schematic.
Additional questions for TI regarding the HD3SS460
-
On Page 20 of the datasheet it says “For ease of routing, the P and N connection of the USB 3.1 differential pairs to the HD3SS460 pins can be swapped as long as the corresponding pairs are swapped on the other end of the switch. This example is shown in the reference EVM schematic section of this document.”.
What it says makes perfect sense, but I don’t see any example of it on that document. I do see on page 17 that they’ve swapped the P/N of the 4 differential output pins going to the Type C connector, and they’ve swapped the P/N of the 4 differential signals inputs coming from the DisplayPort Source. But, they don’t swap the USB 3.1 RX P/N pins or the USB 3.1 TX P/N pins. They do the same thing on the HD3SS460EVM, and on the TIDA-00630 TI Type C Dock Schematic. But, I don’t see anywhere where the logic in this is explained. Why swap the output pins, and the DisplayPort input pins but not the SSTXN/SSTXP or SSRXN/SSRXP pins?
-
On Page 8 of the EVM User Guide it shows ML1 being mapped to LaneA, and ML0 being mapped to LaneB. Which I find confusing because that connection is for a DisplayPort Sink. But, the EVM acts like a DisplayPort Source. On that same page on the Top left it has the pinout that matches a Source Output pin mapping. My understanding is in a USB type C cable the RX/TX pairs are swapped. They’re swapped so the TX of the one side can go to the RX of the other side, and vice versa. This is great for USB 3.0 applications because there is no worry about which side is which. But, for ALT connections like running displayport over it we have to account for this swap. From my understanding this is accounted for by having a Source pin mapping, and a Sink pin mapping.
