linux; GNU C++ version 5.4.0 20160609; Boost_105800; UHD_003.010.002.000-3-g122bfae1..
No UHD Devices Found

Creating the usrp device with: ...
-- Detected Device: B210
-- Operating over USB 3.

Hi all, My B210 on Ubuntu 16.04 *used* to work fine. I recently downloaded and compiled ( & install) new host dev source /lib binaries ( examples etc) , NOW I cant see my B210. ( Its still phys there in dmesg) Ultimately I want to be able to compile and run my own C++ code through the UHD API. Today As advised by an example code, I also ran uhd_images_downloader.. & I notice I now have.. Nov 25 13:41 /usr/share/uhd/images/003.009.002.tag ( also old .hex, .bit etc ) Jan 6 00:52 /usr/local/share/uhd/images/003.010.002.000.tag (also NEW .hex, .bit etc ) Its also strange that libusb appears under ldd for any example-binaries, but NOT for "uhd_find_devices". ( related??) Can someone explain whats going on? ANd how i might compile my own code without inadvertantly installing new code that doesnt work with my B210 ?? Thanks. DM. Heres my outputs refd above.. >uhd_find_devices linux; GNU C++ version 5.4.0 20160609; Boost_105800; UHD_003.010.002.000-3-g122bfae1.. No UHD Devices Found > ....although the output from any example seem to at least notice its presence.. ~/uhd/host/build/examples$ ./2chan linux; GNU C++ version 5.4.0 20160609; Boost_105800; UHD_003.010.002.000-0-gbd6e21dc UHD Warning: Unable to set the thread priority. Performance may be negatively affected. Please see the general application notes in the manual for instructions. EnvironmentError: OSError: error in pthread_setschedparam Creating the usrp device with: ... -- Detected Device: B210 -- Operating over USB 3. ** Error: RuntimeError: Expected FPGA compatibility number 14, but got 13: The FPGA build is not compatible with the host code build. Please run: "/usr/local/lib/uhd/utils/uhd_images_downloader.py" --------- In case its relevant... Interestingly, looking at the libraries linked, "Uhd_find_devices" doesnt show libusb... ~/uhd/host/build/examples$ ldd /usr/bin/uhd_find_devices linux-vdso.so.1 => (0x00007ffc66df9000) libuhd.so.003 => /usr/local/lib/libuhd.so.003 (0x00007f2e958af000) libboost_program_options.so.1.58.0 => /usr/lib/x86_64-linux-gnu/libboost_program_options.so.1.58.0 (0x00007f2e95631000) libstdc++.so.6 => /usr/lib/x86_64-linux-gnu/libstdc++.so.6 (0x00007f2e952ae000) libgcc_s.so.1 => /lib/x86_64-linux-gnu/libgcc_s.so.1 (0x00007f2e95098000) libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x00007f2e94cce000) libboost_date_time.so.1.58.0 => /usr/lib/x86_64-linux-gnu/libboost_date_time.so.1.58.0 (0x00007f2e94abc000) libboost_filesystem.so.1.58.0 => /usr/lib/x86_64-linux-gnu/libboost_filesystem.so.1.58.0 (0x00007f2e948a4000) libboost_regex.so.1.58.0 => /usr/lib/x86_64-linux-gnu/libboost_regex.so.1.58.0 (0x00007f2e9459c000) libboost_system.so.1.58.0 => /usr/lib/x86_64-linux-gnu/libboost_system.so.1.58.0 (0x00007f2e94397000) libboost_serialization.so.1.58.0 => /usr/lib/x86_64-linux-gnu/libboost_serialization.so.1.58.0 (0x00007f2e94136000) libboost_thread.so.1.58.0 => /usr/lib/x86_64-linux-gnu/libboost_thread.so.1.58.0 (0x00007f2e93f10000) libpthread.so.0 => /lib/x86_64-linux-gnu/libpthread.so.0 (0x00007f2e93cf2000) librt.so.1 => /lib/x86_64-linux-gnu/librt.so.1 (0x00007f2e93aea000) libdl.so.2 => /lib/x86_64-linux-gnu/libdl.so.2 (0x00007f2e938e6000) libm.so.6 => /lib/x86_64-linux-gnu/libm.so.6 (0x00007f2e935dc000) /lib64/ld-linux-x86-64.so.2 (0x00005621eafec000) libicui18n.so.55 => /usr/lib/x86_64-linux-gnu/libicui18n.so.55 (0x00007f2e9317a000) libicuuc.so.55 => /usr/lib/x86_64-linux-gnu/libicuuc.so.55 (0x00007f2e92de5000) libicudata.so.55 => /usr/lib/x86_64-linux-gnu/libicudata.so.55 (0x00007f2e9132e000) whereas the example binaries do.. ~/uhd/host/build/examples$ ldd 2chan linux-vdso.so.1 => (0x00007ffc586ef000) libuhd.so.003 => /home/tarboy/uhd/host/build/lib/libuhd.so.003 (0x00007fbb73d4f000) libboost_program_options.so.1.58.0 => /usr/lib/x86_64-linux-gnu/libboost_program_options.so.1.58.0 (0x00007fbb73ab2000) libboost_system.so.1.58.0 => /usr/lib/x86_64-linux-gnu/libboost_system.so.1.58.0 (0x00007fbb738ad000) libboost_thread.so.1.58.0 => /usr/lib/x86_64-linux-gnu/libboost_thread.so.1.58.0 (0x00007fbb73687000) libpthread.so.0 => /lib/x86_64-linux-gnu/libpthread.so.0 (0x00007fbb7346a000) libstdc++.so.6 => /usr/lib/x86_64-linux-gnu/libstdc++.so.6 (0x00007fbb730e7000) libgcc_s.so.1 => /lib/x86_64-linux-gnu/libgcc_s.so.1 (0x00007fbb72ed1000) libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x00007fbb72b07000) libboost_date_time.so.1.58.0 => /usr/lib/x86_64-linux-gnu/libboost_date_time.so.1.58.0 (0x00007fbb728f5000) libboost_filesystem.so.1.58.0 => /usr/lib/x86_64-linux-gnu/libboost_filesystem.so.1.58.0 (0x00007fbb726dd000) libboost_regex.so.1.58.0 => /usr/lib/x86_64-linux-gnu/libboost_regex.so.1.58.0 (0x00007fbb723d5000) libboost_serialization.so.1.58.0 => /usr/lib/x86_64-linux-gnu/libboost_serialization.so.1.58.0 (0x00007fbb72173000) librt.so.1 => /lib/x86_64-linux-gnu/librt.so.1 (0x00007fbb71f6b000) libdl.so.2 => /lib/x86_64-linux-gnu/libdl.so.2 (0x00007fbb71d67000) ** libusb-1.0.so.0 => /lib/x86_64-linux-gnu/libusb-1.0.so.0 (0x00007fbb71b4e000) libm.so.6 => /lib/x86_64-linux-gnu/libm.so.6 (0x00007fbb71845000) /lib64/ld-linux-x86-64.so.2 (0x0000561ac9388000) libicui18n.so.55 => /usr/lib/x86_64-linux-gnu/libicui18n.so.55 (0x00007fbb713e2000) libicuuc.so.55 => /usr/lib/x86_64-linux-gnu/libicuuc.so.55 (0x00007fbb7104e000) libudev.so.1 => /lib/x86_64-linux-gnu/libudev.so.1 (0x00007fbb7102d000) libicudata.so.55 => /usr/lib/x86_64-linux-gnu/libicudata.so.55 (0x00007fbb6f576000)

  linux; GNU C++ version 5.4.0 20160609; Boost_105800; UHD_003.010.002.000-3-
  g122bfae1..>      No UHD Devices Found

  Creating the usrp device with: ...
  -- Detected Device: B210
  -- Operating over USB 3.

