EasyManuals Logo

Xilinx ChipScope Pro User Manual

Xilinx ChipScope Pro
226 pages
To Next Page IconTo Next Page
To Next Page IconTo Next Page
To Previous Page IconTo Previous Page
To Previous Page IconTo Previous Page
Page #202 background image
202 www.xilinx.com ChipScope Pro Software and Cores User Guide
UG029 (v14.3) October 16, 2012
Chapter 5: ChipScope Engine Tcl Interface
::chipscope::csevio_undefine_name
Removes a VIO signal/bus name and all associated information.
Syntax
::chipscope::csevio_undefine_name handle [list deviceIndex
userRegNumber coreIndex] name flags
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,
undefine a bus called
control_bus that is assigned to bits of the SYNC_OUTPUT port:
%set coreRef [list 3 2 0]
%set csevio_undefine_name $handle $coreRef “control_bus”
$CSEVIO_SYNC_OUTPUT
Back to list of all CseVIO Tcl Commands
Table 5-68: Arguments for Subcommand ::chipscope::csevio_undefine_name
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 of the signal or bus to be removed.
flags 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

Table of Contents

Questions and Answers:

Question and Answer IconNeed help?

Do you have a question about the Xilinx ChipScope Pro and is the answer not in the manual?

Xilinx ChipScope Pro Specifications

General IconGeneral
BrandXilinx
ModelChipScope Pro
CategoryComputer Hardware
LanguageEnglish

Related product manuals