ChipScope Pro Software and Cores User Guide
201
UG029 (v14.3) October 16, 2012
CseVIO Tcl Commands
::chipscope::csevio_define_bus
Defines a name for a grouping of VIO signal bits (called a “
bus
”). Requires that
csevio_init_core
be called first.
Syntax
::chipscope::csevio_define_bus handle [list deviceIndex userRegNumber
coreIndex] name flags bitIndexArray arrayLen
Arguments
Returns
An exception is thrown if the command fails.
Example
For the VIO core connected to ICON core inside fourth device on second
USER
register,
define a bus called “
control_bus
” that is assigned to bits 3:0 of the
SYNC_OUTPUT
port:
%set coreRef [list 3 2 0]
%set csevio_define_bus $handle $coreRef “control_bus”
$CSEVIO_SYNC_OUTPUT [list 0 1 2 3]
Back to list of all CseVIO Tcl Commands
Table 5-67:
Arguments for Subcommand ::chipscope::csevio_define_bus
Argument
Type
Description
handle
Required
Handle to the session that is returned by
::chipscope::csejtag_session create
[list
deviceIndex
userRegNumber
coreIndex]
A list containing three elements:
•
Device index (0 to
n
-1) in the
n
-length JTAG chain
•
BSCAN block
USER
register number (starting with 1)
•
Index for core unit. First core unit connected to ICON
has index 0.
name
Name to be given to the bus. All input bus names must
be unique with respect to other input buses. All output
bus names must be unique with respect to other output
buses.
flags
Flags used to determine the port type to which the bus
belongs. Possible flag values include:
•
$CSEVIO_SYNC_OUTPUT
•
$CSEVIO_SYNC_INPUT
•
$CSEVIO_ASYNC_OUTPUT
•
$CSEVIO_ASYNC_INPUT
[list
bitIndicies...]
List containing the bit indices of the signals in the bus.
Left-most element in the list is the LSB.
