I forgot to mention 2 things: 1) it originally didn't even get this far. It is looking for a non-existant "setup_env.sh" in the ".../top/e300/" folder. I copied the "setup_env.sh" from the ".../top/e31x" folder into the ".../top/e300" folder and then it ran and died as described below. 2) I forgot to mention that the first two lines displayed after running "make noc_block_gain_tb" were the following which at least confirms that it is intending to use the e310. But, I've been trying to navigate the make files with no success in deciding why it is choosing the xc7k part
Setting up a 64-bit FPGA build environment for the USRP-E31x... - Vivado: Found (/opt/Xilinx/Vivado/2018.3/bin) On Sat, Aug 3, 2019 at 3:27 PM Rob Kossler <rkoss...@nd.edu> wrote: > Hi, > I just installed installed the latest UHD master with fpga source and > installed the 2018.3 Xilinx webpack (I also have a 2017.4 webpack installed > which was working). I followed the rfnoc getting started build, but got > the following error when I tried the command "make noc_block_gain_tb" > > # puts "BUILDER: Creating Vivado simulation project part $part_name" > BUILDER: Creating Vivado simulation project part xc7k410tffg900-2 > # create_project -part $part_name -force $project_name/$project_name > WARNING: [Device 21-436] No parts matched 'xc7k410tffg900-2' > ERROR: [Coretcl 2-106] Specified part could not be found. > INFO: [Common 17-206] Exiting Vivado at Sat Aug 3 14:59:04 2019... > > I fully understand that webpack does not support the X310 part, but my > question is why is the part being selected? At the point of running the > rfnoc getting started example, I have not knowingly selected any part. My > assumption is that if I could change this part, the make will succeed. > Does anyone know how I can make it use a webpack compatible part like > xc7z020? > > Thanks. > Rob >
_______________________________________________ USRP-users mailing list USRP-users@lists.ettus.com http://lists.ettus.com/mailman/listinfo/usrp-users_lists.ettus.com