Hi David - It looks like you have 2 versions of UHD around, both of which are in standard install locations (/usr and /usr/local). This can cause confusion / issues when running executables for either install. I'd advise you to pick one UHD install and remove the other; you might have to even remove both & reinstall to get this to work (especially with the odd libusb issue you noted). It's clear from the error you noted ("Error: RuntimeError: Expected FPGA compatibility number 14, but got 13: The FPGA build is not compatible with the host code build.") that both installs are trying to be used. Hence if you don't need the older install, why keep it around? Hope this helps! - MLD On Fri, Jan 5, 2018, at 10:18 AM, David Merit via USRP-users wrote: > My B210 on Ubuntu 16.04 *used* to work fine. I recently downloaded and > compiled ( & install) new host dev source /lib binaries ( examples > etc) , NOW I cant see my B210. ( Its still phys there in dmesg)> Ultimately I want to be able to compile and run my own C++ code > through the UHD API.> Today As advised by an example code, I also ran > uhd_images_downloader.. & I notice I now have..> Nov 25 13:41 /usr/share/uhd/images/003.009.002.tag ( also old .hex, > .bit etc )> Jan 6 00:52 /usr/local/share/uhd/images/003.010.002.000.tag (also > NEW .hex, .bit etc )> Its also strange that libusb appears under ldd for any example- > binaries, but NOT for "uhd_find_devices". ( related??)> Can someone explain whats going on? ANd how i might compile my own > code without inadvertantly installing new code that doesnt work with > my B210 ??> Thanks. > DM. > > Heres my outputs refd above.. > >uhd_find_devices > linux; GNU C++ version 5.4.0 20160609; Boost_105800; UHD_003.010.002.000-3- > g122bfae1..> No UHD Devices Found > > > > ....although the output from any example seem to at least notice its > presence..> > ~/uhd/host/build/examples$ ./2chan > linux; GNU C++ version 5.4.0 20160609; Boost_105800; UHD_003.010.002.000-0- > gbd6e21dc> UHD Warning: > Unable to set the thread priority. Performance may be > negatively affected.> Please see the general application notes in the manual for > instructions.> EnvironmentError: OSError: error in pthread_setschedparam > > Creating the usrp device with: ... > -- Detected Device: B210 > -- Operating over USB 3. > ** Error: RuntimeError: Expected FPGA compatibility number 14, but > got 13:> The FPGA build is not compatible with the host code build. > Please run: > "/usr/local/lib/uhd/utils/uhd_images_downloader.py" > > --------- > In case its relevant... > Interestingly, looking at the libraries linked, "Uhd_find_devices" > doesnt show libusb...> > ~/uhd/host/build/examples$ ldd /usr/bin/uhd_find_devices > linux-vdso.so.1 => (0x00007ffc66df9000) > libuhd.so.003 => /usr/local/lib/libuhd.so.003 > (0x00007f2e958af000)> libboost_program_options.so.1.58.0 => /usr/lib/x86_64-linux- > gnu/libboost_program_options.so.1.58.0 (0x00007f2e95631000)> libstdc++.so.6 => /usr/lib/x86_64-linux-gnu/libstdc++.so.6 > (0x00007f2e952ae000)> libgcc_s.so.1 => /lib/x86_64-linux-gnu/libgcc_s.so.1 > (0x00007f2e95098000)> libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 > (0x00007f2e94cce000)> libboost_date_time.so.1.58.0 => /usr/lib/x86_64-linux- > gnu/libboost_date_time.so.1.58.0 (0x00007f2e94abc000)> libboost_filesystem.so.1.58.0 => /usr/lib/x86_64-linux- > gnu/libboost_filesystem.so.1.58.0 (0x00007f2e948a4000)> libboost_regex.so.1.58.0 => /usr/lib/x86_64-linux- > gnu/libboost_regex.so.1.58.0 (0x00007f2e9459c000)> libboost_system.so.1.58.0 => /usr/lib/x86_64-linux- > gnu/libboost_system.so.1.58.0 (0x00007f2e94397000)> libboost_serialization.so.1.58.0 => /usr/lib/x86_64-linux- > gnu/libboost_serialization.so.1.58.0 (0x00007f2e94136000)> libboost_thread.so.1.58.0 => /usr/lib/x86_64-linux- > gnu/libboost_thread.so.1.58.0 (0x00007f2e93f10000)> libpthread.so.0 => /lib/x86_64-linux-gnu/libpthread.so.0 > (0x00007f2e93cf2000)> librt.so.1 => /lib/x86_64-linux-gnu/librt.so.1 > (0x00007f2e93aea000)> libdl.so.2 => /lib/x86_64-linux-gnu/libdl.so.2 > (0x00007f2e938e6000)> libm.so.6 => /lib/x86_64-linux-gnu/libm.so.6 > (0x00007f2e935dc000)> /lib64/ld-linux-x86-64.so.2 (0x00005621eafec000) > libicui18n.so.55 => /usr/lib/x86_64-linux- > gnu/libicui18n.so.55 (0x00007f2e9317a000)> libicuuc.so.55 => /usr/lib/x86_64-linux-gnu/libicuuc.so.55 > (0x00007f2e92de5000)> libicudata.so.55 => /usr/lib/x86_64-linux- > gnu/libicudata.so.55 (0x00007f2e9132e000)> > whereas the example binaries do.. > ~/uhd/host/build/examples$ ldd 2chan > linux-vdso.so.1 => (0x00007ffc586ef000) > libuhd.so.003 => > /home/tarboy/uhd/host/build/lib/libuhd.so.003 > (0x00007fbb73d4f000)> libboost_program_options.so.1.58.0 => /usr/lib/x86_64-linux- > gnu/libboost_program_options.so.1.58.0 (0x00007fbb73ab2000)> libboost_system.so.1.58.0 => /usr/lib/x86_64-linux- > gnu/libboost_system.so.1.58.0 (0x00007fbb738ad000)> libboost_thread.so.1.58.0 => /usr/lib/x86_64-linux- > gnu/libboost_thread.so.1.58.0 (0x00007fbb73687000)> libpthread.so.0 => /lib/x86_64-linux-gnu/libpthread.so.0 > (0x00007fbb7346a000)> libstdc++.so.6 => /usr/lib/x86_64-linux-gnu/libstdc++.so.6 > (0x00007fbb730e7000)> libgcc_s.so.1 => /lib/x86_64-linux-gnu/libgcc_s.so.1 > (0x00007fbb72ed1000)> libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 > (0x00007fbb72b07000)> libboost_date_time.so.1.58.0 => /usr/lib/x86_64-linux- > gnu/libboost_date_time.so.1.58.0 (0x00007fbb728f5000)> libboost_filesystem.so.1.58.0 => /usr/lib/x86_64-linux- > gnu/libboost_filesystem.so.1.58.0 (0x00007fbb726dd000)> libboost_regex.so.1.58.0 => /usr/lib/x86_64-linux- > gnu/libboost_regex.so.1.58.0 (0x00007fbb723d5000)> libboost_serialization.so.1.58.0 => /usr/lib/x86_64-linux- > gnu/libboost_serialization.so.1.58.0 (0x00007fbb72173000)> librt.so.1 => /lib/x86_64-linux-gnu/librt.so.1 > (0x00007fbb71f6b000)> libdl.so.2 => /lib/x86_64-linux-gnu/libdl.so.2 > (0x00007fbb71d67000)> ** libusb-1.0.so.0 => /lib/x86_64-linux-gnu/libusb-1.0.so.0 > (0x00007fbb71b4e000)> libm.so.6 => /lib/x86_64-linux-gnu/libm.so.6 > (0x00007fbb71845000)> /lib64/ld-linux-x86-64.so.2 (0x0000561ac9388000) > libicui18n.so.55 => /usr/lib/x86_64-linux- > gnu/libicui18n.so.55 (0x00007fbb713e2000)> libicuuc.so.55 => /usr/lib/x86_64-linux-gnu/libicuuc.so.55 > (0x00007fbb7104e000)> libudev.so.1 => /lib/x86_64-linux-gnu/libudev.so.1 > (0x00007fbb7102d000)> libicudata.so.55 => /usr/lib/x86_64-linux- > gnu/libicudata.so.55 (0x00007fbb6f576000)