Vivado locks IP if it's been targeted for the wrong device, or generated with the wrong version of the software.
Did you receive any warnings about the wrong version of Vivado being used? Are you running in a clean UHD repo (git status shows no changes)? I've run into this issue when things were targeted incorrectly and old artifacts were still present during the build process. Brian On Fri, Jan 13, 2023 at 1:48 PM <jmalo...@umass.edu> wrote: > Hello, > > > I have run the setupenv. > > build-ip is a folder that is made when the > makefile(uhd/fpga/usrp3/top/n3xx/Makefile.inc) is run. Removing it does not > do anything, but I did try commenting out include statements in the > Makefile. > > > I tried commenting hb47_1to2 in the makefile, and it proceeded since it > did not look for it. It asked for hb47_2to1, I commented that out and it > moved on, but then it looked for something called axi_hb31, which I could > not file in the include statements in the makefile. > > > The errors I get refer to an IP being “locked”, though I am unsure how to > proceed from there. Some of the IPs have been built successfully > _______________________________________________ > USRP-users mailing list -- usrp-users@lists.ettus.com > To unsubscribe send an email to usrp-users-le...@lists.ettus.com >
_______________________________________________ USRP-users mailing list -- usrp-users@lists.ettus.com To unsubscribe send an email to usrp-users-le...@lists.ettus.com
