问题描述
我的程序支持七个小段显示，我对此感到非常兴奋，但是当我向不在现场的人展示该程序时，他们总是说:你能用它做什么?"我永远无法给他们一个简洁的答案.有人可以帮我吗?
I'm super excited about my program powering a little seven-segment display, but when I show it off to people not in the field, they always say "well what can you do with it?" I'm never able to give them a concise answer. Can anyone help me out?
推荐答案
首先:它们不需要具有易失性内存.
First: They don't need to have volatile memory.
实际上，大型厂商(Xilinx，Altera)通常将其配置存储在SRAM中，因此您需要额外的EEPROM/Flash/WhatEver(TM)才能将其存储在外部.
Indeed the big players (Xilinx, Altera) usually have their configuration on-chip in SRAM, so you need additional EEPROM/Flash/WhatEver(TM) to store it outside.
但是还有其他一些，例如Actel是我想到的一个重要参与者，在其FPGA上具有非易失性配置存储(顺便说一句.这还有其他优点，因为SRAM通常不是很耐辐射，并且在进入轨道时必须进行特殊测量).
But there are others, e.g. Actel is one big player that come to mind, that has non-volatile configuration storage on their FPGAs (btw. this has also other advantages, as SRAM is usually not very radiation tolerant, and you have to require special measurements when you go into orbit).
有两点可以证明FPGAS是正确的:
There are two big things that justify FPGAS:
-
价格-它们并不便宜.但是有时您无法在软件中执行某些操作，而您需要硬件.而且当您在所需数量的某个点以下时(例如，因为它只是一个很小的系列或一个原型)，FPGA比ASIC便宜得多.而且，在开发ASIC时，这可以在达到最终状态之前-延长周转时间.
Price - They are not cheap. But sometimes you can't do something in software, and you need hardware for it. And when you are below a certain point in your required volume (e.g. because its just small series, or a prototype) an FPGA is MUCH cheaper than an ASIC. Also, while developing ASICs this allows - before a final state is reached - much higher turn-around times.
重新配置-您可以重新配置FPGA.这是处理器或ASIC无法做到的.您可以在某些应用程序中使用此功能:当您需要在设计中修复某些东西的能力时，却无法实际接触到设备.示例:火星轨道器/漫游器使用Xilinx FPGA.当有人发现一个错误(或想要切换到用于传输数据或其他内容的其他编码)时，您将无法替换这艘船，因为那是无法到达的.但是使用FPGA，您可以重新配置并应用您的更改.另一种情况是，您可以拥有一个芯片，该芯片可以根据情况执行不同的加速.想象一下智能手机，打电话时可以将FPGA配置为进行音频编码/解码，冲浪时可以将其用作压缩引擎，播放视频时可以将其配置为h264解码器/加速器.您可以做的另一件事是，可以将硬件与问题实例匹配.例如.思科在其硬件中使用了许多FPGA.您需要硬件以所需的速度执行切换/路由/数据包检查，并且可以从实际设置匹配引擎直接将其生成到硬件中.
Reconfiguration - You can reconfigure your FPGA. That is something a processor or an ASIC can't do. There are some applications where you can use this: E.g. When you need the ability to fix something in the design, but you can't get physically to the device. Example for this: The mars orbiters/rovers used Xilinx FPGAs. When someone finds there a mistake (or wants to switch to a different coding for transmitting data or whatever), you can't replace the ship, as it is just not reachable. But with an FPGA you can just reconfigure and can apply your changes. Another scenario is, that you can have one single chip which is able to perform different accelerations, depending on the scenario. Imagine a smartphone, when telephoning the FPGA can be configured to make audio en-/decoding, when surfing it can work as a compression engine, when playing videos it can be configured as h264 decoder/accelerator. Another thing you could do is that you can match your hardware to your problem instance. E.g. Cisco uses many FPGAs in their hardware. You need the hardware to perform switching/routing/packet inspection with the required speed, and you can generate from actual setting matching engines directly into hardware.
可能很快就会出现的另一件事(我知道有一家汽车制造商对此有所考虑)，是针对包含许多不同电子设备并具有庞大供应链的设备的.它或多或少是价格和重新配置的结合.拥有10个ASIC的成本要高于拥有10个FPGA的10个FPGA的成本，而这10个FPGA都执行相同的任务，但是拥有10个FPGA的只有一个供应商，并且只需要在服务和供应中保留一种芯片的成本要比拥有10个ASIC的供应商便宜.必须在供应和服务中持有和管理10种不同的芯片.
Another thing which might come up soon (I know some car manufacturer thought about it), is for devices which include a lot of different electronics and have a big supply chain. It's more or less a combination of price and reconfiguration. It's more expensive to have 10 ASICs than 10 FPGAs - where both perform the same task, but it's cheaper to have 10 FPGAs with just one supplier and the need to hold just 1 type of chip at service and supply than to have 10 suppliers with the necessity to hold and manage 10 different chips in supply and service.
这篇关于FPGA的一些实际应用是什么?的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持！