Ok,
now I have been reading through the documents with focus on USB.
Basically the OMAP5432 has
1 USB2.0/3.0 OTG capable port (OTG meaning it can be used for charging)
3 USB2 host only ports (2 with HSIC = serial and 1 with ULPI - i.e. we need an external driver chip anyways)
The ULPI-PHY on USB-B1 usually has an ID pin which can be read by the CPU and maybe generate an interrupt, but that does not make a client/OTG port out of it because the OMAP port can't receive data through it.
For mechanical USB sockets we have these limitations:
This means that we can't reasonably combine the USB3.0 OTG port of the OMAP with a Standard USB 3.0 socket, because we can't charge through it.
And, we can't use any other socket for charging since the USB2.0 ports of the OMAP are host only.
So the only combinations that we can reasonably interface to an OMAP5 are:
* OTG3.0 micro-AB port for charging and USB3 host (may need an external host cable for Standard USB devices)
* ca. 1-9 (through HSIC hubs) Host only ports of any size (A only and not AB)
So we would have enough USB ports for an internal USB-SD bridge if we want (see my other mail about multiple SD-Slots). But the chip availability is questionable.
This all means that I would propose:
1 USB 3.0-micro AB
1 USB 2.0-mini A
1 USB 2.0-A (that one can be combined with the eSATA wires - but we need a SMD capable socket for PCB routing)
And if we take all connectors we will have from left to right
* USB3-micro-AB (for charging)
* Pandora-Expansion
* USB2-A
* Headset
* HDMI
* USB2-mini-A
I still have to think a little about swapping the USB3-micro-AB and the USB2-mini-A because USB3 has very high speed signals and needs shortest wires to the CPU.
If you have no objections I would prepare the new PCB for this.
BR,
Nikolaus