Table of Contents
Advertisement
Figure 12-7
hierarchy, the embedded processor subsystem is created using an EDK project containing
only the blocks illustrated in the EDK tool domain block. This EDK project is not the top
level of the system and is instantiated as a black box subcomponent in a standard ISE
software project as illustrated.
In this example:
•
•
The main advantages of this implementation hierarchy are in terms of possible faster
development turn-around for synthesis/implementation run time. This is as a result that
the EDK components will pre-exist in netlist format and do not have to be re-synthesized
for each design iteration.
A final word of explanation is required for the EDK project illustrated in
assign the AVB software drivers running on the MicroBlaze processor to the Ethernet AVB
Endpoint core, the plb_port pcore was created. This pcore is simply a bunch of wires to
route through all of the PLB signals through to ports of the EDK block top level. In the
Microprocessor Hardware Specification (.mhs) file, this pcore was assigned a base address
matching that of the Ethernet AVB Endpoint
produced by the CORE Generator software). Then the AVB software drivers were assigned
to the plb_port instance in the Microprocessor Software Specification (.mss) file.
Ethernet AVB Endpoint User Guide
UG492 September 21, 2010
shows the implementation using an ISE® software top-level project. In this
The EDK component is synthesized by the EDK tools; this block can then be left alone
(unedited)
All other components (for example, the Custom AV logic) can be created using a
standard ISE software project. This flow should be familiar to a wider range of
engineers than the EDK tool set.
www.xilinx.com
Using the Xilinx LogiCORE IP Tri-Mode Ethernet MACs
"PLB Base Address"
Figure
12-7. To
(in the generated netlist
123
Advertisement
Table of Contents
