Xilinx ChipScope Pro User Manual page 202

Chapter 5: ChipScope Engine Tcl Interface
::chipscope::csevio_undefine_name
Removes a VIO signal/bus name and all associated information.
Syntax
Arguments
Table 5-68: Arguments for Subcommand ::chipscope::csevio_undefine_name
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,
undefine a bus called control_bus that is assigned to bits of the SYNC_OUTPUT port:
Back to list of all CseVIO Tcl Commands
202
::chipscope::csevio_undefine_name handle [list deviceIndex
userRegNumber coreIndex] name flags
Argument Type
handle
[list
deviceIndex
userRegNumber
coreIndex]
Required
name
flags
%set coreRef [list 3 2 0]
%set csevio_undefine_name $handle $coreRef "control_bus"
$CSEVIO_SYNC_OUTPUT
www.xilinx.com
Description
Handle to the session that is returned by
::chipscope::csejtag_session create
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 of the signal or bus to be removed.
Flags used to determine the port type to which the signal
or bus belongs. Possible flag values include:
• $CSEVIO_SYNC_OUTPUT
• $CSEVIO_SYNC_INPUT
• $CSEVIO_ASYNC_OUTPUT
• $CSEVIO_ASYNC_INPUT
ChipScope Pro Software and Cores User Guide
UG029 (v14.3) October 16, 2012