Supports up to 16:1 MUX
— Programmable Pull-ups, Bus Hold Latch and Open
Drain on I/O Pins
— Outputs Tri-state During Power-up (“Live Insertion”
Friendly)
• DESIGN SUPPORT THROUGH LATTICE’S ispGDX
DEVELOPMENT SOFTWARE
— MS Windows or NT / PC-Based or Sun O/S
— Easy Text-Based Design Entry
— Automatic Signal Routing
— Program up to 100 ISP Devices Concurrently
— Simulator Netlist Generation for Easy Board-Level
The ispGDXV/VA architecture provides a family of fast,
flexible programmable devices to address a variety of
system-level digital signal routing and interface requirements including:
• Multi-Port Multiprocessor Interfaces
• Wide Data and Address Bus Multiplexing
(e.g. 16:1 High-Speed Bus MUX)
• Programmable Control Signal Routing
(e.g. Interrupts, DMAREQs, etc.)
• Board-Level PCB Signal Routing for Prototyping or
Programmable Bus Interfaces
The devices feature fast operation, with input-to-output
signal delays (Tpd) of 3.5ns and clock-to-output delays of
3.5ns.
The architecture of the devices consists of a series of
programmable I/O cells interconnected by a Global Routing Pool (GRP). All I/O pin inputs enter the GRP directly
or are registered or latched so they can be routed to the
required I/O outputs. I/O pin inputs are defined as four
sets (A,B,C,D) which have access to the four MUX inputs
I/O
Cells
I/O Pins A
I/O Pins D
Global Routing
Pool
(GRP)
I/O Pins B
I/O
Cells
ISP
Control
I/O Pins C
TM
Description (Continued)
Specifications ispGDX160V/VA
found in each I/O cell. Each output has individual, programmable I/O tri-state control (OE), output latch clock
(CLK), clock enable (CLKEN), and two multiplexer control (MUX0 and MUX1) inputs. Polarity for these signals
is programmable for each I/O cell. The MUX0 and MUX1
inputs control a fast 4:1 MUX, allowing dynamic selection
of up to four signal sources for a given output. A wider
16:1 MUX can be implemented with the MUX expander
feature of each I/O and a propagation delay increase of
2.0ns. OE, CLK, CLKEN, and MUX0 and MUX1 inputs
can be driven directly from selected sets of I/O pins.
Optional dedicated clock input pins give minimum clockto-output delays. CLK and CLKEN share the same set of
I/O pins. CLKEN disables the register clock when
CLKEN = 0.
Through in-system programming, connections between
I/O pins and architectural features (latched or registered
inputs or outputs, output enable control, etc.) can be
defined. In keeping with its data path application focus,
the ispGDXV devices contain no programmable logic
arrays. All input pins include Schmitt trigger buffers for
noise immunity. These connections are programmed
into the device using non-volatile E
2
CMOS technology.
Non-volatile technology means the device configuration
is saved even when the power is removed from the
device.
In addition, there are no pin-to-pin routing constraints for
any
1:1 or 1:n signal routing. That is,
I/O pin configured
as an input can drive one or more I/O pins configured as
outputs.
The device pins also have the ability to set outputs to
fixed HIGH or LOW logic levels (Jumper or DIP Switch
mode). Device outputs are specified for 24mA sink and
12mA source current (at JEDEC LVTTL levels) and can
be tied together in parallel for greater drive. On the
ispGDXVA, each I/O pin is individually programmable for
3.3V or 2.5V output levels as described later. Programmable output slew rate control can be defined
independently for each I/O pin to reduce overall ground
bounce and switching noise.
All I/O pins are equipped with IEEE1149.1-compliant
Boundary Scan Test circuitry for enhanced testability. In
addition, in-system programming is supported through
the Test Access Port via a special set of private commands.
The ispGDXV I/Os are designed to withstand “live insertion” system environments. The I/O buffers are disabled
during power-up and power-down cycles. When designing for “live insertion,” absolute maximum rating conditions
for the Vcc and I/O pins must still be met.
* The CLK/CLK_EN, OE, MUX0 and MUX1 terminals on each I/O cell can each be assigned to
25% of the I/Os.
** Global clock pins Y0, Y1, Y2 and Y3 are multiplexed with CLKEN0, CLKEN1, CLKEN2 and
CLKEN3 respectively in all devices.
ispGDXV/VA Device
ispGDX80VAispGDX240VA
80
20
20
20
20
2
1
1
4
1
100-Pin TQFP
ispGDX160V/VA
1
1
208-Ball fpBGA
272-Ball BGA
240
60
60
60
60
4
1
1
4
1
388-Ball fpBGA
2
Architecture
Specifications ispGDX160V/VA
The ispGDXV/VA architecture is different from traditional
PLD architectures, in keeping with its unique application
focus. The block diagram is shown below. The program-
The various I/O pin sets are also shown in the block
diagram below. The A, B, C, and D I/O pins are grouped
together with one group per side.
mable interconnect consists of a single Global Routing
Pool (GRP). Unlike ispLSI devices, there are no programmable logic arrays on the device. Control signals for
OEs, Clocks/Clock Enables and MUX Controls must
come from designated sets of I/O pins. The polarity of
these signals can be independently programmed in each
I/O cell.
Each I/O cell drives a unique pin. The OE control for each
I/O pin is independent and may be driven via the GRP by
one of the designated I/O pins (I/O-OE set). The I/O-OE
set consists of 25% of the total I/O pins. Boundary Scan
test is supported by dedicated registers at each I/O pin.
In-system programming is accomplished through the
standard Boundary Scan protocol.
I/O Architecture
Each I/O cell contains a 4:1 dynamic MUX controlled by
two select lines as well as a 4x4 crossbar switch con-
trolled by software for increased routing flexiability (Figure
1). The four data inputs to the MUX (called M0, M1, M2,
and M3) come from I/O signals in the GRP and/or
adjacent I/O cells. Each MUX data input can access one
quarter of the total I/Os. For example, in a 160 I/O
ispGDXV, each data input can connect to one of 40 I/O
pins. MUX0 and MUX1 can be driven by designated I/O
pins called MUXsel1 and MUXsel2. Each MUXsel input
covers 25% of the total I/O pins (e.g. 40 out of 160). MUX0
and MUX1 can be driven from either MUXsel1 or MUXsel2.
ispGDXV/VA architecture enhancements over ispGDX (5V)
4-to-1 MUX
M0
M1
M2
M3
MUX1MUX0
I/O Cell 158
To 2 Adjacent
I/O Cells above
To 2 Adjacent
I/O Cells below
I/O Cell 81
I/O Cell 80
•
•
•
•
•
•
Bypass Option
Register
or Latch
A
D
B
CLK
CLK_EN
Reset
Prog.
Prog.
Bus Hold
Pull-up
Latch
(VCCIO)
C
Q
R
Prog. Open Drain
2.5V/3.3V Output
Prog. Slew Rate
Boundary
Scan Cell
I/O
Pin
I/O Cell N
3
Specifications ispGDX160V/VA
I/O MUX Operation
MUX1MUX0Data Input Selected
00M0
01M1
11M2
10M3
Flexible mapping of MUXselx to MUXx allows the user to
change the MUX select assignment after the ispGDXV/
VA device has been soldered to the board. Figure 1
shows that the I/O cell can accept (by programming the
appropriate fuses) inputs from the MUX outputs of four
adjacent I/O cells, two above and two below. This enables cascading of the MUXes to enable wider (up to
16:1) MUX implementations.
The I/O cell also includes a programmable flow-through
latch or register that can be placed in the input or output
path and bypassed for combinatorial outputs. As shown
in Figure 1, when the input control MUX of the register/
latch selects the “A” path, the register/latch gets its inputs
from the 4:1 MUX and drives the I/O output. When
selecting the “B” path, the register/latch is directly driven
by the I/O input while its output feeds the GRP. The
programmable polarity Clock to the latch or register can
be connected to any I/O in the I/O-CLK/CLKEN set (onequarter of total I/Os) or to one of the dedicated clock input
pins (Yx). The programmable polarity Clock Enable input
to the register can be programmed to connect to any of
the I/O-CLK/CLKEN input pin set or to the global clock
enable inputs (CLKENx). Use of the dedicated clock
inputs gives minimum clock-to-output delays and minimizes delay variation with fanout. Combinatorial output
mode may be implemented by a dedicated architecture
bit and bypass MUX. I/O cell output polarity can be
programmed as active high or active low.
allow adjacent I/O cell outputs to be directly connected
without passing through the global routing pool. The
relationship between the [N+i] adjacent cells and A, B, C
and D inputs will vary depending on where the I/O cell is
located on the physical die. The I/O cells can be grouped
into “normal” and “reflected” I/O cells or I/O “hemi-
spheres.” These are defined as:
DeviceNormal I/O CellsReflected I/O Cells
ispGDX80VA
ispGDX160V/VA
ispGDX240VAB29-B0, A59-A0,
B9-B0, A19-A0,
D19-D10
B19-B0, A39-A0,
D39-D20
D59-D30
B10-B19, C0-C19,
D0-D9
B20-B39, C0-C39,
D0-D19
B30-B59, C0-C59,
D0-D29
Table 2 shows the relationship between adjacent I/O
cells as well as their relationship to direct MUX inputs.
Note that the MUX expansion is circular and that I/O cell
B20, for example, draws on I/Os B19 and B18, as well as
B21 and B22, even though they are in different hemi-
spheres of the physical die. Table 2 shows some typical
cases and all boundary cases. All other cells can be
extrapolated from the pattern shown in the table.
Figure 2. I/O Hemisphere Configuration of
ispGDX160V/VA
I/O cell 0I/O cell 159
A0
D39
D20D19
D0
C39C0
MUX Expander Using Adjacent I/O Cells
The ispGDXV/VA allows adjacent I/O cell MUXes to be
cascaded to form wider input MUXes (up to 16 x 1)
without incurring an additional full Tpd penalty. However,
there are certain dependencies on the locality of the
adjacent MUXes when used along with direct MUX
inputs.
Adjacent I/O Cells
Expansion inputs MUXOUT[n-2], MUXOUT[n-1],
MUXOUT[n+1], and MUXOUT[n+2] are fuse-selectable
for each I/O cell MUX. These expansion inputs share the
same path as the standard A, B, C and D MUX inputs, and
I/O cell index increases in this direction
A39
B0
I/O cell 79I/O cell 80
B19B20
B39
Direct and Expander Input Routing
Table 2 also illustrates the routing of MUX direct inputs
that are accessible when using adjacent I/O cells as
inputs. Take I/O cell D23 as an example, which is also
shown in Figure 3.
4
I/O cell index increases in this direction
Specifications ispGDX160V/VA
Figure 3. Adjacent I/O Cells vs. Direct Input Path for
ispGDX160V/VA, I/O D23
ispGDX160V/VA I/O Cell
I/O Group A
D21 MUX Out
I/O Group B
D22 MUX Out
I/O Group C
D24 MUX Out
I/O Group D
D25 MUX Out
4 x 4
Crossbar
Switch
.m0
.m1
.m2
.m3
S0S1
D23
It can be seen from Figure 3 that if the D21 adjacent I/O
cell is used, the I/O group “A” input is no longer available
as a direct MUX input.
The ispGDXV/VA can implement MUXes up to 16 bits
wide in a single level of logic, but care must be taken
when combining adjacent I/O cell outputs with direct
MUX inputs. Any particular combination of adjacent I/O
cells as MUX inputs will dictate what I/O groups (A, B, C
or D) can be routed to the remaining inputs. By properly
choosing the adjacent I/O cells, all of the MUX inputs can
be utilized.
Special Features
Slew Rate Control
All output buffers contain a programmable slew rate
control that provides software-selectable slew rate op-
tions.
Open Drain Control
All output buffers provide a programmable Open-Drain
option which allows the user to drive system level reset,
interrupt and enable/disable lines directly without the
need for an off-chip Open-Drain or Open-Collector buffer.
Wire-OR logic functions can be performed at the printed
circuit board level.
Pull-up Resistor
All pins have a programmable active pull-up. A typical
resistor value for the pull-up ranges from 50kΩ to 80kΩ.
Output Latch (Bus Hold)
All pins have a programmable circuit that weakly holds
the previously driven state when all drivers connected to
the pin (including the pin's output driver as well as any
other devices connected to the pin by external bus) are
tristated.
Table 2. Adjacent I/O Cells (Mapping of
ispGDX160V/VA)
I/Os supporting either 3.3V or 2.5V output voltage level
options. The ispGDX160VA uses a VCCIO pin to provide
the 2.5V reference voltage when used. The ispGDX160VA
VCCIO pin occupies the same location as VCC on the
ispGDX160V, allowing drop-in replacement. The
ispGDX160VA offers improved performance by reducing
fanout delays and has PCI compatible drive capability.
Only the ispGDX160VA is available in the fastest (3.5ns)
Commercial speed grade and in -5,-7, and -9ns Industrial
grades in all packages.
The ispGDX160VA has a device ID different from the
ispGDX160V requiring that the latest Lattice download
software be used for programming and verification. Al-
though the ispGDX160VA and ispGDX160V are
functionally equivalent, they are not 100% JEDEC com-
patible. All design files must be recompiled targeting the
ispGDX160VA.
5
Applications
Specifications ispGDX160V/VA
The ispGDXV/VA Family architecture has been developed to deliver an in-system programmable signal routing
solution with high speed and high flexibility. The devices
are targeted for three similar but distinct classes of endsystem applications:
Programmable, Random Signal
Interconnect (PRSI)
This class includes PCB-level programmable signal routing and may be used to provide arbitrary signal swapping
between chips. It opens up the possibilities of programmable system hardware. It is characterized by the need
to provide a large number of 1:1 pin connections which
are statically configured, i.e., the pin-to-pin paths do not
need to change dynamically in response to control inputs.
Programmable Data Path (PDP)
This application area includes system data path transceiver, MUX and latch functions. With today’s 32- and
64-bit microprocessor buses, but standard data path glue
components still relegated primarily to eight bits, PCBs
are frequently crammed with a dozen or more data path
glue chips that use valuable real estate. Many of these
applications consist of “on-board” bus and memory interfaces that do not require the very high drive of standard
glue functions but can benefit from higher integration.
Therefore, there is a need for a flexible means to integrate these on-board data path functions in an analogous
way to programmable logic’s solution to control logic
integration. Lattice’s CPLDs make an ideal control logic
complement to the ispGDXV/VA in-system programmable data path devices as shown below.
Figure 4. ispGDXV/VA Complements Lattice CPLDs
Address
Inputs
(from P)
Control
Inputs
(from P)
Data Path
Bus #1
Programmable Switch Replacement (PSR)
Includes solid-state replacement and integration of me-
chanical DIP Switch and jumper functions. Through
in-system programming, pins of the ispGDXV/VA de-
vices can be driven to HIGH or LOW logic levels to
emulate the traditional device outputs. PSR functions do
not require any input pin connections.
These applications actually require somewhat different
silicon features. PRSI functions require that the device
support arbitrary signal routing on-chip between any two
pins with no routing restrictions. The routing connections
are static (determined at programming time) and each
input-to-output path operates independently. As a result,
there is little need for dynamic signal controls (OE,
clocks, etc.). Because the ispGDXV/VA device will inter-
face with control logic outputs from other components
(such as ispLSI or ispMACH) on the board (which fre-
quently change late in the design process as control logic
is finalized), there must be no restrictions on pin-to-pin
signal routing for this type of application.
PDP functions, on the other hand, require the ability to
dynamically switch signal routing (MUXing) as well as
latch and tri-state output signals. As a result, the pro-
grammable interconnect is used to define
routes that are then selected dynamically by control
signals from an external MPU or control logic. These
functions are usually formulated early in the conceptual
design of a product. The data path requirements are
driven by the microprocessor, bus and memory architec-
ture defined for the system. This part of the design is the
earliest portion of the system design frozen, and will not
usually change late in the design because the result
would be total system and PCB redesign. As a result, the
ability to accommodate
arbitrary
any pin-to-any pin rerouting is not a strong requirement as long as the designer
has the ability to define his functions with a reasonable
degree of freedom initially.
possible
signal
ispMACH
System
Clock(s)
ispLSI/
Device
Control
Outputs
Buffers / RegistersState Machines
ispGDXV/VA
Device
Buffers / RegistersDecoders
Data Path
Bus #2
ISP/JTAG
Interface
Configuration
(Switch)
Outputs
As a result, the ispGDXV/VA architecture has been
defined to support PSR and PRSI applications (including
bidirectional paths) with no restrictions, while PDP applications (using dynamic MUXing) are supported with a
minimal number of restrictions as described below. In this
way, speed and cost can be optimized and the devices
can still support the system designer’s needs.
The following diagrams illustrate several ispGDXV/VA
applications.
6
Applications (Continued)
SpecificationsispGDX160V/VA
Figure 5. Address Demultiplex/Data Buffering
XCVR
Control Bus
MUXed Address Data Bus
I/OAI/OB
OEAOEB
Address
Latch
DQ
CLK
Buffered
Data
To Memory/
Peripherals
Address
Figure 6. Data Bus Byte Swapper
XCVR
I/OA
I/OB
OEA OEB
XCVR
I/OA I/OB
OEA OEB
D0-7
XCVR
I/OA I/OB
OEA OEB
XCVR
I/OA I/OB
OEA OEB
Control Bus
D0-7
Data Bus A
D8-15D8-15
Data Bus B
Designing with the ispGDXV/VA
As mentioned earlier, this architecture satisfies the PRSI
class of applications without restrictions: any I/O pin as a
single input or bidirectional can drive any other I/O pin as
output.
For the case of PDP applications, the designer does have
to take into consideration the limitations on pins that can
be used as control (MUX0, MUX1, OE, CLK) or data
(MUXA-D) inputs. The restrictions on control inputs are
not likely to cause any major design issues because the
input possibilities span 25% of the total pins.
The MUXA-D input partitioning requires that designers
consciously assign pinouts so that MUX inputs are in the
appropriate, disjoint groups. For example, since the
MUXA group includes I/O0-39 (160 I/O device), it is not
possible to use I/O0 and I/O9 in the same MUX function.
As previously discussed, data path functions will be
assigned early in the design process and these restrictions are reasonable in order to optimize speed and cost.
User Electronic Signature
The ispGDXV/VA Family includes dedicated User Electronic Signature (UES) E2CMOS storage to allow users
to code design-specific information into the devices to
identify particular manufacturing dates, code revisions,
or the like. The UES information is accessible through
the boundary scan programming port via a specific command. This information can be read even when the
security cell is programmed.
Figure 7. Four-Port Memory Interface
4-to-1
16-Bit MUX
Bidirectional
Port #1
OE1
Port #2
OE2
Bus 4
Bus 3
Bus 2
Bus 1
Note: All OE and SEL lines driven by external arbiter logic (not shown).
Port #3
OE3
Port #4
OE4
Memory
Port
OEM
SEL0
SEL1
To
Memory
Security
The ispGDXV/VA Family includes a security feature that
prevents reading the device program once set. Even
when set, it does not inhibit reading the UES or device ID
code. It can be erased only via a device bulk erase.
7
Specifications ispGDX160VA
Absolute Maximum Ratings
1,2
Supply Voltage Vcc................................. -0.5 to +5.4V
Input Voltage Applied............................... -0.5 to +5.6V
Off-State Output Voltage Applied ............ -0.5 to +5.6V
Storage Temperature................................ -65 to 150°C
Case Temp. with Power Applied .............. -55 to 125°C
Max. Junction Temp. (TJ) with Power Applied ... 150 °C
1. Stresses above those listed under the “Absolute Maximum Ratings” may cause permanent damage to the device. Functional
operation of the device at these or at any other conditions above those indicated in the operational sections of this specification
is not implied (while programming, follow the programming specifications).
2. Compliance with the Thermal Management section of the Lattice Semiconductor Data Book or CD-ROM is a requirement.
ispGDX160VA timings are specified with a GRP load
(fanout) of four I/O cells. The figure below shows the ∆
GRP Delay with increased GRP loads. These deltas
ispGDX160VA Maximum ∆ GRP Delay vs. I/O Cell Fanout
1.6
1.4
1.2
1.0
0.8
0.6
∆ GRP Delay (ns)
0.4
0.2
0.0
0 4 10203040506070
I/O Cell Fanout
apply to any signal path traversing the GRP (MUXA-D,
OE, CLK/CLKEN, MUXsel0-1). Global Clock signals
which do not use the GRP have no fanout delay adder.
13
Specifications ispGDX160VA
Internal Timing Parameters
1
Over Recommended Operating Conditions
PARAMETER #DESCRIPTION
Inputs
t
io
32Input Buffer Delay—0.4—0.9ns
GRP
t
grp
33GRP Delay—1.1—1.1ns
MUX
t
muxd
t
muxexp
t
muxs
t
muxsio
t
muxsg
t
muxselexp
34I/O Cell MUX A/B/C/D Data Delay—1.0—1.5ns
35I/O Cell MUX A/B/C/D Expander Delay—1.5—2.0ns
36I/O Cell Data Select—1.0—1.5ns
37I/O Cell Data Select (I/O Clock)—1.5—3.0ns
38I/O Cell Data Select (Yx Clock)—1.5—2.0ns
39I/O Cell MUX Data Select Expander Delay—1.5—2.0ns
Register
t
iolat
t
iosu
t
ioh
t
ioco
t
ior
t
cesu
t
ceh
40I/O Latch Delay—1.0—1.0ns
41I/O Register Setup Time Before Clock—0.8—2.0ns
42I/O Register Hold Time After Clock—1.7—1.5ns
43I/O Register Clock to Output Delay—1.2—0.5ns
44I/O Reset to Output Delay—1.0—1.5ns
45I/O Clock Enable Setup Time Before Clock—2.3—2.0ns
46I/O Clock Enable Hold Time After Clock—0.2—0.5ns
1. Internal Timing Parameters are not tested and are for reference only .
2. Refer to the Timing Model in this data sheet for further details.
1
-3-5
MIN. MAX. MIN. MAX. UNITS
14
Specifications ispGDX160VA
Internal Timing Parameters
1
Over Recommended Operating Conditions
PARAMETER #DESCRIPTION
Inputs
t
io
32Input Buffer Delay—1.4—1.9ns
GRP
t
grp
33GRP Delay—1.1—1.1ns
MUX
t
muxd
t
muxexp
t
muxs
t
muxsio
t
muxsg
t
muxselexp
34I/O Cell MUX A/B/C/D Data Delay—2.0—2.5ns
35I/O Cell MUX A/B/C/D Expander Delay—2.5—3.0ns
36I/O Cell Data Select—2.0—2.5ns
37I/O Cell Data Select (I/O Clock)—4.5—6.0ns
38I/O Cell Data Select (Yx Clock)—2.5—3.0ns
39I/O Cell MUX Data Select Expander Delay—2.5—3.0ns
Register
t
iolat
t
iosu
t
ioh
t
ioco
t
ior
t
cesu
t
ceh
40I/O Latch Delay—1.0—1.0ns
41I/O Register Setup Time Before Clock—3.2—4.4ns
42I/O Register Hold Time After Clock—2.3—2.6ns
43I/O Register Clock to Output Delay—0.5—0.5ns
44I/O Reset to Output Delay—1.5—1.5ns
45I/O Clock Enable Setup Time Before Clock—2.5—2.0ns
46I/O Clock Enable Hold Time After Clock—1.0—2.0ns
1. Internal Timing Parameters are not tested and are for reference only .
2. Refer to the Timing Model in this data sheet for further details.
1
-7-9
MIN. MAX. MIN. MAX. UNITS
15
Specifications ispGDX160V
Absolute Maximum Ratings
1,2
Supply Voltage Vcc................................. -0.5 to +5.4V
Input Voltage Applied............................... -0.5 to +5.6V
Off-State Output Voltage Applied ............ -0.5 to +5.6V
Storage Temperature................................ -65 to 150°C
Case Temp. with Power Applied .............. -55 to 125°C
Max. Junction Temp. (TJ) with Power Applied ... 150°C
1. Stresses above those listed under the “Absolute Maximum Ratings” may cause permanent damage to the device. Functional
operation of the device at these or at any other conditions above those indicated in the operational sections of this specification
is not implied (while programming, follow the programming specifications).
2. Compliance with the Thermal Management section of the Lattice Semiconductor Data Book or CD-ROM is a requirement.
DC Recommended Operating Conditions
SYMBOL
V
CC
1
V
IL
1
V
IH
1. Typical 100mV of input hysteresis.
Supply Voltage
Input Low Voltage
Input High Voltage
PARAMETER
Commercial
Industrial
TA = 0°C to +70°C
= -40°C to +85°C
T
A
MIN.MAX.UNITS
3.0
3.0
-0.3
2.0
3.6
3.6
0.8
5.25
V
V
V
V
Table 2-0005/gdxv
Capacitance (TA=25oC, f=1.0 MHz)
SYMBOL
C
1
C
2
PARAMETER
Dedicated Clock Capacitance
8I/O Capacitance
10
UNITSTYPICALTEST CONDITIONS
pf
pf
V = 3.3V, V = 2.0V
CC
V = 3.3V, V = 2.0V
CCY
I/O
Erase/Reprogram Specifications
PARAMETERMINIMUMMAXIMUMUNITS
Erase/Reprogram Cycles10,000—Cycles
Table 2 - 0006
16
Switching Test Conditions
+ 3.3V
R
1
R
2
C
L
*
Device
Output
Test
Point
*C
L
includes Test Fixture and Probe Capacitance.
Input Pulse LevelsGND to 3.0V
Input Rise and Fall Time≤ 1.5ns 10% to 90%
Input Timing Reference Levels1.5V
Output Timing Reference Levels1.5V
Output LoadSee figure at right
3-state levels are measured 0.5V from steady-state
active level.
Output Low Voltage
Output High Voltage
Input or I/O Low Leakage Current
Input or I/O High Leakage Current
I/O Active Pull-Up Current
Bus Hold Low Sustaining Current
Bus Hold High Sustaining Current
Bus Hold Low Overdrive Current
Bus Hold High Overdrive Current
Bus Hold Trip Points
Output Short Circuit Current
Quiescent Power Supply Current
Dynamic Power Supply Current
per Input Switching
5
Maximum Continuous I/O Pin Sink
PARAMETER
CONDITION
=24 mA
I
OL
=-12 mA
I
OH
0V ≤ V
V
0V ≤ V
VIN = V
V
0V ≤ V
0V ≤ VIN ≤ V
VCC = 3.3V, V
V
≤ VIL (Max.)
IN
≤ VIN ≤ 5.25V
CC
≤ V
IN
(Max.)
IL
= V
(Min.)
IN
IH
≤ V
IN
= 0.5V, V
IL
IL
CC
CC
= 0.5V, TA = 25˚C
OUT
= V
IH
CC
One input toggling @ 50% duty cycle,
outputs open.
MIN.MAX.TYP.
–
2.4
–
–
–
50
-50
–
–
V
IL
–
–
–
–
Current Through Any GND Pin
1. One output at a time for a maximum duration of one second. V
2. Typical values are at VCC = 3.3V and T
3. I
4. For a typical application with 50% of I/O pins used as inputs, 50% used as outputs or bidirectionals.
degradation. Characterized but not 100% tested.
= 25oC.
A
/ MHz = (0.01 x I/O cell fanout) + 0.04
CC
e.g. An input driving four I/O cells at 40 MHz results in a dynamic ICC of approximately ((0.01 x 4) + 0.04) x 40 = 3.2 mA.
= 0.5V was selected to avoid test problems by tester ground
OUT
5. This parameter limits the total current sinking of I/O pins surrounding the nearest GND pin.
1. All timings measured with one output switching, fast output slew rate setting, except tsl.
#
A
A
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
A
A
A
A
B
C
B
C
–
–
–
–
D
A
Data Prop. Delay from Any I/O pin to Any I/O pin (4:1 MUX)
1
Data Prop. Delay from MUXsel Inputs to Any Output (4:1 MUX)
2
Clock Frequency, Max. Toggle
3
Clock Frequency with External Feedback
4
Input Latch or Register Setup Time Before Y
5
Input Latch or Register Setup Time Before I/O Clock
6
Output Latch or Register Setup Time Before Y
7
Output Latch or Register Setup Time Before I/O Clock
8
Global Clock Enable Setup Time Before Y
9
Global Clock Enable Setup Time Before I/O Clock
10
I/O Clock Enable Setup Time Before Y
11
Input Latch or Register Hold Time (Yx)
12
Input Latch or Register Hold Time (I/O Clock)
13
Output Latch or Register Hold Time (Y
14
Output Latch or Register Hold Time (I/O Clock)
15
Global Clock Enable Hold Time (Y
16
Global Clock Enable Hold Time (I/O Clock)
17
I/O Clock Enable Hold Time (Y
18
Output Latch or Register Clock (from Y
19
Input Latch or Register Clock (from Y
20
Output Latch or Register Clock (from I/O pin) to Output Delay
21
Input Latch or Register Clock (from I/O pin) to Output Delay
22
Input to Output Enable
23
Input to Output Disable
24
Test OE Output Enable
25
Test OE Output Disable
26
Clock Pulse Duration, High
27
Clock Pulse Duration, Low
28
Register Reset Delay from RESET Low
29
Reset Pulse Width
30
Output Delay Adder for Output Timings Using Slow Slew Rate
31
Output Skew (tgco1 Across Chip)
32
DESCRIPTIONPARAMETER
1
( )
tsu3+tgco1
x
x
x
x
)
x
)
x
)
x
) to Output Delay
x
) to Output Delay
x
-5
MIN. MAX.
–
5.0
–
6.5
143
110
10.0
4.0
3.0
4.0
3.0
2.5
1.5
4.5
0.0
1.5
0.0
1.5
0.0
1.5
0.0
–
–
–
–
–
–
–
–
3.5
3.5
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
5.0
8.5
6.0
9.5
6.0
6.0
9.0
9.0
–
–
14.0
–
8.0
0.5
-7
MIN. MAX.
–
7.0
–
9.0
100
80.0
14.0
5.5
4.5
5.5
4.5
3.5
2.5
6.5
0.0
2.5
0.0
2.5
0.0
2.5
0.0
–
–
–
–
–
–
–
–
5.0
5.0
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
7.0
11.0
9.0
13.0
8.5
8.5
12.0
12.0
–
–
18.0
–
12.0
0.5
UNITS
ns
ns
MHz
MHz
ns
ns
ns
ns
ns
ns
ns
ns
ns
ns
ns
ns
ns
ns
ns
ns
ns
ns
ns
ns
ns
ns
ns
ns
ns
ns
ns
ns
18
External Timing Parameters (Continued)
Specifications ispGDX160V
ispGDX160V timings are specified with a GRP load
(fanout) of four I/O cells. The figure below shows the ∆
GRP Delay with increased GRP loads. These deltas
ispGDX160V Maximum ∆ GRP Delay vs. I/O Cell Fanout
10
8
6
4
∆ GRP Delay (ns)
2
0104203040506070
apply to any signal path traversing the GRP (MUXA-D,
OE, CLK/CLKEN, MUXsel0-1). Global Clock signals
which do not use the GRP have no fanout delay adder.
I/O Cell Fanout
19
Specifications ispGDX160V
Internal Timing Parameters
1
Over Recommended Operating Conditions
PARAMETER #DESCRIPTION
Inputs
t
io
32Input Buffer Delay—0.9—1.4ns
GRP
t
grp
33GRP Delay—1.1—1.1ns
MUX
t
muxd
t
muxexp
t
muxs
t
muxsio
t
muxsg
t
muxselexp
34I/O Cell MUX A/B/C/D Data Delay—1.5—2.0ns
35I/O Cell MUX A/B/C/D Expander Delay—2.0—2.5ns
36I/O Cell Data Select—3.0—4.0ns
37I/O Cell Data Select (I/O Clk)—4.5—6.5ns
38I/O Cell Data Select (Yx Clk)—3.5—4.5ns
39I/O Cell MUX Data Select Expander Delay—3.5—4.5ns
Register
t
iolat
t
iosu
t
ioh
t
ioco
t
ior
t
cesu
t
ceh
40I/O Latch Delay—1.0—1.0ns
41I/O Register Setup Time Before Clock—2.0—3.2ns
42I/O Register Hold Time After Clock—1.5—2.3ns
43I/O Register Clock to Output Delay—0.5—0.5ns
44I/O Reset to Output Delay—1.5—1.5ns
45I/O Clock Enable Setup Time Before Clock—2.0—2.5ns
46I/O Clock Enable Hold Time After Clock—0.5—1.0ns
The ispGDX Development System supports ispGDX
design using a simple language syntax and an easy-touse Graphical User Interface (GUI) called Design
Manager. From creation to In-System Programming, the
ispGDX system is an easy-to-use, self-contained design
tool delivered on CD-ROM media.
Features
• Easy-to-use Text Entry System
• ispGDX Design Compiler
- Design Rule Checker
- I/O Connectivity Checker
- Automatic Compiler Function
• Industry Standard JEDEC File for Programming
• Min / Max Timing Report
• Interfaces To Popular Timing Simulators
• User Electronic Signature (UES) Support
• Detailed Log and Report Files For Easy Design Debug
• On-Line Help
• Windows® 3.1x, Windows 95, Windows 98 and Win-
dows NT® Compatible Graphical User Interface
• SUN O/S, Command Line Driven version available
PC Version
With the ispGDX GUI for the PC, command line entry is
not required. The tools run under Microsoft Windows 3.1,
Windows 95, Windows 98 and Windows NT. When the
ispGDX software is invoked, the Design Manager and an
accompanying message window are displayed. The
Design Manager consists of the Menu Bar, Tool Bar,
Status Bar and the work area. The figure below shows
these elements of the ispGDX GUI.
The Menu Bar displays topics related to functions used in
the design process. Access the various drop-down menus
and submenus by using the mouse or “hot” keys. The
menu items available in the ispGDX system are FILE,
EDIT, DEVICE, INVOKE, INTERFACES, VIEW, WINDOW and HELP.
The Tool Bar is a quick and easy way to perform many of
the functions found in the menus with a single click of the
mouse. File, Edit, Undo, Redo, Find, Print Download and
Compiler are just some of the Icons found in the ispGDX
Tool Bar. For instance, the Compiler Icon performs the
same function as the Invoke => Compiler menu commands, including design analysis and rule checking and
the fitting operation.
The Status Bar displays action prompts and the line and
column numbers reflect the location of the cursor within
the message window or the work area.
Workstation Version
The ispGDX software is also available for use under the
Sun O/S 4.1.x or Solaris 2.4 or 2.5. The Sun version of the
ispGDX software is invoked from the command line
under the UNIX operating system. A GUI is not supported
in this environment.
In the UNIX environment, the ispGDX Design File (GDF)
must be created using a text editor. Once the GDF has
been created, invoke the ispGDX workstation software
from the UNIX command line. The following is an example of how to invoke ispGDX software.
Lattice’s ispGDX Development System Interface
Usage:
ispGDX
[-i input_file]
[-of[edif|orcad|viewlogic|verilog|vhdl]]
[-p part name]
[-r par_file]
.M0MUXA Data input to 4:1 MUX
.M1MUXB Data input to 4:1 MUX
MUX0 Selection input to 4:1 MUX
MUX1 Selection input to 4:1 MUX
.M2MUXC Data Input to 4:1 MUX
.M3
.S0
.S1
MUXD Data input to 4:1 MUX
.CLKClock for a register
.CEClock enable for register clock
.AAdjacent MUX output of an I/O cell
.ENLatch enable for a latch signal
.OEOutput enable for 3-state output
or bidirectional signal
ispGDXV Dot Ext
ispGDX Development System (Continued)
SpecificationsispGDX160V/VA
The GDF File
The GDF file is a simple text description of the design
function, device and pin parameters. The file has four
parts: device selection, set and constant statements, a
pin section and a connection section. A sample file looks
like this:
// 32-Bit Data 3 to 1 Mux
DESIGNdatamux;
PART ispGDX160V-7Q208;
PARAM SECURITY ON;
PARAM OPENDRAIN ON;// USE OPEN DRAIN
// OPTION
PARAM PULL HOLD;// USE BUS HOLD
// LATCH OPTION
SET BUS_A[dataA31..dataA0];
SET BUS_B[dataB31..dataB0];
SET BUS_C[dataC31..dataC0];
SET BUS_D[dataD31..dataD0];
This example shows a simple, but complete, 32-bit 3:1
MUX design. Once completed, the compiler takes over.
Powerful Syntax
Lattice’s ispGDX Design System uses simple, but powerful, syntax to easily define a design. The !(bang) operator
controls pin polarity and can be used in both the pin and
connection sections of the design definition. Dot extensions define data inputs, select controls for the 4:1
multiplexor, and control inputs of sequential elements
and tri-state buffers. Dot extensions are .M# (MUX Input),
.S# (MUX Select), and control functions, such as .CLK,
.EN, .OE and .A (shown in adjacent table). Pin Attributes
are assigned in the pin section of the GDF as well.
SLOWSLEW selects the slow slew rate for an output
buffer. The Pull parameter can be used to select the
internal pull-up or bus hold latch. OPEN drain can be
used to select open drain operation. The COMB attribute
distinguishes the structure for bidirectional pins. If COMB
is used, the input register, or latch, of an output buffer will
be applied to bidirectional pins.
Please consult the ispGDX Development System Manual
for full details.
ispGDX GDF File Dot Extensions
INPUT [oe]{B37};
INPUT [clk] {B36};
INPUT [sel1]{B38};
INPUT [sel0]{B39};
BEGIN
BUS_D.m0 = BUS_A;
BUS_D.m1 = BUS_B;
END
BUS_D.m2 = BUS_C;
BUS_D.m3 = VCC;// Default all
BUS_D.s1 = sel1;
BUS_D.s0 = sel0;
BUS_D.oe = oe;
BUS_D.clk = clk;
// outputs to VCC
23
ispGDX Development System (Continued)
SpecificationsispGDX160V/VA
The ispGDX Design System Compiler
After the GDF file is created, the compiler checks the
syntax and provides helpful hints and the location of any
syntax errors. The compiler performs design rule checks,
such as, clock and enable designations, the use of input/
output/BIDI usage, and the proper use of attributes. I/O
connectivity is also checked to ensure polarity, MUX
selection controls, and connections are properly made.
Compilation is completed automatically and report and
programming files are saved.
Reports Generated
When the ispGDX system compiles a design and generates the specified netlists, the following output files are
created:
Report Files:
.logCompiler History
.rptCompiler Report
.mfrMaximum Frequency Timing Report
.tsuSet-up and Hold Timing Report
.tcoClock to Out Timing Report
.tptTiming Report
Third-Party Timing Simulation
The ispGDX Design System will generate simulation
netlists as specified by a user. The simulation netlist
formats available are: EDIF, Verilog (OVI compliant),
VHDL (VITAL compliant), Viewlogic, and OrCAD.
For In-System Programming, Lattice’s ispGDX devices
may be programmed, alone or in a chain with up to 100
other Lattice ISP devices, using Lattice’s ISP Daisy
Chain Download software. This powerful Windows-based
tool can be launched from the Tool Bar or by Invoking the
Download option from the drop down menu within the
ispGDX Design System. ISP Daisy Chain Download
version 7.1 or above supports the ispGDX Family devices.
Simulation File:
.simPost-Route Simulation With LAC Format
Netlists:
.edoEDIF Output
.vloVerilog Output
.ifoOrCAD Output
.vhoVHDL non-VITAL with Maximum Delays Output
.vhnVHDL non-VITAL with Maximum Delays Output
.vtoVHDL VITAL Output
Download:
.jedJEDEC Device Programming File
24
In-System Programmability
Specifications ispGDX160V/VA
All necessary programming of the ispGDXV/VA is done
via four TTL level logic interface signals. These four
signals are fed into the on-chip programming circuitry
where a state machine controls the programming.
On-chip programming can be accomplished using an
IEEE 1149.1 boundary scan protocol. The IEEE 1149.1compliant interface signals are Test Data In (TDI), Test
Data Out (TDO), Test Clock (TCK) and Test Mode Select
(TMS) control. The EPEN pin is also used to enable or
disable the JTAG port.
The embedded controller port enable pin (EPEN) is used
to enable the JTAG tap controller and in that regard has
similar functionality to a TRST pin. When the pin is driven
high, the JTAG TAP controller is enabled. This is also true
Figure 9. ispJTAG Device Programming Interface
TDO
TDI
TMS
TCK
ispJTAG
Programming
Interface
EPEN
when the pin is left unconnected, in which case the pin is
pulled high by the permanent internal pullup. This allows
ISP programming and BSCAN testing to take place as
specified by the Instruction Table.
When the pin is driven low, the JTAG TAP controller is
driven to a reset state asynchronously. It stays there
while the pin is held low. After pulling the pin high the
JTAG controller becomes active. The intent of this feature is to allow the JTAG interface to be directly controlled
by the data bus of an embedded controller (hence the
name Embedded Port Enable). The EPEN signal is used
as a “device select” to prevent spurious programming
and/or testing from occuring due to random bit patterns
on the data bus. Figure 9 illustrates the block diagram for
the ispJTAG interface.
ispGDX
160V/VA
Device
ispLSI
Device
ispMACH
Device
25
ispGDX
160V/VA
Device
ispGDX
160V/VA
Device
Boundary Scan
Specifications ispGDX160V/VA
The ispGDXV/VA devices provide IEEE1149.1a test
capability and ISP programming through a standard
Boundary Scan Test Access Port (TAP) interface.
The boundary scan circuitry on the ispGDXV/VA Family
operates independently of the programmed pattern. This
Figure 10. Boundary Scan Register Circuit for I/O Pins
SCANIN
(from previous
cell
BSCAN
Registers
DQDQ
DQ
BSCAN
Latches
DQ
allows customers using boundary scan test to have full
test capability with only a single BSDL file.
The ispGDXV/VA devices are identified by the 32-bit
JTAG IDCODE register. The device ID assignments are
listed in Table 4.
The ispJTAG programming is accomplished by executing Lattice private instructions under the Boundary Scan
State Machine.
Downlowad (ispDCD™), ispCODE ‘C’ routines or any
third-party programmers. Contact Lattice Technical Support to obtain more detailed programming information.
Details of the programming sequence are transparent to
the user and are handled by Lattice ISP Daisy Chain
Figure 11. Boundary Scan Register Circuit for Input-Only Pins
Input Pin
SCANIN
DQ
(from previous
cell
Shift DR
Clock DR
Figure 12. Boundary Scan State Machine
Test-Logic-Reset
1
0
Run-Test/Idle
0
Select-DR-Scan
1
0
Capture-DR
0
Shift-DR
1
Exit1-DR
0
0
1
SCANOUT
(to next cell)
Select-IR-Scan
1
0
Capture-IR
0
Shift-IR
1
Exit1-IR
0
111
0
1
Pause-DR
0
Exit2-DR
Update-DR
0
Pause-IR
1
Exit2-IR
1
Update-IR
0
0101
0
1
1
27
Specifications ispGDX160V/VA
Boundary Scan (Continued)
Figure 13. Boundary Scan Waveforms and Timing Specifications
TMS
TDI
TCK
TDO
Data to be
captured
Data to be
driven out
T
btch
T
btsu
T
btcl
T
btvo
T
btcsu
Data Captured
T
btuov
T
bth
T
btcp
T
btco
Valid DataValid Data
T
btch
T
btuco
Valid DataValid Data
T
btoz
T
btuoz
SymbolParameterMinMaxUnits
t
btcp
t
btch
t
btcl
t
btsu
t
bth
t
rf
t
btco
t
btoz
t
btvo
t
btcpsu
t
btcph
t
btuco
t
btuoz
t
btuov
TCK [BSCAN test] clock pulse width100–ns
TCK [BSCAN test] pulse width high50–ns
TCK [BSCAN test] pulse width low50–ns
TCK [BSCAN test] setup time20–ns
TCK [BSCAN test] hold time25–ns
TCK [BSCAN test] rise and fall time50–mV/ns
TAP controller falling edge of clock to valid output–25ns
TAP controller falling edge of clock to data output disable–25ns
TAP controller falling edge of clock to data output enable–25ns
BSCAN test Capture register setup time20–ns
BSCAN test Capture register hold time25–ns
BSCAN test Update reg, falling edge of clock to valid output–50ns
BSCAN test Update reg, falling edge of clock to output disable–50ns
BSCAN test Update reg, falling edge of clock to output enable–50ns
28
Specifications ispGDX160V/VA
Signal Descriptions
Signal Name Description
I/OInput/Output Pins – These are the general purpose bidirectional data pins. When used as outputs,
each may be independently latched, registered or tristated. They can also each assume one other
control function (OE, CLK/CLKEN, and MUXsel as described in the text).
TOETest Output Enable Pin – This pin tristates all I/P pins when a logic low is driven.
RESETActive LOW Input Pin – Resets all I/O register outputs when LOW.
Yx/CLKENxInput Pins –These can be either Global Clocks or Clock Enables.
EPENInput Pin – JTAG TAP Controller Enable Pin. When high, JTAG operation is enabled. When low,
JTAG TAP controller is driven to reset.
TDIInput Pin – Serial data input during ISP programming or Boundary Scan mode.
TCKInput Pin – Serial data clock during ISP programming or Boundary Scan mode.
TMSInput Pin – Control input during ISP programming or Boundary Scan mode.
TDOOutput Pin – Serial data output during ISP programming or Boundary Scan mode.
GNDGround (GND)
VCCVcc – Supply voltage (3.3V).
2
VCCIO
1
NC
1. NC pins are not to be connected to any active signals, VCC or GND.
2. “VA” version only.
Input – This pin is used if optional 2.5V output is to be used. Every I/O can independently select either
3.3V or the optional voltage as its output level. If the optional output voltage is not required, this pin
must be connected to the VCC supply. Programmable pull-up resistors and bus-hold latches only draw
VCCIO/VCC
I/O D1
I/O D 0
VCC
I/O C 39
I/O C 38
I/O C 37
I/O C 36
GND
I/O C 35
I/O C 34
I/O C 33
I/O C 32
I/O C 31
I/O C 30
I/O C 29
I/O C 28
GND
I/O C 27
VCC
I/O C 26
I/O C 25
I/O C 24
I/O C 23
I/O C 22
I/O C 21
I/O C 20
GND
I/O C 19
I/O C 18
I/O C 17
I/O C 16
I/O C 15
I/O C 14
I/O C 13
VCC
I/O C 12
GND
I/O C 11
I/O C 10
I/O C 9
I/O C 8
I/O C 7
I/O C 6
I/O C 5
I/O C 4
GND
I/O C 3
I/O C 2
I/O C 1
I/O C 0
VCC
Control
2
—
OE
CLK/CLKEN
—
MUXsel2
MUXsel1
OE
CLK/CLKEN
—
MUXsel2
MUXsel1
OE
CLK/CLKEN
MUXsel2
MUXsel1
OE
CLK/CLKEN
—
MUXsel2
—
MUXsel1
OE
CLK/CLKEN
MUXsel2
MUXsel1
OE
CLK/CLKEN
—
MUXsel2
MUXsel1
OE
CLK/CLKEN
MUXsel2
MUXsel1
OE
—
CLK/CLKEN
—
MUXsel2
MUXsel1
OE
CLK/CLKEN
MUXsel2
MUXsel1
OE
CLK/CLKEN
—
MUXsel2
MUXsel1
OE
CLK/CLKEN
—
GND
Data
I/O B 3
—
MUXsel2
Control
I/O B 4
I/O B 5
I/O B 6
I/O B 7
OE
MUXsel1
MUXsel2
CLK/CLKEN
I/O B 8
I/O B 9
I/O B 10
I/O B 11
OE
MUXsel1
MUXsel2
CLK/CLKEN
VCC
GND
I/O B 12
—
—
CLK/CLKEN
I/O B 13
I/O B 14
OE
MUXsel1
I/O B 15
I/O B 16
I/O B 17
OE
MUXsel2
CLK/CLKEN
NC
1NC1
I/O B 18
I/O B 19
CLK_EN0/Y0
CLK_EN1/Y1
—————————
MUXsel1
MUXsel2
GND
TDO
TMS
TCK
TDI
I/O B 20
I/O B 21
I/O B 22
I/O B 23
OE
MUXsel1
MUXsel2
CLK/CLKEN
VCC
I/O B 24
I/O B 25
I/O B 26
OE
MUXsel1—MUXsel2
CLK/CLKEN
I/O B 27
1. No Connect Pins (NC) are not to be connected to any active signal, Vcc or GND.
*Use ispGDX160VA for new designs.
Note: The ispGDX160VA devices are dual-marked with both Commercial and Industrial grades. The Industrial speed grade is slower,
e.g. ispGDX160VA-3B208-5I.
7
ispGDX160VA-5Q208I
ispGDX160VA-7B208I
ispGDX160VA-9B208I
208-Pin PQFP
208-Ball fpBGA5ispGDX160VA-5B208
272-Ball BGA5ispGDX160VA-5B272
208-Pin PQFP7ispGDX160VA-7Q208
208-Ball fpBGA
272-Ball BGA7ispGDX160VA-7B272
208-Pin PQFP
208-Ball fpBGA5ispGDX160V-5B208
272-Ball BGA5ispGDX160V-5B272
208-Pin PQFP7ispGDX160V-7Q208
208-Ball fpBGA
272-Ball BGA7ispGDX160V-7B272
Table 2-0041A/ispGDXV/A
208-Pin PQFP
208-Ball fpBGA5ispGDX160VA-5B208I
272-Ball BGA5ispGDX160VA-5B272I
208-Pin PQFP7ispGDX160VA-7Q208I
208-Ball fpBGA
272-Ball BGA7ispGDX160VA-7B272I
208-Pin PQFP9ispGDX160VA-9Q208I
208-Ball fpBGA9
272-Ball BGA9ispGDX160VA-9B272I
208-Pin PQFP7ispGDX160V-7Q208I
Table 2-0041C/ispGDXV
37
Loading...
+ hidden pages
You need points to download manuals.
1 point = 1 manual.
You can buy points or you can get point for every manual you upload.