by support »
Hello,
This is most likely not a problem. A similar warning for the xillybus_S_AXI interface is muted to Info level by the initialization script. It seems like Vivado 2017.2 produces the warning on xillybus_S_AXI instead, which is currently not muted. That's why it appeared as a Critical Warning to you.
On Vivado 2017.3, this warning disappears altogether.
So if the system boots up find, and /dev/xillybus_* files appear, you can safely ignore this warning.
Regards,
Eli
Hello,
This is most likely not a problem. A similar warning for the xillybus_S_AXI interface is muted to Info level by the initialization script. It seems like Vivado 2017.2 produces the warning on xillybus_S_AXI instead, which is currently not muted. That's why it appeared as a Critical Warning to you.
On Vivado 2017.3, this warning disappears altogether.
So if the system boots up find, and /dev/xillybus_* files appear, you can safely ignore this warning.
Regards,
Eli