C
Christian Gelinek
Hi there,
I created a CPLD design which works perfect in simulation, but does not work
in hardware. There are many warnings from the Xilinx ISE looking like
WARNING:Xst:1291 - FF/Latch <Sig> is unconnected in block <Blck>.
and
WARNING:Xst:1710 - FF/Latch <Sig> (without init value) is constant in block
<Blck>.
These come up only in the Low Level Synthesis processing step. There is one
relevant solution record on the Xilinx website (see
http://www.xilinx.com/xlnx/xil_ans_display.jsp?iLanguageID=1&iCountryID=1&getPagePath=18396)
with the following suggestion:
created, but the output is never connected or the signals or logic it drives
have been trimmed. Check the XST log for messages such as the following to
find signals that have been trimmed out of the design:
"WARNING:Xst:646 - Signal <my_sig> is assigned but never used." <<
However, there are no such warnings in my XST log.
Any help would be appreciated.
Christian
I created a CPLD design which works perfect in simulation, but does not work
in hardware. There are many warnings from the Xilinx ISE looking like
WARNING:Xst:1291 - FF/Latch <Sig> is unconnected in block <Blck>.
and
WARNING:Xst:1710 - FF/Latch <Sig> (without init value) is constant in block
<Blck>.
These come up only in the Low Level Synthesis processing step. There is one
relevant solution record on the Xilinx website (see
http://www.xilinx.com/xlnx/xil_ans_display.jsp?iLanguageID=1&iCountryID=1&getPagePath=18396)
with the following suggestion:
created, but the output is never connected or the signals or logic it drives
have been trimmed. Check the XST log for messages such as the following to
find signals that have been trimmed out of the design:
"WARNING:Xst:646 - Signal <my_sig> is assigned but never used." <<
However, there are no such warnings in my XST log.
Any help would be appreciated.
Christian