why is it so that whatever I do, I am stuck with (Xilinx) problems?! I need urgently, within 2 days to implement a programming solution for XCF08P, unfortunatly the only devices for whicht the IEEE1532 BSDL files are not available are exactly the XCFxxP series Platform Flash !!!
Allmost all other devices have proper ieee1532 files available. For XCF08P impact is able to generate the .ISC file ok, but when I try to generate a SVF file from ISC (in order to reverse the ISC commands) then of course impact complains about missing bsdl files, giving an error, and soon after that there comes C asserition error
FATAL_ERROR: WinAPP.C:710
then of course follows quick self termination!!!
nice! thats 3 days after the release of 7.1 SP3
Antti if anyone (in or outside Xilinx) can help in either obtaining the ieee1532 BDSL files or proper programming specs for XCFP platform flash, I would be very glad :) I really dont wanna go reverse engineerinf the SVF files in order to get the programming algorithm.
"Antti Lukats" schrieb im Newsbeitrag news:db0h5t$upa$03$ snipped-for-privacy@news.t-online.com...
need
the
formatting link
there are some findings about the Platform Flash - I did think I did damage the chip by using inproper programming sequence, but it happened to be known silicon bug described in confidential Xilinx documents DS123-E03 !!!
but I am still unsure if I managed to damage the xcf08p by software as it is failing on verify when programmed with impact as well
the programming algorithm (reverse engineered from .SVF files!) works ok for readback and erase, still having problems with actual programming...
"Antti Lukats" schrieb im Newsbeitrag news:db33me$u8v$05$ snipped-for-privacy@news.t-online.com...
XCF08P
a
after
ieee1532
be
damage
known
is
for
uups!
the DS123-E03 is confidential!
but I did not include here any info what i obtained from it, only said that the errata that I am seeing is described there, this information is available from the public 'title' of the document as well public info (non conf) : "A test escape has been discovered with the devices named above which for some applications results in device failure during "Power on Reset Activation." Devices that have a VCCint ramp during "Power on Reset Activation" that takes longer than 1ms to reach 1.6V may see failures."
the FFFFFFFF as idcode and other erratic behavior are things I discovered myself and made public BEFORE I ever did read the DS123-E03, so that information is NOT derived from the confidential document.
I hope this explanation is not necessary, but I just figured out, that I have made public pretty much the info that is also described in a conf. document, again I really have not said anything what I did learn in the DS123-E03, except that this document applies to the problem I have, and this is something that could be guessed from the document title already.
The DS123-E03 document is not marked as confidential inside the document itself, and it is FREELY available from xilinx website, but before download there is 'agree' to the confidential statements, hence my long commentary to the issue.
Antti
PS i personally dont understand this kind of confidentiality clauses. If I have a product that doesnt work properly then I have the right to know why, if the vendor knows it this information should be made available, without the 'Agree' to conf clause. If I would have elected not to agree I would have never known that it was me who did burn the chip, but the chip was having silicon errata known to the chip vendor.
"Antti Lukats" schrieb im Newsbeitrag news:db34cg$2mu$00$ snipped-for-privacy@news.t-online.com...
XCF08P,
not
XCF08P
generate
course
after
would
its all working now, no thanks to anyone. my issues where somehow related to the V4 in the chain, yes the ES with JTAG errata. Not sure how but it makes some of the commands not working..
when I did see that bsdebug -irscan 1111111111111111 did not return proper values in the impact batch mode I did come suspisious and tested my XCF08P programming algo on different board with newer revision of the XCF08P silicon and no other devices in chain, the non working algo started to work immediatly.
ElectronDepot website is not affiliated with any of the manufacturers or service providers discussed here.
All logos and trade names are the property of their respective owners.