Also it may be blowing whatever power budget your port provides. Is it a USB2 or USB3 port? Sent from my iPhone > On Apr 12, 2021, at 3:36 PM, Marcus D Leech <patchvonbraun@gmail.com> wrote: > > There is no kernel-level > Driver for this device. It’s handled by Libusb > > Sent from my iPhone > >>> On Apr 12, 2021, at 3:34 PM, paradis@kwesst.com wrote: >>> >>  >> I’ve been poking around trying to find out any more information on my issue and I noticed this after running the ‘usb-devices’ command: >> >> T: Bus=01 Lev=01 Prnt=01 Port=01 Cnt=02 Dev#= 10 Spd=480 MxCh= 0 >> >> D: Ver= 2.00 Cls=00(>ifc ) Sub=00 Prot=00 MxPS=64 #Cfgs= 1 >> >> P: Vendor=2500 ProdID=0022 Rev=01.00 >> >> S: Manufacturer=Cypress >> >> S: Product=WestBridge >> >> S: SerialNumber=0000000004BE >> >> C: #Ifs= 1 Cfg#= 1 Atr=80 MxPwr=200mA >> >> I: If#=0x0 Alt= 0 #EPs= 0 Cls=ff(vend.) Sub=00 Prot=00 Driver=(none) >> >> >> >> The VID/PID are 2500:0022 so this is the B205 I have plugged in, but on the very last line it says “Driver=(none). >> >> Could there be something wrong with the UHD installation? Should I try a different version than v4.0.0.0? >> >> _______________________________________________ >> USRP-users mailing list -- usrp-users@lists.ettus.com >> To unsubscribe send an email to usrp-users-leave@lists.ettus.com

Hm, this looks like the EEPROM on the B205 containing the bootloader / initial USB identifier code for the USB chipset isn't quite right. Good news: you can fix that! When you built UHD, b2xx_fx3_utils got built along the way, and is probably install under somewhere like $PREFIX/lib64/uhd/utils or so. You'll need to locate usrp_b200_bl.img ; it's probably been downloaded alongside with the other firm- and gateware images to $PREFIX/share/uhd/images/ Then, it's just a matter of calling sudo /path/leading/us/to/b2xx_fx3_utils -B /full/path/of/usrp_b200_bl.img Best regards, Marcus the other DISCLAIMER: Any attached Code is provided As Is. It has not been tested or validated as a product, for use in a deployed application or system, or for use in hazardous environments. You assume all risks for use of the Code. Use of the Code is subject to terms of the licenses to the UHD or RFNoC code with which the Code is used. Standard licenses to UHD and RFNoC can be found at https://www.ettus.com/sdr-software/licenses/. NI will only perform services based on its understanding and condition that the goods or services (i) are not for the use in the production or development of any item produced, purchased, or ordered by any entity with a footnote 1 designation in the license requirement column of Supplement No. 4 to Part 744, U.S. Export Administration Regulations and (ii) such a company is not a party to the transaction. If our understanding is incorrect, please notify us immediately because a specific authorization may be required from the U.S. Commerce Department before the transaction may proceed further. On 12.04.21 21:15, paradis@kwesst.com wrote: > > This is the output of ‘dmesg -wH’ after plugging in the B205. > > > [Apr12 15:14] usb 1-1: new high-speed USB device number 11 using xhci_hcd > > [ +0.148694] usb 1-1: New USB device found, idVendor=2500, idProduct=0022, bcdDevice= 1.00 > > [ +0.000006] usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3 > > [ +0.000003] usb 1-1: Product: WestBridge > > [ +0.000003] usb 1-1: Manufacturer: Cypress > > [ +0.000003] usb 1-1: SerialNumber: 0000000004BE > > > _______________________________________________ > USRP-users mailing list -- usrp-users@lists.ettus.com > To unsubscribe send an email to usrp-users-leave@lists.ettus.com

Hi Marcus, thanks for the response. So I tried to do what you suggested, but unfortunately it’s giving me and error, and google isn’t being helpful at all, maybe you’ve seen this before? /usr/local/lib64/uhd/utils/b2xx_fx3_utils: symbol lookup error: /usr/local/lib64/uhd/utils/b2xx_fx3_utils: undefined symbol: _ZN10b200_iface16fx3_state_stringB5cxx11Eh It seems like the b2xx_fx3_utils is looking for a symbol it can find, is there something else I need to do before using the B2xx_fx3_utils? Thanks!

Have you checked the B205mini-i board itself to ensure the USB connector pins are soldered down securely? There have been instances where a dislodged connector caused USB connection issues. (If not, you can either retouch the connections yourself with a soldering iron or RMA to NI.) On Tue, Apr 13, 2021 at 11:32 AM <paradis@kwesst.com> wrote: > Hi Marcus, thanks for the response. So I tried to do what you suggested, > but unfortunately it’s giving me and error, and google isn’t being helpful > at all, maybe you’ve seen this before? > > /usr/local/lib64/uhd/utils/b2xx_fx3_utils: symbol lookup error: > /usr/local/lib64/uhd/utils/b2xx_fx3_utils: undefined symbol: > _ZN10b200_iface16fx3_state_stringB5cxx11Eh > > > It seems like the b2xx_fx3_utils is looking for a symbol it can find, is > there something else I need to do before using the B2xx_fx3_utils? > > Thanks! > > > _______________________________________________ > USRP-users mailing list -- usrp-users@lists.ettus.com > To unsubscribe send an email to usrp-users-leave@lists.ettus.com >

This is the kind of error that happens when you have a “mixed” system with libraries and utilities from different builds. Also after rhe build/install did you “sudo ldconfig” ? Sent from my iPhone > On Apr 13, 2021, at 2:38 PM, Robin Coxe <coxe@quanttux.com> wrote: > >  > Have you checked the B205mini-i board itself to ensure the USB connector pins are soldered down securely? There have been instances where a dislodged connector caused USB connection issues. (If not, you can either retouch the connections yourself with a soldering iron or RMA to NI.) > > > >> On Tue, Apr 13, 2021 at 11:32 AM <paradis@kwesst.com> wrote: >> Hi Marcus, thanks for the response. So I tried to do what you suggested, but unfortunately it’s giving me and error, and google isn’t being helpful at all, maybe you’ve seen this before? >> >> /usr/local/lib64/uhd/utils/b2xx_fx3_utils: symbol lookup error: /usr/local/lib64/uhd/utils/b2xx_fx3_utils: undefined symbol: _ZN10b200_iface16fx3_state_stringB5cxx11Eh >> >> >> >> It seems like the b2xx_fx3_utils is looking for a symbol it can find, is there something else I need to do before using the B2xx_fx3_utils? >> >> Thanks! >> >> >> >> _______________________________________________ >> USRP-users mailing list -- usrp-users@lists.ettus.com >> To unsubscribe send an email to usrp-users-leave@lists.ettus.com > _______________________________________________ > USRP-users mailing list -- usrp-users@lists.ettus.com > To unsubscribe send an email to usrp-users-leave@lists.ettus.com

Hi Marcus, I originally build the UHD without the 64bit option, then I rebuilt it with the 64bit on, but I didn’t uninstall the first UHD build. That might be causing some issues. Maybe I’ll do a clean install and try again. Also, yes, I did a ‘sudo ldconfig’ after the build/install. Thanks, hopefully tomorrow I’ll have some success.