I need to develop usb3.0 VIP , but I have some query regarding compliance mode of usb3.0.
How host/device goes to compliance mode.
Can Both host and device transition to compliance Mode state of LTSSM of link.???
when host in compliance mode and sending compliance pattern cp0,cp1… ,at that
time what device will do??? Same for device case.
when Host/Device in compliance mode state then it send compliance pattern and
spec says it change one compliance pattern to other by ping lfps , But Ping pfps
send by device/host in power down state U1 then , Is it necessary for device/host
which receive compliance pattern is in Low power state.
I need to develop usb3.0 VIP , but I have some query regarding compliance mode of usb3.0.
How host/device goes to compliance mode.
Can Both host and device transition to compliance Mode state of LTSSM of link.???
when host in compliance mode and sending compliance pattern cp0,cp1… ,at that
time what device will do??? Same for device case.
when Host/Device in compliance mode state then it send compliance pattern and
spec says it change one compliance pattern to other by ping lfps , But Ping pfps
send by device/host in power down state U1 then , Is it necessary for device/host
which receive compliance pattern is in Low power state.
I need to develop usb3.0 VIP , but I have some query regarding compliance mode of usb3.0.
How host/device goes to compliance mode.
Can Both host and device transition to compliance Mode state of LTSSM of link.???
when host in compliance mode and sending compliance pattern cp0,cp1… ,at that
time what device will do??? Same for device case.
when Host/Device in compliance mode state then it send compliance pattern and
spec says it change one compliance pattern to other by ping lfps , But Ping pfps
send by device/host in power down state U1 then , Is it necessary for device/host
which receive compliance pattern is in Low power state.
This is not really a Windows question. A standard driver stack will
never request compliance mode. That is only used by the special host
controller driver that is used for USB-IF compliance testing.
If you are developing host controller IP, then you really, really need
to be a member of the USB Implementor’s Forum. Once you join, you can
find resources to help you resolve detailed hardware questions like this.
–
Tim Roberts, xxxxx@probo.com
Providenza & Boekelheide, Inc.
7.5.4.3.2 Exit from Polling.LFPS
The port shall transition to Compliance Mode upon the 360-ms timer timeout
(tPollingLFPSTimeout) and the following two conditions are met:
The port has never successfully completed Polling.LFPS after PowerOn Reset.
The condition to transition to Polling.RxEQ is not met.
Note: If the very first attempt in Polling.LFPS handshake fails after PowerOn Reset, it implies
that a passive test load may be present and compliance test should be initiated. If the very first
attempt in Polling.LFPS handshake succeeds after PowerOn Reset, it implies the presence of
the SuperSpeed ports on each side of the link and no compliance test is intended. Therefore,
any subsequent handshake timeout in Polling.LFPS when the link is retrained is only an
indication of link training failure, not a signal to enter Compliance Mode.
Namely the first polling.lfps is failed conditioning link go to Compliance mode.
Yes, link means both side, not the single side.
both device and host port should transmit CPx.
No.
ping.lfps have different usage when link in compliance mode and U1 mode.
This thing is ok that , transmitter send CPx while receiver send ping lfps
, But one thing when device and host both in compliance mode at same time
then what happen…
In this case both host and device send CPx in this state and both wait for
ping lfps for CP advancing , Then how host/device send both(ping lfps and
CPx) at same time .
On Fri, Jul 19, 2013 at 7:49 AM, wrote:
> For 3, I need to clarify > > When in compliance mode, the device under test DUT, drive the CP0 - CP8 > patterns. > While linker partner, send ping.lfps to advance to CPn+1. > > DUT is not specific to USB device. > > So when device/host is transmitter, it send CPx, while the receiver side > control the CP advancing. > > > — > NTDEV is sponsored by OSR > > Visit the list at: http://www.osronline.com/showlists.cfm?list=ntdev > > OSR is HIRING!! See http://www.osr.com/careers > > For our schedule of WDF, WDM, debugging and other seminars visit: > http://www.osr.com/seminars > > To unsubscribe, visit the List Server section of OSR Online at > http://www.osronline.com/page.cfm?name=ListServer >