TUSB522P: TUSB522P with Kaby-Lake board can not recognize the device

Hi,

In the KBL testing, are you using TUSB522P for the USB2 operation mode/interface? TUSB522P is meant for USB3.1 Gen1 not USB 2.0 interface.  Can you confrim the KBL testing is with a USB 3.0 interface and not USB2? 

Hi Sir,

KBL testing USB3.0 signal only.

Could you help check our EQ/DE setting is correct or not?

Why KBL fail but APL passed?

Thanks!!

Hi,

Would you be able to tell me which test failed or provide test report for this application (not sure if this was provided before)? In the tests were failures related to the eye diagram, jitter or LFPS? The "correct" EQ/DE settings depend on the pre and post channels as well as USB Host characteristics, it seems that APL USB host allows for better performance with your particular layout. Its would be useful to identify the difference between KBL and APL USB Host characteristics to full understand the problem. 

Hi Sirs,

More detail you could refer here

https://e2e.ti.com/support/interface/f/138/t/797031

Thanks!!

Hi,

I checked the test reports from the previous thread however bot APL and KBL past say passed. Could you repost so I have the most recent? Have you tried with a different USB Device and see if the same issue is seen?

Hi Sirs,

Sorry, the issue not close.

TUSB522P still fail on Kaby-Lake platform.

Redriver are put carry board 

KBL CPU + carry board will be fail 
APL CPU + carry board will be pass

The Carry board are same, only different on CPU board.

TX compliance test is pass on both CPU, 
The RX iEMT test has adjusted the de-emphasis & EQ strength of the re-driver to the weakest, but still can't recognize the device.
Did you need any more information?

Thanks!!

Is there any more support needed for this issue? If so please reply with any relevant details so that I can further assist you. If you have resolved your issue, please post the solution to the original problem/post for others with similar issues.

Hi Sirs,

Thanks for your reply

Actually we are not already clean this issue.

Just waiting internal SI team to provide time for test Rx signal.

If there have any idea in future feel free to let us know.

If we have any test result will let you know as soon.

Thanks!!

Hi,

Will do. I will wait for the RX data to evaluate further. 

Hi,

Was KBL + carry board able to enter loopback state for RX testing?

Hi Sirs,

Thanks for this message.

Unfortunately we still not booking internal LAB's time so not have this test result.

Any update will let you know as soon.

Thanks!!