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