On 04/19/2018 01:28 PM, John McGinn via USRP-users wrote: > I’m a relative newbie with rfnoc to build X310 loads so I may have > missed something, but if so, I can’t find what it is. > > > > After successfully making many HG builds (one 1GbE link, one 10GbE > link), I reached a point where I needed higher X310 to host bandwidth > so switched to making XG builds for the X310 with two 10GbE links with > the following: > > ./uhd_image_builder.py fft ROMsiggen keep_one_in_n -I > ~/rfnoc/src/rfnoc-X310ROMtx/ -d x310 -t X310_RFNOC_XG -m 5 --fill-with-fifos > > > > This worked well and I was then able to communicate to the X310 over a > 10GbE link on port 0, but when I wanted to make an HG build again with > the same HG command used previously, Vivado failed with fatal errors > about unassigned physical pins when I used the following: > > ./uhd_image_builder.py fft ROMsiggen keep_one_in_n -I > ~/rfnoc/src/rfnoc-X310ROMtx/ -d x310 -t X310_RFNOC_HG -m 5 --fill-with-fifos > > I found that when making XG builds, at least one constraints file, > including x300.xdc in ~/rfnoc/src/uhd-fpga/usrp3/top/x300 was changed to > reassign physical pins on the ethernet links but was not changed back > when I later tried to make an HG build again. > > I was able to work around the problem by restoring the x300 constraints > files to their original versions but it would be nice if the build > scripts did this automatically. Assuming this is not due to an error on > my part, is there any planned update for this?
John, what you're describing is the correct flow, and I'm not sure why it's failing. We'll first need to reproduce this. I can't give an estimate for when it'll be fixed. As a workaround, you might be able to run 'make clean' in the build directory to force generation of the corresponding IP. Thanks for bringing this up, Martin _______________________________________________ USRP-users mailing list [email protected] http://lists.ettus.com/mailman/listinfo/usrp-users_lists.ettus.com
