by support »
Hello,
This is Xilinx' mapper which has gone a bit too far with optimizing the design. This is essentially a bug in the tools, which tends to appear in particular when there are pins of an IP core that aren't used by the application logic. So the mapper gets eager to cut away unused logic, and at some point confuses itself.
Odds are that there is some Xillybus interface that you didn't use, possibly the one that you just generated. Note that it isn't enough to connect it to some wires in a module, but it has to be used to the extent that it has some effect on the outer world. Otherwise, the tools detect that noone will see if the logic is removed, and which case the logic is optimized away.
Regards,
Eli
Hello,
This is Xilinx' mapper which has gone a bit too far with optimizing the design. This is essentially a bug in the tools, which tends to appear in particular when there are pins of an IP core that aren't used by the application logic. So the mapper gets eager to cut away unused logic, and at some point confuses itself.
Odds are that there is some Xillybus interface that you didn't use, possibly the one that you just generated. Note that it isn't enough to connect it to some wires in a module, but it has to be used to the extent that it has some effect on the outer world. Otherwise, the tools detect that noone will see if the logic is removed, and which case the logic [b]is[/b] optimized away.
Regards,
Eli