SAF1761BE/V1,518 NXP Semiconductors, SAF1761BE/V1,518 Datasheet - Page 152

• Manufacturer Part Number: SAF1761BE/V1,518
• Manufacturer: NXP Semiconductors

Specifications of SAF1761BE/V1,518

• Lead Free Status / Rohs Status: Compliant

NXP Semiconductors
SAF1761_1
Product data sheet
18.6.3.1 Condition 1
18.6.3.2 Condition 2
18.6.2 Implication
18.6.3 Workaround
The implication will be serious if the device is getting disconnected during the data
transfer.
The software workaround will check if a port has suddenly been disabled (Port Enable bit
cleared) when a device is still connected to the port. Once it detects this condition, the
software workaround will perform the necessary steps to re-enable the port and
reschedule any halted transfer because of the error condition.
The following actions are taken by the software once the error condition is detected:
There are two conditions when the software workaround will be invoked and appropriate
actions will be taken to determine if it truly is a problematic behavior (see
Section 18.6.3.2
Condition 1 refers to the condition when Port Enable/Disable Change event is detected
in the Hub Class driver. To determine and resolve the problematic condition, the following
steps are taken:
Check the Port Status again to see if the port has recovered. See also
Condition 2 refers to the condition when a HALT occurs during PTD processing without
other bus errors (that is, babble, transaction error).
•
•
•
•
•
•
•
•
•
•
•
•
•
Increment the count of the variable that keeps the number of times the ports have
been force enabled.
Determine which active PTDs (ATL and INTL) are scheduled to the affected port and
suspend them.
Determine the speed of the device connected to the affected port.
Put the internal hub in Force Configure mode.
Force enable the affected port (this will set the Port Enable bit of the affected port to 1
again).
Remove the force enable on the affected port.
Remark: If the force enable is set, the particular port will always be enabled even if
the device connected has been removed.
Put the internal hub back to normal mode (exit from the force configure mode).
Re-active all the suspended PTDs.
Determine if the hub event has occurred on one of the internal hubs three ports and if
the connected device is either full-speed or low-speed.
Determine if the port enable bit is cleared when a device is still connected on the port.
Ensure that the port has not been force enabled three consecutive times by checking
the variable that keeps track of the number of times the port has been force enabled.
Otherwise, reset the port if it has been force enabled three consecutive times.
Invoke the software workaround.
and
Rev. 01 — 18 November 2009
Section
18.6.3.3).
Hi-Speed USB OTG controller
SAF1761
Section
© NXP B.V. 2009. All rights reserved.
Section
18.6.3.3.
18.6.3.1,
152 of 166