⭐ 欢迎来到虫虫下载站! | 📦 资源下载 📁 资源专辑 ℹ️ 关于我们
⭐ 虫虫下载站

📄 ch04.5.htm

📁 介绍asci设计的一本书
💻 HTM
字号:
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML EXPERIMENTAL 970324//EN">

<HTML>

<HEAD>

<META NAME="GENERATOR" CONTENT="Adobe FrameMaker 5.5/HTML Export Filter">



<TITLE> 4.5&nbsp;Specifications</TITLE></HEAD><!--#include file="top.html"--><!--#include file="header.html"-->



<DIV>

<P>[&nbsp;<A HREF="CH04.htm">Chapter&nbsp;start</A>&nbsp;]&nbsp;[&nbsp;<A HREF="CH04.4.htm">Previous&nbsp;page</A>&nbsp;]&nbsp;[&nbsp;<A HREF="CH04.6.htm">Next&nbsp;page</A>&nbsp;]</P><!--#include file="AmazonAsic.html"--><HR></DIV>

<H1 CLASS="Heading1">

<A NAME="pgfId=20658">

 </A>

4.5&nbsp;<A NAME="36178">

 </A>

Specifications</H1>

<P CLASS="BodyAfterHead">

<A NAME="pgfId=20659">

 </A>

All FPGA manufactures are continually improving their products to increase performance and reduce price. Often this means changing the design of an FPGA or moving a part from one process generation to the next without changing the part number (and often without changing the specifications). </P>

<P CLASS="Body">

<A NAME="pgfId=24725">

 </A>

FPGA companies usually explain their part history in their data books.<A HREF="#pgfId=20662" CLASS="footnote">

1</A>

 The following history of Actel FPGA ACT&nbsp;1 part numbers illustrates changes typical throughout the IC industry as products develop and mature:</P>

<UL>

<LI CLASS="BulletFirst">

<A NAME="pgfId=20665">

 </A>

The Actel ACT&nbsp;1 A1010/A1020 used a 2 <SPAN CLASS="Symbol">

m</SPAN>

m process. </LI>

<LI CLASS="BulletList">

<A NAME="pgfId=20666">

 </A>

The Actel A1010A/A1020A used a 1.2 <SPAN CLASS="Symbol">

m</SPAN>

m process.</LI>

<LI CLASS="BulletList">

<A NAME="pgfId=20667">

 </A>

The Actel A1020B was a die revision (including a shrink to a 1.0 <SPAN CLASS="Symbol">

m</SPAN>

m process). At this time the A1020, A1020A, and A1020B all had different speeds.</LI>

<LI CLASS="BulletList">

<A NAME="pgfId=20668">

 </A>

Actel graded parts into three speed bins as they phased in new processes, dropping the distinction between the different die suffixes. </LI>

<LI CLASS="BulletLast">

<A NAME="pgfId=20672">

 </A>

At the same time as the transition to die rev. 'B', Actel began specifying timing at worst-case commercial conditions rather than at typical conditions.</LI>

</UL>

<P CLASS="Body">

<A NAME="pgfId=24727">

 </A>

From this history we can see that it is often possible to have parts from the same family that use different circuit designs, processes, and die sizes, are manufactured in different locations, and operate at very different speeds. FPGA companies ensure that their products always meet the current published worst-case specifications, but there is no guarantee that the average performance follows the typical specifications, and there are usually no best-case specifications.</P>

<P CLASS="Body">

<A NAME="pgfId=20678">

 </A>

There are also situations in which two parts with identical part numbers can have different performance&#8212;when different ASIC foundries produce the same parts. Since FPGA companies are fabless, second sourcing is very common. For example, TI began making the TPC1010A/1020A to be equivalent to the original Actel ACT&nbsp;1 parts produced elsewhere. The TI timing information for the TPC1010A/1020A was the same as the 2 <SPAN CLASS="Symbol">

m</SPAN>

m Actel specifications, but TI used a faster 1.2 <SPAN CLASS="Symbol">

m</SPAN>

m process. This meant that &#8220;equivalent&#8221; parts with the same part numbers were <SPAN CLASS="Emphasis">

much</SPAN>

 faster than a designer expected. Often this type of information can only be obtained by large customers in the form of a <SPAN CLASS="Definition">

qualification kit</SPAN>

<A NAME="marker=24810">

 </A>

 from FPGA vendors.</P>

<P CLASS="Body">

<A NAME="pgfId=24691">

 </A>

A similar situation arises when the FPGA manufacturer adjusts its product mix by selling fast parts under a slower part number in a procedure known as <A NAME="marker=20682">

 </A>

<SPAN CLASS="Definition">

down-binning</SPAN>

<A NAME="marker=24047">

 </A>

. This is not a problem for synchronous designs that always work when parts are faster than expected, but is another reason to avoid asynchronous designs that may not always work when parts are much faster than expected. </P>

<HR>

<DIV CLASS="footnotes">

<DIV CLASS="footnote">

<P CLASS="Footnote2">

<SPAN CLASS="footnoteNumber">

1.</SPAN>

<A NAME="pgfId=20662">

 </A>

See, for example, p.1-8 of the Xilinx 1994 data book.</P>

</DIV>

</DIV>

<HR><P>[&nbsp;<A HREF="CH04.htm">Chapter&nbsp;start</A>&nbsp;]&nbsp;[&nbsp;<A HREF="CH04.4.htm">Previous&nbsp;page</A>&nbsp;]&nbsp;[&nbsp;<A HREF="CH04.6.htm">Next&nbsp;page</A>&nbsp;]</P></BODY>



<!--#include file="Copyright.html"--><!--#include file="footer.html"-->

⌨️ 快捷键说明

复制代码 Ctrl + C
搜索代码 Ctrl + F
全屏模式 F11
切换主题 Ctrl + Shift + D
显示快捷键 ?
增大字号 Ctrl + =
减小字号 Ctrl + -