Talk:OMAP35x Schematic Checklist

Comments on OMAP35x Schematic Checklist -

D-smalley said ...
MMC/SD related pins on CBC package formerly listed as PBIAS_MMC1 (ball N18) and PBIAS_MMC1a (ball K23) should be left as "no connects" since pulling these to VDDS_MMC can cause problems

--D-smalley 14:48, 1 December 2009 (CST)

Arembisz said ...
recommend including link to the SD-MMC usage notes on this page: http://wiki.davincidsp.com/index.php/SD-MMC_Usage_Notes_on_OMAP35x

--Arembisz 12:34, 2 December 2009 (CST)

D-smalley said ...
Note that USB host ports (USB1 and USB2) can be connected internally to either EHCI sub-controller (HS operation) or OHCI sub-controller. The EHCI controller only supports ULPI interface to external PHY and the OHCI controller only supports serial interface to external PHY. Therefore the selection of hardware PHY typically fixes the operating mode as either HS operation or FS/LS operation. That is, if ULPI HS PHY is connected, it will not be possible to run the port in FS/LS mode.

--D-smalley 16:05, 8 January 2010 (CST)

D-smalley said ...
USB Host PHY should have its reset connected to logical AND of gpio and nRESPWRON since EHCI software driver asserts manual reset during initialization and during some USB errata workarounds. See OMAP35xx EVM main board schematics for reference

--D-smalley 09:57, 29 October 2010 (CDT)

D-smalley said ...
USB Host PHY should have its reset connected to logical AND of gpio and nRESPWRON since EHCI software driver asserts manual reset during initialization and during some USB errata workarounds. See OMAP35xx EVM main board schematics for reference

--D-smalley 11:34, 29 October 2010 (CDT)