VHDL和FPGA's[英] VHDL and FPGA's

本文是小编为大家收集整理的关于VHDL和FPGA's的处理/解决方法,可以参考本文帮助大家快速定位并解决问题,中文翻译不准确的可切换到English标签页查看源文。

问题描述

我对FPGA SCEEN相对较新,并希望与他们和VHDL获得经验.我不太确定使用标准MCU会产生什么好处,但是由于许多公司正在寻找它,因此寻找经验.

什么是一个不错的平台,并获得不多钱的经验.我一直在寻找,如果不是1000,我能找到的是200-300美元的董事会.我应该在FPGA开发板上寻找什么,我听到高速外围界面,我想我真的很困惑的是,具有50/100 GPIO的MCU开发板可以使用约100个,而同样的功能也可以FPGA板要贵得多!我知道您可以重新编程FPGA,但是MCU也可以.我什至应该摆弄FPGA的市场会继续使用它们吗?还是我们只朝着MCU迈进?

?

推荐答案

嗯...我能够很快找到三个低于$ 100的评估板:

$ 79: http://www. terasic.com.tw/cgi-bin/page/archive.pl?language=English&no=593

$ 79: http://www.arlownac.com/solutions/solutions/bemicro-sdk/

$ 89: http://wwww.xilinx. com/products/boars-and-kits/aes-s6mb-lx9.htm

关于在评估委员会中寻找的内容,这完全取决于您想做什么.如果您有一项特定的设计任务,则需要一个支持尽可能多的功能的板,而I/O和最终电路一样.您可以获得具有各种内存选项(SRAM,DDR2,DDR3,Flash等),以太网,PCI/PCIE总线,高速光学收发器等的董事会.如果您只想开始,几乎任何董事会都会为您工作.实际上,今天出售的任何东西都应该有足够的空间来进行非平凡的示例设计(即:使用软核CPU和设计/选择自己的外围混合物构建自己的微控制器).

即使您的董事会只有几个开关和LED,您也可以开始设计硬件" Hello World"(又称闪烁的LED :),简单的状态机和许多其他应用程序.您从哪里开始以及尝试做的事情应该取决于您的整体目标.如果您只是想获得FPGA的一般经验,我建议:

  • 从任何低成本评估板开始
  • 通过他们的演示应用程序(通常已经被编程到HW),以熟悉它的工作
  • 从源构建演示程序并验证它可以熟悉FPGA工具链
  • 以某种方式修改演示应用程序,以熟悉为FPGAS设计硬件
  • 使用您的新发现的体验来确定下一步尝试什么

至于市场继续使用FPGA,它们绝对可以留在这里,但这并不意味着它们适合每个应用程序. MCU本身对于许多应用程序就可以了,但是无法处理所有应用程序.例如,您可以轻松地使用大多数微型控制器"咬" I2C甚至连续的UART,但是您很难与以太网端口,VGA显示器或PCI/PCIE BUS进行交谈,而没有某些自定义的硬件.由您决定如何混合可用技术(MCUS,FPGA,自定义逻辑内部设计,许可的IP内核,现成的标准硬件芯片等)以创建功能性产品或设备,通常在那里不是任何单一的"正确"答案.

其他推荐答案

FPGA赢得微控制器,如果您需要一些或全部:

  • 大量的数学要完成(甚至超过DSP也有意义)
  • 大量的内存带宽(通常与上几点息息相关 - 如果您没有数据可以执行此操作,那么要做很多数学要做!)
  • 极为可预测的硬实时性能 - 定时分析器将告诉您给定设计逻辑的设备可以计时多快.您可以(具有一定的 - 高 - 统计可能性)"保证"以这种速度运行.因此,您可以设计逻辑,即使这些截止日期位于纳米段领域,您都会始终满足某些实时响应时间.

如果没有,那么您可能会使用微型或DSP.

更好

其他推荐答案

OpenCores 网站是一个很好的资源,尤其是编程工具部分.网站上的文章链接是开始调查FPGA板的好地方.

FPGA比微处理器的最大优势是体系结构.微处理器具有一组固定的功能单元,可以很好地解决大多数问题.我已经看到微处理器的计算效率数字构成6%至15%.在FPGA中,您正在专门为您的问题创建功能单元,因此您可以达到90-100%的计算效率.

