12-03-2019 08:43 PM
Hello,
We have 2 different PROM XCF02S ICs, One is XCF02S V and another is XCF02S VG. I have checked datasheet of IC. In that it is mentioned that VG version IC are Lead (Pb Free) Free.
XCF02S V version PROM IC is failed to program under ISE Impact 14.2/14.7 using Digilent’s HS1/HS3 cable. Error is IDCODE does not match issue (tried on different TCK frequencies but same problem occurs). But same PROM is programmed successfully under ISE Impact 10.1 with parallel port cable and transfer program to FPGA.
While XCF02S VG version PROM IC is programmed successfully under ISE Impact 14.2/14.7 using Digilent’s HS1/HS3 cable and transfers data to FPGA. Also it is programmed successfully under ISE Impact 10.1 with parallel port cable and transfer program to FPGA.
What’s the difference between V and VG versions?
12-03-2019 09:10 PM
Hello @anshumantech
It seems their is change in version of flash XCF02S due to change in package
12-03-2019 10:41 PM
there shouldnt be any difference in the way leaded and lead free XCF02S programming is concerned.
could you try with Xilinx platform usb programming cable in 14.7/14.2 both the proms and share the results
https://www.xilinx.com/products/boards-and-kits/hw-usb-ii-g.html
This will help in identifying if the issue is in impact tool/xilinx device or with the programming cable
12-06-2019 12:22 AM
12-06-2019 01:08 AM
12-13-2019 04:24 AM
12-13-2019 10:43 AM
12-15-2019 10:38 PM - edited 12-15-2019 10:39 PM
12-15-2019 11:39 PM
12-17-2019 05:03 AM
12-17-2019 05:13 AM
IDcode fits as an answer,
From what you said, It can be concluded that older tools dont sheck the IDCODE ?
whilst newer tools do check the ID code.
So older tools can program either part, as they dont care about IDcode.
where as newer tools need correct ID code in part to match the file,
My guess is your file is for the VG part, so will program VG parts for all tools.
whilst only the older tools, that dont care about ID code can be used to program a V part whos ID does not match the file.
have a great Christmas
12-18-2019 10:09 PM - edited 12-18-2019 10:11 PM
Sorry to bother you. However answer following: -
Who is supplying IDCODE? The newer software has to read it correctly from VG version but cannot read from V version. In both cases we only select XCF02S part yet newer software fails to detect part with V version but detects VG version.
Conclusion: Xilinx must release patch file for correct the anomaly, we have no role to play here. So please learn to draw correct conclusion. Merry Christmas!
12-18-2019 11:49 PM
12-20-2019 05:03 AM