完善资料让更多小伙伴认识你,还能领取20积分哦, 立即完善>
我是Xilinx和FPGA的新手。
我有一个Spartan3A入门套件。 我的困惑在于ISE Project Navigator和Xilinx Platform Studio。 有什么不同? 我知道:很多!,但我的意思是他们最终都编程了FPGA吗? 平台工作室XPS了解我的入门套件板的所有信息,但ISE并不知道哪个LED连接到我板上的哪个FPGA引脚。 你什么时候使用ISE vs XPS? (我对Microchip PIC和各种IDE有很多经验,但我很无聊,决定看看FPGA的世界是什么。) 任何输入的Thanx。 以上来自于谷歌翻译 以下为原文 I'm brand new to Xilinx and FPGAs. I have a Spartan3A Starter kit. My confusion is over ISE Project Navigator and Xilinx Platform Studio. What's the difference? I know: Alot!, but i mean do they both end up programming the FPGA? The Platform Studio, XPS, knows all about my Starter Kit board, but the ISE doesn't know like what LED is connected to what FPGA pin on my board. When do you use ISE vs XPS? (I have lots experience with Microchip PICs and various IDE's, but I was bored and decided to see what the world of FPGAs holds.) Thanx for any input. |
|
相关推荐
3个回答
|
|
嗨,
XPS是使用预定义块(处理器和I / O)进行SOC开发的高级工具。 它了解您的电路板,因为它带有电路板支持包,其中包含有关电路板的所有相关信息。 ISE Projct navigator是用于HDL综合和FPGA Place& Route的IDE。 由于单个FPGA不直接依赖于外部硬件,因此不需要BSP。 仍然需要定义I / O-Pin分配。 这是笏UCF文件是好的。 您可以在文档中找到适用于您的电路板的通用UCF文件,但您可以根据自己的需要自由调整它们。 此外,您不必使用预定义的宏。 您可以使用支持的HDL编写自己的硬件描述。 为了使芯片工作,XPS通过脚本控制ISE工具链以执行合成和P& R. 所以,没有ISE XPS几乎是无用的。 有一个很好的综合 Eilert 以上来自于谷歌翻译 以下为原文 Hi, XPS is a high level tool for SOC-development with predefined blocks (Processor and I/O). It knows about your board, because it comes with a Board Support Package, where all relevant information about your board is predefined. ISE Projct navigator is a IDE for HDL synthesis and FPGA Place&Route. Since a single FPGA is not directly depending on external hardware there is no BSP necessary. Still the I/O-Pin assignment needs to be defined. That's wat UCF Files are good for. You will find a generic UCF file for your board in the documentation, but you are free to adapt them to your needs. Also you are not bound to use predefined macros. You can write your own hardware descriptions withthe supported HDLs. To make a chip work XPS controls the ISE Toolchain via scripts to perform synthesis and P&R. So, without ISE XPS is almost useless. Have a nice synthesis Eilert |
|
|
|
XPS和ISE之间存在重叠,但这是我如何看待它们并使用它们......
使用XPS与MicroBlaze及其外设一起工作......如UART,SPI,外部存储器接口,定时器/计数器等.XPS管理这些外设(IP内核)的参数设置,它们如何连接在一起以及它们如何连接 对外界。 这些内核中的大多数都是Xilinx或第三方内核,但有些内核可能是您自己的定制IP内核,用VHDL或Verilog编写。 XPS使用ISE来合成,放置和放大 路由这些IP核。 这就是为什么必须安装ISE才能使XPS正常工作。 您可以将XPS视为ISE的包装,可以帮助您避免使用 不得不处理令人难以置信的海洋之间的互联互通 核心和核心参数。此外,MicroBlaze许可证与XPS绑定,因此您需要它与基于MicroBlaze的项目一起使用。 使用ISE与您自己的自定义IP核一起工作.....编辑代码,创建和运行测试平台,并进行试验合成,换句话说,使用ISE测试和调试各个自定义IP核。 一旦您满意自定义IP核,您可以退出ISE并使用XPS构建整个项目。 如果FPGA项目只是您自己的代码,没有MicroBlaze,那么您不需要XPS ...仅使用ISE。 顺便说一下,我应该建议可以使用ISE来管理XPS 项目,但这对我来说似乎是颠倒的,我没有这样做 避免混淆自己! 吉姆 以上来自于谷歌翻译 以下为原文 There is overlap between XPS and ISE, but here is how I think of them and use them ... Use XPS to work with the MicroBlaze and its peripherals ... like UART, SPI, external memory interface, timer/counter, etc. XPS manages the parameter settings of these peripherals (IP cores), how they connects together, and how they connect to the outside world. Most of these cores will be Xilinx or 3rd party cores, but some may be your own custom IP cores, written in VHDL or Verilog. XPS uses ISE to synthesise, place & route these IP cores. That is why ISE must be installed for XPS to work. You could think of XPS as a wrapper around ISE that saves you fromhaving to deal with a mind boggling sea of interconnects betweencores, and core params. Also the MicroBlaze license is tied to XPS so you need it to work with MicroBlaze based projects. Use ISE to work with your own custom IP cores ..... to edit code, create and run test benches, and do trial synthesis, in other words, use ISE to test and debug individual custom IP cores. Once you are happy a custom IP core works, you can exit ISE and use XPS to build the whole project. If an FPGA project is just your own code, with no MicroBlaze, then you do not need XPS ... use ISE only. As an aside, I should menton it is possible to use ISE to manage an XPSproject, but this seems upside-down to me, and I have not done this toavoid confusing myself ! Jim |
|
|
|
感谢大家的投入。
使用ISE,我能够编写一个简单的Verilog程序,下载并运行它。 很难向妻子解释让LED闪烁的快感! 我对Xilinx有关许可证的问题。 我以225美元的价格从Digikey购买了Spartan3A StarterKit,在我获得在线许可后,在建设项目期间,我说我有60天的评估许可证。 此外,从XPS,我无法运行XPS SDK。 我想用C ++作为语言。 我怎么做? (如果有帮助的话,我有WindRiver'sworkbenck 3和VxWorks 6.3。我从FIRST机器人俱乐部获得它们,因为这是FIRSTuses编程他们的NI cRIO机器人控制器。) 如果我从“开始”菜单运行SDK,它会对许可证进行限制。 我想我会打电话给Xilinx。 Thanx再次获取信息。 以上来自于谷歌翻译 以下为原文 Thanks for everyones input. Using ISE, I'm able to write a simple Verilog program, download and run it. Tough to explain to the wife what a thrill it is to make a LED blink! I have a question for Xilinx about the license. I bought the Spartan3A StarterKit from Digikey for $225, and after I got the license online, during building a project, it says I have a 60 day evaluation license. Also, from XPS, I can't get XPS SDK to run. I want to use C++ as the language. How do I do that? ( If it helps, I have WindRiver'sworkbenck 3 and VxWorks 6.3. I got them from our FIRST robotics club, cause that's what FIRSTuses to program their National Instruments cRIO robotic controller.) If I run the SDK from the START menu, it barfs over the license. I think I'll call Xilinx. Thanx again for the info. |
|
|
|
只有小组成员才能发言,加入小组>>
2416 浏览 7 评论
2821 浏览 4 评论
Spartan 3-AN时钟和VHDL让ISE合成时出现错误该怎么办?
2292 浏览 9 评论
3372 浏览 0 评论
如何在RTL或xilinx spartan fpga的约束文件中插入1.56ns延迟缓冲区?
2459 浏览 15 评论
有输入,但是LVDS_25的FPGA内部接收不到数据,为什么?
1146浏览 1评论
请问vc707的电源线是如何连接的,我这边可能出现了缺失元件的情况导致无法供电
582浏览 1评论
求一块XILINX开发板KC705,VC707,KC105和KCU1500
448浏览 1评论
2003浏览 0评论
727浏览 0评论
小黑屋| 手机版| Archiver| 电子发烧友 ( 湘ICP备2023018690号 )
GMT+8, 2024-12-22 18:04 , Processed in 1.361961 second(s), Total 48, Slave 41 queries .
Powered by 电子发烧友网
© 2015 bbs.elecfans.com
关注我们的微信
下载发烧友APP
电子发烧友观察
版权所有 © 湖南华秋数字科技有限公司
电子发烧友 (电路图) 湘公网安备 43011202000918 号 电信与信息服务业务经营许可证:合字B2-20210191 工商网监 湘ICP备2023018690号