Hello, I use an X310 for an application in which the daughterboards are 2 Basic RX and 2 BasicTX. The subdevspec I use (in a Gnuradio Flowgraph) is "A:A B:A", both for emission and reception. Last time someone from my lab checked (a year ago or so), UHD 003.009.007-release was apparently the latest UHD version that was OK with such subdevspec, and I therefore believe that I am effectively stuck to this old version.
I was working so far with a usrp_x310_fpga_HGS.bit FPGA image on the X310, with single 10Gb/s ethernet interface. However, I want now to improve performance by going to dual 10Gb/s interface. Unfortunately, using "uhd_images_downloader" (which seems to work fine and tells me it extracts .bit files from the correct 003.009.007-release version) followed by "uhd_image_loader --args="type=x300,addr=192.168.40.2" --fpga-path="/usr/local/share/uhd/images/usrp_x310_fpga_XG.bit" seems to upload an FPGA image that is not compatible with the UHD version (benchmark_rate, for example, gives a "Error: RuntimeError: Expected FPGA compatibility number 19, but got 33"). For reference, uploading usrp_x310_HG.bit produces a similar compatibility number error, but usrp_x310_HGS.bit does, on the contrary, upload an image that UHD is happy with. It seems to me that the files in the repository at "https://files.ettus.com/binaries/images/"; may be misplaced for the 003.009.007-release version. I actually tried manually dowloading the "https://files.ettus.com/binaries/images/uhd-images_003.009.007-release.tar.gz"; file and extracting the .bit files from that, but got the same results as when I use the .bit downloaded by uhd_image_loader. Can someone let me know if I am missing something here ? My only alternative, as I see it, would be to build the FPGA image myself with the fpga-src submodule of the UHD version I use, but that would first require me to get a Vivado license... Help would be greatly appreciated. -Yann _______________________________________________ USRP-users mailing list -- [email protected] To unsubscribe send an email to [email protected]
