Table of Contents
Advertisement
component-name_sdk.xml - Hardware description of the specific component,
°
imported into SDK.
component-name.bmm - The BMM file of the specific component, which defines
°
the configuration of the block RAMs used by the component. This file is necessary
to update the bitstream with the software to be executed by MicroBlaze.
microblaze_mcs_setup.tcl - A script that is available to automate certain
°
steps in the flow.
mb_bootloop_le.elf - An infinite loop, which is the default program used to
°
update the bitstream.
The full hierarchical name of the component in the design as well as the input clock
Note:
frequency must be decided in this step, and adhered to when the component is later
instantiated.
•
Create Merged BMM: This step is optional, and is only required when the project
contains more than one MicroBlaze MCS core.
The step can be performed by executing the script microblaze_mcs_setup.tcl in
the tool Tcl Console. The script creates a merged BMM file, called
microblaze_mcs_merged.bmm, which includes all MicroBlaze MCS components in
the project.
To perform the step manually, find all the MicroBlaze MCS core BMM files in the project,
and merge them using a text editor. The contents of the files can be concatenated in any
order, except that the id number at the end of each ADDRESS_MAP line (100 in the input
files) must be changed to a unique number for each ADDRESS MAP line. It is suggested
that you use the numbers 100, 200, ...
•
Update Tool to Use BMM: This step informs the tool about the BMM file to use, either
the component BMM file, component-name.bmm, or he merged file from the previous
step when the project contains more than one MicroBlaze MCS core.
The step is also performed by executing the script microblaze_mcs_setup.tcl in
the tool Tcl Console. Project properties are updated to use the appropriate BMM file, by
adding a command line option to the ngdbuild command.
To perform the step manually, see the specific commands for PlanAhead or ISE Project
Navigator below.
•
Implement Project: This is the normal step to create the implemented netlist.
•
Update Tool to Use Software: This step informs the tool about the software
executable files to use, one for each MicroBlaze MCS component in the project. After
this step, whenever the bitstream is generated, it is updated with the contents of the
software executable files.
The step can be performed by invoking the microblaze_mcs_data2mem Tcl
procedure, with one argument for each MicroBlaze MCS component in the project,
MicroBlaze Micro Controller System v1.3
PG048 December 18, 2012
Chapter 6: Customizing and Generating the Core
www.xilinx.com
45
Advertisement
Table of Contents
