欢迎访问ic37.com |
会员登录 免费注册
发布采购

ISPGDX160-7Q208 参数 Datasheet PDF下载

ISPGDX160-7Q208图片预览
型号: ISPGDX160-7Q208
PDF下载: 下载PDF文件 查看货源
内容描述: 在系统可编程通用数字CrosspointTM [In-System Programmable Generic Digital CrosspointTM]
分类和应用:
文件页数/大小: 25 页 / 326 K
品牌: LATTICE [ LATTICE SEMICONDUCTOR ]
 浏览型号ISPGDX160-7Q208的Datasheet PDF文件第1页浏览型号ISPGDX160-7Q208的Datasheet PDF文件第2页浏览型号ISPGDX160-7Q208的Datasheet PDF文件第3页浏览型号ISPGDX160-7Q208的Datasheet PDF文件第4页浏览型号ISPGDX160-7Q208的Datasheet PDF文件第6页浏览型号ISPGDX160-7Q208的Datasheet PDF文件第7页浏览型号ISPGDX160-7Q208的Datasheet PDF文件第8页浏览型号ISPGDX160-7Q208的Datasheet PDF文件第9页  
Specifications ispGDX Family  
Applications (Cont.)  
Figure 3. Address Demultiplex/Data Buffering  
Designing with the ispGDX  
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.  
XCVR  
I/OA I/OB  
Buffered  
Data  
OEA OEB  
ForthecaseofPDPapplications, thedesignerdoeshave  
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.  
To Memory/  
Peripherals  
Address  
Latch  
Address  
D
Q
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-19 (80 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 restric-  
tions are reasonable in order to optimize speed and cost.  
CLK  
Figure 4. Data Bus Byte Swapper  
XCVR  
D0-7  
D0-7  
I/OA I/OB  
XCVR  
User Electronic Signature  
OEA OEB  
I/OA I/OB  
The ispGDX Family includes dedicated User Electronic  
Signature (UES) E CMOS storage to allow users to code  
OEA OEB  
2
XCVR  
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 or Lattice ISP programming port via a  
specific command. This information can be read even  
when the security cell is programmed.  
D8-15  
D8-15  
I/OA I/OB  
XCVR  
OEA OEB  
I/OA I/OB  
OEA OEB  
Security Bit  
The ispGDX Family includes a security bit 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.  
Figure 5. Four-Port Memory Interface  
4-to-1  
16-Bit MUX  
Bidirectional  
Port #1  
Memory  
To  
Memory  
OE1  
Port  
Port #2  
OE2  
OEM  
Port #3  
OE3  
SEL0  
SEL1  
Port #4  
OE4  
Note: All OE and SEL lines driven by external arbiter logic (not shown).  
5