I would like to clarify the VBUS, ID and REFCLK settings shown in Figures 10.1 and 10.2 in the TUSB1210 data sheet.
http://www.ti.com/lit/ds/symlink/tusb1210.pdf
In Figure 10-1 (Host or OTG, ULPI Input Clock Mode Application Diagram) a USB Type B (device) connector is used. There is a VBUS Switch to apply power to this Type B connector. Further, the ID pin of the Type B connector is tied to the TUSB1210. The section title and wording suggests this section is intended for a Host application, yet the Type B connector and the ID pin suggest a Device mode application. Finally, the REFCLK is tied low in this configuration.
The converse is shown in Figure 10-2 (Device, ULPI Output Clock Mode Application Diagram) for a Device Mode application.
Can you please confirm the correct implementation?
Hi Rob,
Please refer to Table4-1 and Table4-2 of Micro-USB_1_01.pdf specification available on usb.org.
Please note particularly that a Micro-AB receptacle contains an ID pin, as do Micro-A and Micro-B connectors also.
TUSB1210 datasheet Figure 10-1 is indeed for (Host or OTG, ULPI Input Clock Mode Application Diagram) and shows a receptacle (not a connector). Since this single diagram is meant to cover both Host (no ID pin in Standard-A receptacle) or OTG (ID pin is present in Micro-AB receptacle) applications, the ID pin was included. The receptacle is not Type-B (Standard/Mini/Micro), and the title of Figure 10-1 clearly states this (Host or OTG). When Host, or OTG acting as Host, TUSB1211 may be required to provide VBUS, and so one example of VBUS being provided through a switch is illustrated. The REFCLK tied low is because ULPI is in Input clock mode (please refer to Chapter 4.2 in TUSB1210 datasheet) in Figure 10-1, although this is independent of Host/Device/OTG since it is just the configuration of the PHY-to-Link ULPI interface. Figure 10-2 (Device, ULPI Output Clock Mode Application) shows an example of ULPI in Output clock mode (REFCLK required) but again this is indepent of the fact that the rest of this Figure has been chosen to depict a Device mode application.
Therefore I see no error in these implementation examples in TUSB1210 datasheet.
Best regards,
Peter