MATLAB DESIGN HDL CODER RELEASE NOTES User's Guide Page 148

  • Download
  • Add to my manuals
  • Print
  • Page
    / 410
  • Table of contents
  • TROUBLESHOOTING
  • BOOKMARKS
  • Rated. / 5. Based on customer reviews
Page view 147
148 www.xilinx.com System Generator for DSP User Guide
UG640 (v 12.2) July 23, 2010
Chapter 2: Hardware/Software Co-Design
Co-Simulation block, these ports will still connect to the pads on the FPGA and will not
appear as ports on the Hardware Co-Simulation block. Similarly, the bitstream flow
constraints specified on top-level ports in the imported XPS system will be honored.
Should there be top-level ports that do not connect to pads, or are not constrained, these
ports can be made visible in System Generator by exposing the ports using the Processor
Port Interface table in the Advanced tab of the EDK Processor block. See the topic Exposing
Processor Ports to System Generator for details.
You may use the EDK's XPS tool to write and compile your software. However before
simulation can begin, the Compile and update bitstream button in the co-simulation
block's Software tab must be used to put the compiled C-code into the bitstream.
When used in conjunction with a hardware-board supported by network-based hardware
co-simulation, it is possible to free up the JTAG port on the FPGA and use that for software
debug with XMD.
The Software Driver
For both the EDK pcore generation mode and the HDL netlist mode, the EDK Processor
block automatically generates a custom software driver, which can be used to drive the
memory map which is automatically generated by the block.
Location of the Software Driver
In the EDK pcore generation mode, the software driver is located at pathname
<pcores>/<sysgen_pcore_dir>/src.<sysgen_pcore_dir> which is the directory
where System Generator places the exported pcore. Normally, this is under the netlist
directory specified by the System Generator token.
In the HDL netlist mode, when the XPS project is imported into System Generator, the
software driver is placed at
<xps_project_dir>/pcores/sg_plbiface_v1_00_a/src,
where
<xps_project_dir> is the location of the imported XPS project. After going
through the HDL netlist, NGC netlist, Bitstream, or other hardware co-simulation
compilation flows as provided by the System Generator token, the software driver and the
associated API documentation are placed under the directory
<netlist_dir>/SDK_Export/sysgen_repos/drivers/sg_plbiface_v1_00_a/src
along with other SDK export files. By doing so, the generated software driver can be used
in the Xilinx SDK (Software Development Kit).
Launching Xilinx SDK from System Generator
In the HDL netlist mode, the EDK Processor automatically invokes the Export to SDK
utility provided by XPS (Xilinx Platform Studio) to export the imported XPS project to
<netlist_dir>/SDK_Export. For the Bitstream compilation flow, this directory also
contains the bit file and the back-annotation BMM file generated from the compilation
flow. Thus, for the Bitstream compilation flow, the
SDK_Export directory is the only
directory required to be handed off to a software developer for software development.
Page view 147
1 2 ... 143 144 145 146 147 148 149 150 151 152 153 ... 409 410

Comments to this Manuals

No comments