XPS Main Window

XPS Main Window

The Xilinx® Platform Studio (XPS) main window comprises several viewing panels. The numbered sections of the main window are described below.

The Project Information Area (1)

The Project Information Area has three tabs:

    • Project Tab

The Project tab opens the Project Explorer, which lists references to project-related files. This information is grouped together in the following general categories:

    • Project Files: This category includes all project-specific files. These include the Microprocessor Hardware Specification (MHS) files, User Constraints File (UCF) file, iMPACT Command files, Implementation Option file, and BitGen Option files, and software ELF files associated with each processor instance. For more information on these files, refer to XPS Project Files.
    • Project Options: This category includes all project-specific options. The options include Device, Netlist, Implementation, Hardware Description Language (HDL), and Sim Model. Double-click or right-click any entry to open the Project Options dialog box, in which you can change the option assignments.
    • Design Summary: Double-click to open the Design Summary, which provides quick access to various report files. You can also use the Design Summary to filter and sort messages for various stages of design generation.
  • IP Catalog Tab

The IP Catalog tab opens the IP Catalog, which lists all the EDK IP cores, as well as any custom IP cores that you created. Only the IP cores compatible with the target Xilinx® device architecture are displayed. The catalog lists information about the IP cores, including release version, status (PRODUCTION, DISCONTINUED, PRE_PRODUCTION, SUPERSEDED, DEVELOPMENT, BETA, REMOVED), lock (not licensed, locked, or unlocked), processor support and a short description. Additional details about the IP core, including the version change history, data sheet, and Microprocessor Peripheral Description file (MPD), are available in the right-click menu. By default the IP cores are grouped by function, but alternately can be viewed in a flattened list.

The System Assembly View (2)

The System Assembly view displays when an XPS project is open, and it closes when the project is closed. This view allows you to view and edit your hardware platform. Select the Bus Interface, Ports, and Addresses tabs to view the corresponding aspects of your design. The default is Hierarchical view, in which the information of your design is grouped into a tree by the IP core instances in your hardware platform. Refer to the following topics for more information about using these tabs:

You can change the layout of the information using the layout tool bar buttons (5) at the top of the pane.

    • Click the Change to Flat View/Change to Hierarchical View toggle button  to change between flat view and hierarchical view. In the flat view, you can sort the table in alphanumeric order by any column.

Note In Flat mode, IPs without bus interfaces are NOT shown.

  • Click the Collapse All Tree Nodes/Expand All Tree Nodes button /  to expand or collapse all the nodes in the IP instance tree. You can also expand and collapse an individual tree node by clicking on the + or - sign next to it.

Note To tile the System Assembly view with another file open in the main window, use the tile buttons in the toolbar.

The Console Window (3)

The Console Window acts as a console for output, warning, and error messages from XPS and from other tools invoked by XPS. Error, warning, and output messages are separated in tabbed windows. Click the Error and Warning links to open associated answer records. If you right-click or double-click an error that has an associated file name and line number, you can navigate to that file in the editor.

The Connectivity Panel (4)

The Connectivity panel is part of the System Assembly View when the Bus Interface tab is selected. This panel is a graphical representation of the bus connectivity of your hardware platform. Each rectangle represents a bus, and each horizontal line represents the bus interfaces for an IP core. For a shared bus, a vertical line represents the bus connection. On an AXI design, multiple vertical lines within an AXI interconnect are present. Each vertical line represents a master connection within that AXI interconnect, which connects to an existing AXI master bus interface. A connector is displayed at the intersection if a compatible connection can be made among the bus and IP core bus interfaces. The rectangles and connectors are color-coded to show the compatibility. The different shapes of the connections symbolize the mastership of the IP core bus interface. A hollow connector represents a potential connection that you can make, and a filled connector represents a connection made. To make or disconnect a connection, click the connector symbol.

Note You can now view potential connections by selecting Edit > Preferences. Select System Assembly View in the Category panel on the left and select the Show Potential Connections check box. When the check box is unchecked, you can mouse over the Patch Panel and the potential connections are displayed. When the check box is checked, you can see the potential connections in the Patch Panel all the time.

