This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

Is there an interoperability issue between SMSC3320 and TUSB2036?

Other Parts Discussed in Thread: OMAP3530, TUSB2036

Hi,

My customer's USB design looks like this:

USB Path 1) OMAP3530 to SMSC3320 (Works-only FS is used; HSUSB errata does not seem a affect FS)

USB Path 2) SMSC3320 to TUSB2036

USB Path 3) TUSB2036 downstream ports to outside world

Path 1 was verified by connecting an external USB device directly to SMSC3320.  Path 3 was verified by connecting a single board computer's USB directly to the TUSB2036 upstream port.

Path 2 does not work.  Is there a know issue with SMSC3320 interfacing to TUSB2036?

Thanks,

Rick