07-19-2010 03:29 PM
I am attempting to use the ScanWorks boundary scan software from Asset Intertech to test a board with an XC5VLX30T-1FF323I. Using iMPACT, the chain functions normally. I can talk to all of the devices and even program the attached flash on the FPGA. ScanWorks can read the IDCODE of all devices in the chain including the FPGA. However, the next thing it checks is the boundary scan length which does not report the same value that's expected from the bsdl, so the test fails. Any suggestions?
07-19-2010 04:09 PM
Have you contacted ASSET InterTech support and asked them?
07-20-2010 06:21 AM
Yes, I am in contact with Asset support. They mentioned there are some quirks with the XC5 family bsdl, but so far my board is designed per their recommendations. Does iMPACT look at the scan length of the devices when it initializes the chain? The bsdl file says the scan length of my part is 1265. What could cause an incorrect scan length error? I've been testing the board, and it is fully functional. Is there some configuration pin that interferes with boundary scan operation?
07-20-2010 08:26 AM
The iMPACT tool is only concerned about the length of the TAP controller Instruction Register for each device and does not execute any IO test commands.
The issue here is really with the way that the Asset InterTech ScanWorks tool is interperting the BSDL file and executing JTAG commands and since they know their tool the best they should be able to best help you.
05-24-2011 08:08 AM
Using a different boundary scan tool I am experiencing a problem with the BOUNDARY_LENGTH of a XC5VLX220T_1738. IP - What was the resolution?