USBN9604-28M/NOPB National Semiconductor, USBN9604-28M/NOPB Datasheet - Page 22
![IC CONTROLLER SERIAL BUS 28-SOIC](/photos/6/59/65917/pkg_m28b_sml.jpg)
USBN9604-28M/NOPB
Manufacturer Part Number
USBN9604-28M/NOPB
Description
IC CONTROLLER SERIAL BUS 28-SOIC
Manufacturer
National Semiconductor
Datasheet
1.USBN9604-28MNOPB.pdf
(60 pages)
Specifications of USBN9604-28M/NOPB
Controller Type
USB 2.0 Controller
Interface
Parallel/Serial
Voltage - Supply
3 V ~ 5.5 V
Current - Supply
30mA
Operating Temperature
0°C ~ 70°C
Mounting Type
Surface Mount
Package / Case
28-SOIC (7.5mm Width)
For Use With
USBN9604-HS-EB - KIT NODE CONTROLLER SAMPLE
Lead Free Status / RoHS Status
Lead free / RoHS Compliant
Other names
*USBN9604-28M
*USBN9604-28M/NOPB
USBN9604-28M
*USBN9604-28M/NOPB
USBN9604-28M
Available stocks
Company
Part Number
Manufacturer
Quantity
Price
Company:
Part Number:
USBN9604-28M/NOPB
Manufacturer:
Freescale
Quantity:
2 314
Part Number:
USBN9604-28M/NOPB
Manufacturer:
TI/德州仪器
Quantity:
20 000
www.national.com
6.0 Functional Description
6.1 FUNCTIONAL STATES
6.1.1
At any given time, the device is in one of the following states (see Section 6.1.2 for the functional state transitions):
The NodeSuspend, NodeResume, or NodeReset line condition causes a transition from one operating state to another.
These conditions are detected by specialized hardware and reported via the Alternate Event (ALTEV) register. If interrupts
are enabled, an interrupt is generated upon the occurrence of any of the specified conditions.
NodeOperational
This is the normal operating state of the device. In this state, the node is configured for operation on the USB bus.
NodeSuspend
A USB device is expected to enter NodeSuspend state when 3 mS have elapsed without any detectable bus activity. The
device looks for this event and signals it by setting the SD3 bit in the ALTEV register, which causes an interrupt, if enabled,
to be generated. The firmware should respond by putting the device into the NodeSuspend state.
The device can resume normal operation under firmware control in response to a local event at the host controller. It can
wake up the USB bus via a NodeResume, or when detecting a resume command on the USB bus, which signals an interrupt
to the host controller.
NodeResume
If the host has enabled remote wake-ups from the node, the device can initiate a remote wake-up.
Once the firmware detects the event, which wakes up the bus, it releases the device from NodeSuspend state by initiating
a NodeResume on the USB using the NFSR register. The node firmware must ensure at least 5 mS of Idle on the USB.
While in NodeResume state, a constant “K” is signalled on the USB. This should last for at least 1 mS and no more than 5
mS, after which the USB host should continue sending the NodeResume signal for at least an additional 20 mS, and then
completes the NodeResume operation by issuing the End Of Packet (EOP) sequence.
To successfully detect the EOP, the firmware must enter USB NodeOperational state by setting the NFSR register.
If no EOP is received from the host within 100 mS, the software must reinitiate NodeResume.
NodeReset
When detecting a NodeResume or NodeReset signal while in NodeSuspend state, the device can signal this to the main
controller by generating an interrupt.
USB specifications require that a device must be ready to respond to USB tokens within 10 mS after wake-up or reset.
6.1.2
Figure 18 shows the device states and transitions, as well as the conditions that trigger each transition. All state transitions
are initiated by the firmware.
•
•
•
•
NodeOperational
NodeSuspend
NodeResume
NodeReset
Line Condition Detection
Functional State Transition
Normal operation
Device operation suspended due to USB inactivity
Device wake-up from suspended state
Device reset
22