AR #22742 - 8.1i EDK - ChipScope ICON automatic MDM identification does not work for non Virtex-4 parts - (MAP errors because of multiple BSCAN components)

Search Answers Database


 

8.1i EDK - ChipScope ICON automatic MDM identification does not work for non Virtex-4 parts - (MAP errors because of multiple BSCAN components)

AR# 22742
Part EDK_General
Last Modified 2006-01-19 00:00:00.0
Status Active
Keywords OPB_MDM, JTAG, BSCAN

Description

Keywords: OPB_MDM, JTAG, BSCAN

With the chipscope_icon_v1.01.a core, customers do not have to specify the C_SYSTEM_CONTAINS_MDM parameter. The TCL code automatically sets this parameter based on the presence of MDM IP or use of Virtex-4 architecture. The TCL code, which checks for the MDM core, has a bug that results in using multiple BSCANs.

Solution

1. Locate and open in a text editor C:\EDK\hw\XilinxProcessorIPLib\pcores\chipscope_icon_v1_01_a\data\chipscope_icon_v2_1_0.tcl
2. Change the following code from:

foreach ip $iplist {
set ipname [xget_hw_name $ip]
# set mpd_handle [xget_hw_mpd_handle $ip]
set iptype [xget_hw_option_value $ip IPTYPE]
# puts "Instance $ipname is of type $iptype"
if { $iptype == "opb_mdm" } {
return 1
}
}


to

foreach ip $iplist {
set ip_instance_name [xget_hw_name $ip]
set ip_realname [xget_hw_value $ip]
puts "Instance $ip_instance_name has realname: $ip_realname"
if { $ip_realname == "opb_mdm" } {
return 1
}
}

3. Save and close the file.

This problem will be fixed in Service Pack 1 for EDK.
 
 
/csi/footer.htm