使用IMPACT 11.4编程后变得非常热

埃里克
显然，有一些非常非常错误的事情。
然而，影响不是问题。
这部分家族现在已经超过4年了，如果这是一个问题，它将在这里爆炸成一个全面的应急响应。
鉴于我从未听说过这种情况，看起来似乎没有影响责任。
影响不会用错误的位文件编程一个部分（它将错误输出，并告诉你它不能编程该部分），自Virtex E / Spartan 2天后更正。
那时候，你可以获得一个高电流条件编程一个较小的部分，其中一个位文件用于较大的部分。
哪个电源在发热时提供电流，Vccint，Vccaux或Vcco？
记住这一点，我们稍后会再回来。
更有可能的是该部件已经锁定。
这被称为SCR撬棒或闩锁，是由向IO注入（或抽出）超过200 mA的电流引起的。
检查编程电压。
是2.5v还是3.3v？
应该是哪一个？
检查IO，当发生这种闩锁时他们在做什么？
如果这是在IO组中的闩锁，这将从Vcco吸收过多的电流。
如果这是ESD zap（下面）或Impact编程电缆电压问题，电流可能会进入Vccaux。
另一个可能的原因是ESD：如果您已将ESD放电到器件中，它现在可能已损坏，并且更容易发生闩锁。
最后，在bitgen中构建位文件时是否有任何DRC违规？
查看日志文件（最后一条评论非常不合适，但为了充分披露，我在这里提到它总是检查你的bitgen警告）。
Austin Lesea主要工程师Xilinx San Jose



以下为原文

Erik,

Obviously, there is something very, very wrong.

Impact is not the problem, however.  This part family is now more than 4 years old, and if this was a problem, it would have exploded here into a full scale emergency response.  Given that I have never heard of this happening, it doesn't seem that Impact is to blame.
 
Impact will not program a part with the wrong bitfile (it will error out, and tell you it can not program the part), corrected since the Virtex E/Spartan 2 days.  Back then, you could get a high current condition programming a smaller part with a bitfile intended for a larger part.
 
Which power supply is supplying the current when it gets hot, Vccint, Vccaux, or Vcco?  Remember this, we will return to it later.

Much more likely is that the part has latched-up.  This is known as SCR crowbar or  latch-up, and is caused by injecting more than 200 mA of current into (or drawn out of) the IO's.
 
Check the programming voltage.  Is it 2.5v or 3.3v?  Which is it supposed to be?  Check the IOs, what are they doing when this latch-up occurs?
 
If this is latch-up in the IO banks, this will be drawing excessive current from Vcco.  If this is a ESD zap (below) or a Impact programming cable voltage issue, the current may be going into Vccaux.
 
Another possible cause is ESD:  if you have discharged ESD into the part, it may be now damaged, and much more prone to latch-up.
 
Last, were there any DRC violations when the bitfile was built in bitgen?  Look at the log files (this last comment is extremely unlikey to be the issue, but in the interest of full disclosure, I mention it here to always check you bitgen warnings).
 
 
Austin Lesea
Principal Engineer
Xilinx San Jose