Glossary

uPCore Transaction Model Input File (.mbus_in)


An ASCII text file (with the extension .mbus_in) for use in simulating an embedded processor core in an ARM®-based Excalibur device, created by the exc_bus_translate utility. This file describes the bus transactions between the embedded processor core and the remainder of the device over the Stripe-to-PLD Bridge via the Stripe Master-Port. The Simulator uses the uPCore Transaction Model Input File data to simulate the interactions between the embedded processor core and the PLD.

To create an uPCore Transaction Model Input File, you must first create a Master Port High-Level Command File (.dat) that describes the read, write, wrapping, and incremental burst options, as well as busy and idle transactions and periods of idleness that are initiated by the embedded processor core and directed to the PLD, and then use the exc_bus_translate utility to generate the uPCore Transaction Model Input File.

The uPCore Transaction Model Input File for an embedded processor must have the same root name as the uPCore Transaction Model Slave Configuration File (.cfg.sbus_in) and uPCore Transaction Model Slave Input Files (.sbus_in) for the project, and must be located in the project directory. You can specify the root name of these files in the in the uPCore Transaction Model File Name box, which is available from the Options page of the Settings dialog box (Assignments menu).

- PLDWorld -

 

Created by chm2web html help conversion utility.