The Filter Pane (6)

You can use the Filter pane to create filters for bus interfaces or ports. The pane changes when you click the view tabs. To add or remove a search type, click to select or deselect the corresponding check box. The System Assembly View automatically updates when you make changes to the Filter pane.

The Filter Pane is collapsable to maximize the viewable area of the System Assembly View.

时间: 2024-10-05 02:34:18

XPS Main Window的相关文章

Get the Handle Of the Main Window in WPF

WinForm中获取窗体句柄用this.Handle就行了.  但WPF中有点麻烦,需要先引用命名空间: 1 using System.Windows.Interop; 然后调用方法: 1 IntPtr Handle = new WindowInteropHelper(this).Handle; 其中this指的是要获取的Window的实例,方法返回后,Handle正是Window的句柄.

【Qt学习笔记】10.主窗口 The Main Window

一.工具栏和菜单 只有主框架窗口(QMainWindow)才能够添加菜单和工具栏 QAction 命令 步骤: 1.添加action (动作编辑器) (在Qt Designer 界面的右下角)) 2.把action拖动到菜单或工具栏里 3.在代码里加上响应处理函数 示例代码: Test10_1a_12_11::Test10_1a_12_11(QWidget *parent) : QMainWindow(parent) { ui.setupUi(this); assert( connect( ui

ZetCode PyQt4 tutorial work with menus, toolbars, a statusbar, and a main application window

!/usr/bin/python -*- coding: utf-8 -*- """ ZetCode PyQt4 tutorial This program creates a statusbar. author: Jan Bodnar website: zetcode.com last edited: September 2011 """ import sys from PyQt4 import QtGui class Example(QtGu

The App Life Cycle & The Main Function

The App Life Cycle Apps are a sophisticated interplay between your custom code and the system frameworks. The system frameworks provide the basic infrastructure that all apps need to run, and you provide the code required to customize that infrastruc

window窗口详解

窗口 在图形化的基于win32的应用程序,窗口是屏幕的矩形区域,应用程序显示输出并接收来自用户的输入,因此,一个图形化基于win32的应用程序的首要任务之一就是创建一个窗口. 窗口与其它窗口共享屏幕,[本事]包括来自其它应用程序的窗口,每次只有一个窗口可以接收来自用户的输入,用户可以使用鼠标.键盘或其它输入设备与此窗口以及拥有该窗口的应用程序进行交互. 关于窗口 这个概述描述了应用程序用来创建和使用窗口的编程单元:管理窗口之间的关系:以及大小.移动.和显示窗口:概述包括以下主题: 桌面窗口  

main Runloop

1.An app’s main run loop processes all user-related events 2.The UIApplication object sets up the main run loop at launch time and uses it to process events and handle updates to view-based interfaces. 3. the main run loop executes on the app’s main

Windows API-----top level window

原文地址: http://blog.163.com/cumt_xl/blog/static/19071504420136911838683/ Q: What is a top-level window? A: A top-level window is a window that is not child, i.e. it has not WS_CHILD style set. Notes unlike the child windows, a top-level window can be d

QT Demo 之 window(2) Splash

在QT Demo 之 window一章我们学习了在C++层的QQuickWindow的一些知识,这一章我们重点看一下源码中的Splash.qml文件,该文件给我们演示了如何使用splash screen来显示应用的启动及界面. 关于应用的启动界面,有一个最直观也是比较常见的例子就是photoshop,下图就是PS启动时显示的界面: 在这个例子里也是先显示一个Qt的Logo,然后再进入到主应用窗口中. 源码结构 Splash.qml实现了一个自定义的window来完成Splash screen的功

Centering window on the screen

The following script shows how we can center a window on the desktop screen. #!/usr/bin/python # -*- coding: utf-8 -*- """ ZetCode PyQt4 tutorial This program centers a window on the screen. author: Jan Bodnar website: zetcode.com last edit