Table of Contents
Advertisement
•
Import Hardware Description: This step is performed in SDK, using the hardware
description file component-name_sdk.xml created when the MicroBlaze MCS
component was generated. If there are more than one component in the project, a
hardware platform specification must be imported for each component.
•
Import Hardware Implementation: This step is performed in SDK, using the
toplevel.bit bitstream and the component-name_bd.bmm or
microblaze_mcs_merged_bd.bmm BMM file.
•
Download and Run or Debug Software: When the FPGA has been programmed,
software can be run or debugged as usual in SDK.
PlanAhead
The PlanAhead commands to achieve the MicroBlaze MCS specific steps above are detailed
here.
Using the script provided to perform the steps:
•
Create Merged BMM and Update Tool to Use BMM:
In the Tcl Console type the following commands:
cd project-path
source project-name.srcs/sources_1/ip/component-name/microblaze_mcs_setup.tcl
•
Update Tool to Use Software, Update Bitstream with Software and Generate
Simulation Files:
Type the following command in the Tcl Console, to perform this with one MicroBlaze
MCS component:
microblaze_mcs_data2mem /sdk-workspace-path/sdk-program/Debug/sdk-program.elf
For each additional MicroBlaze MCS component, add an additional executable ELF file
to the command line.
Performing the steps manually:
•
Update Tool to Use BMM:
With one MicroBlaze MCS component, type the following command in the Tcl Console,
using the appropriate absolute directory path:
config_run [current_run] -program ngdbuild -option {More Options} -value \
{-bm /project-path/project-name.srcs/sources_1/ip/component-name/
component-name_bd.bmm}
With more than one MicroBlaze MCS component, the -bm option must indicate the
merged BMM file instead.
MicroBlaze Micro Controller System v1.3
PG048 December 18, 2012
Chapter 6: Customizing and Generating the Core
www.xilinx.com
47
Advertisement
Table of Contents
