ISP1760ET,557

Manufacturer Part NumberISP1760ET,557
ManufacturerNXP Semiconductors
ISP1760ET,557 datasheet
 

Specifications of ISP1760ET,557

Package TypeTFBGAPin Count128
Lead Free Status / RoHS StatusCompliant  
1
2
3
4
5
6
7
8
9
10
11
Page 11
12
Page 12
13
Page 13
14
Page 14
15
Page 15
16
Page 16
17
Page 17
18
Page 18
19
Page 19
20
Page 20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
Page 16/111

Download datasheet (570Kb)Embed
PrevNext
NXP Semiconductors
Table 3.
Port connection scenarios
Port configuration
Port 1
One port (port 1)
DP and DM are routed to USB
connector
One port (port 2)
DP and DM are not connected
(left open)
One port (port 3)
DP and DM are not connected
(left open)
Two ports (ports 1
DP and DM are routed to USB
and 2)
connector
Two ports (ports 2
DP and DM are not connected
and 3)
(left open)
Two ports (ports 1
DP and DM are routed to USB
and 3)
connector
Three ports (ports 1,
DP and DM are routed to USB
2 and 3)
connector
7.2 Host controller buffer memory block
7.2.1 General considerations
The internal addressable host controller buffer memory is 63 kB. The 63 kB effective
memory size is the result of subtracting the size of the registers (1 kB) from the total
addressable memory space defined in the ISP1760 (64 kB). This is the optimized value to
achieve the highest performance with minimal cost.
The ISP1760 is a slave host controller. This means that it does not need access to the
local bus of the system to transfer data from the system memory to the ISP1760 internal
memory, unlike the case of the original PCI Hi-Speed USB host controllers. Therefore,
correct data must be transferred to both the PTD area and the payload area by PIO (using
CPU access) or programmed DMA.
The ‘slave-host’ architecture ensures better compatibility with most of the processors
present in the market today because not all processors allow a ‘bus-master’ on the local
bus. It also allows better load balancing of the processor’s local bus because only the
internal bus arbiter of the processor controls the transfer of data dedicated to USB. This
prevents the local bus from being busy when other more important transfers may be in the
queue; and therefore achieving a ‘linear’ system data flow that has less impact on other
processes running at the same time.
The considerations mentioned are also the main reason for implementing the pre-fetching
technique, instead of using a READY signal. The resulting architecture avoids ‘freezing’ of
the local bus, by asserting READY, enhancing the ISP1760 memory access time, and
avoiding introduction of programmed additional wait states. For details, see
and
Section
The total amount of memory allocated to the payload determines the maximum transfer
size specified by a PTD, a larger internal memory size results in less CPU interruption for
transfer programming. This means less time spent in context switching, resulting in better
CPU usage.
ISP1760_4
Product data sheet
Port 2
DP and DM are not connected
(left open)
DP and DM are routed to USB
connector
DP and DM are not connected
(left open)
DP and DM are routed to USB
connector
DP and DM are routed to USB
connector
DP and DM are not connected
(left open)
DP and DM are routed to USB
connector
8.3.8.
Rev. 04 — 4 February 2008
ISP1760
Embedded Hi-Speed USB host controller
Port 3
DP and DM are not connected
(left open)
DP and DM are not connected
(left open)
DP and DM are routed to USB
connector
DP and DM are not connected
(left open)
DP and DM are routed to USB
connector
DP and DM are routed to USB
connector
DP and DM are routed to USB
connector
© NXP B.V. 2008. All rights reserved.
Section 7.3
15 of 110