-- Bogus BSDL File
--
-- Updated: August 17, 2000
--
--**************************************************************************
-- Generic BSDL file
-- Copyright Xilinx Corporation 1997
-- Xilinx assumes no liability, either expressed or implied,
-- in the use of this BSDL file.
-- For technical support, contact Xilinx at
--
-- http://support.xilinx.com
--
-- or as follow:
-- North America 1-800-255-7778 hotline@xilinx.com
-- United Kingdom (44) 1932 820821 ukhelp@xilinx.com
-- France (33) 1 3463 0100 frhelp@xilinx.com
-- Germany (49) 89 991 54930 dlhelp@xilinx.com
-- Japan (81) 3-3297-9163 jhotline@xilinx.com
--**************************************************************************
entity nothing_at_all is
--**************************************************************************
-- IMPORTANT - If you are using multiple copies of this
-- file in a single boundary-scan chain, you must make
-- certain that the entity name specified in each generic
-- BSDL file (in this file "nothing_at_all") is unique.
-- Note that the entity name occurs nine (9) times in
-- this file (not including once in this comment).
--**************************************************************************
generic(PHYSICAL_PIN_MAP : string:= "X_PACKAGE");
port ( TCK : in bit; TDI : in bit; TDO : out bit; TMS : in bit );
use STD_1149_1_1990.all;
attribute PIN_MAP of nothing_at_all :
entity is PHYSICAL_PIN_MAP;
constant X_PACKAGE:PIN_MAP_STRING := "TCK : 1,"& "TDI : 2,"& "TDO : 3,"& "TMS : 4";
attribute Tap_Scan_In of TDI : signal is true;
attribute Tap_Scan_Mode of TMS : signal is true;
attribute Tap_Scan_Out of TDO : signal is true;
attribute Tap_Scan_Clock of TCK : signal is (1.0e6, BOTH);
-- The information in the three attributes below should be modified
-- as per the device manufacturer's instructions
-- The first attribute specifies the number of bits in
-- the instruction register
--
-- The second attribute specifies the bit code for the BYPASS instruction
--
-- The third attribute specifies the bit pattern captured
-- by the instruction register. If you do not know the
-- capture pattern you may specify it as all X's, you will,
-- however, lose the capability of verifying the boundary-scan
-- chain on-the-fly
attribute Instruction_Length of nothing_at_all: entity is 4;
attribute Instruction_Opcode of nothing_at_all: entity is "BYPASS (1111)";
attribute Instruction_Capture of nothing_at_all : entity is "0001";
-- end of section that should be modified as per the device
-- manufacturer's instructions
attribute Boundary_Cells of nothing_at_all: entity is "BC_1";
attribute Boundary_Length of nothing_at_all: entity is 1;
attribute Boundary_Register of nothing_at_all: entity is "0 (BC_1, *, control, 0)";
end nothing_at_all;