Hi, we're porting our block to the latest Vivado 2017.4 environment but have a few issues we can't explain.
1. Although uhd_usrp_probe finds the blocks with the correct names, it doesn't find the custom control block. This is reported by probe with a warning. Strange thing is that even if we don't use our custom code and just create the block with rfnocmodtool asking to create the custom block, verified the block is compiled and installed under lib, we still see this warning message, which suggests that either the so has not been loaded or there's some kind of mismatch. Xml is instead loaded and correctly parsed as block name is recognized 2. Our block is instantiated manually in x300_core as it has 4 axi ports so can't be automatically instantiated. One of the 4 ports exposes a DDC which is basically cut&paste of the noc DDC block. When doing probe the block does not responds to requests and probe fails. This was working with vivado 2015.4 and yes, we added bus_clk and bus_rst in axi_wrapper Can anyone help at least on the first point? We can't really understand why our custom control block seems to be ignored. Thanks, Dario Pennisi
_______________________________________________ USRP-users mailing list USRP-users@lists.ettus.com http://lists.ettus.com/mailman/listinfo/usrp-users_lists.ettus.com