至于成本的差异,请考虑数量销售.大量的微处理器销售量与FPGA销售相对较低.

本文地址:https://www.itbaoku.cn/post/2090980.html

问题描述

I'm relatively new to the FPGA sceen and was looking to get experience with them and VHDL. I'm not quite sure what the benefit would be over using a standard MCU but looking for experience since many companies are looking for it.

What would be a good platform to start out on and get experience for not to much money. Ive been looking and all I can find are 200 - 300 dollar boards if not 1000's. What should one look for in an FPGA development board, I hear high speed peripheral interfaces, and what I guess I'm really confused about is that an MCU dev board with around 50/100 GPIO can go for around 100 while that same functionality on an FPGA board is much more expensive! I know you can reprogram an FPGA, but so can an MCU. Should I even fiddle with FPGA's will the market keep using them or are we moving towards MCU's only?

推荐答案

Hmm...I was able to find three evaluation boards under $100 pretty quickly:

$79: http://www.terasic.com.tw/cgi-bin/page/archive.pl?Language=English&No=593

$79: http://www.arrownac.com/solutions/bemicro-sdk/

$89: http://www.xilinx.com/products/boards-and-kits/AES-S6MB-LX9.htm

As to what to look for in an evaluation board, that depends entirely on what you want to do. If you have a specific design task to accomplish, you want a board that supports as many of the same functions and I/O as your final circuit. You can get boards with various memory options (SRAM, DDR2, DDR3, Flash, etc), Ethernet, PCI/PCIe bus, high-speed optical transceivers, and more. If you just want to get started, just about any board will work for you. Virtually anything sold today should have enough space for even non-trivial example designs (ie: build your own microcontroller with a soft-core CPU and design/select-your-own peripheral mix).

Even if your board only has a few switches and LEDs you can get started designing a hardware "Hello World" (a.k.a. the blinking LED :), simple state machines, and many other applications. Where you start and what you try to do should depend on your overall goals. If you're just looking to gain general experience with FPGAs, I suggest:

  • Start with any of low-cost evaluation boards
  • Run through their demo application (typically already programmed into the HW) to get familiar with what it does
  • Build the demo program from source and verify it works to get familiar with the FPGA tool chain
  • Modify the demo application in some way to get familiar with designing hardware for FPGAs
  • Use your new-found experience to determine what to try next

As for the market continuing to use FPGAs, they are definitely here to stay, but that does not mean they are suitable for every application. An MCU by itself is fine for many applications, but cannot handle everything. For example, you can easily "bit-bang" an I2C or even serial UART with most micro-controllers, but you would be hard pressed to talk to an Ethernet port, a VGA display, or a PCI/PCIe bus without some custom hardware. It's up to you to decide how to mix the available technology (MCUs, FPGAs, custom logic designed in-house, licensed IP cores, off-the-shelf standard hardware chips, etc) to create a functional product or device, and there typically isn't any single 'right' answer.

其他推荐答案

FPGAs win over microcontrollers if you need some or all of:

  • Huge amounts of maths to be done (even more than a DSP makes sense for)
  • Huge amounts of memory bandwidth (often goes hand in hand with the previous point - not much point having lots of maths to do if you have no data to do it on!)
  • Extremely predictable hard real-time performance - the timing analyser will tell you how fast you can clock you device given the logic you've designed. You can (with a certain - high - statistical likelihood) "guarantee" to operate at that speed. And therefore you can design logic which you know will always meet certain real-time response times, even if those deadlines are in the nano-second realm.

If not, then you are likely better off with a micro or DSP.

其他推荐答案

The OpenCores web site is an excellent resource, especially the Programming Tools section. The articles link on the site is a good place to start to survey FPGA boards.

The biggest advantage of an FPGA over a microprocessor is architecture. The microprocessor has a fixed set of functional units that solve most problems reasonably well. I've seen computational efficiency figures for microprocessors form 6% to 15%. In an FPGA you are creating functional units specifically for your problem and nothing else, so you can reach 90-100% computational efficiency.

As for the difference in cost, think of volume sales. High volume of microprocessor sales vs. relatively lower FPGA sales.