So, I've got a new USRP B200 for some signals analysis work, and while I'll probably be using GNU Radio on Linux eventually, I was trying to get something simple going on a Windows machine to start and to make sure it could do what I want it to do. I have the B200 installed and working. uhd_usrp_probe shows (truncated) Win32; Microsoft Visual C++ version 10.0; Boost_105400; UHD_003.007.001-release -- Operating over USB 3. -- Initialize CODEC control... -- Initialize Radio control... -- Performing register loopback test... pass -- Performing CODEC loopback test... pass -- Asking for clock rate 32 MHz -- Actually got clock rate 32 MHz -- Performing timer loopback test... pass | | Mboard: B200 | | revision: 5 | | product: 1 | | serial: xxxxxx | | name: MyB200 | | **FW Version: 4.0** | | **FPGA Version: 3.0** I chose the 003.007.001 release because I wanted to try HDSDR, and the Balint 1.6 beta 3 Windows binaries ( http://wiki.spench.net/wiki/USRP_Interfaces ) use UHD 3.7.1. So, why, when I try to start HDSDR, do I get Failed to create device without device hint: While creating the UHD device: RuntimeError: Expected firmware compatability number 8.0, but got 4.0: The firmware build it not compatible with the host code build. As an administrator, please run "C:\Program Files\UHD\lib\utils\uhd_images_downloader.py" I believe I have downloaded the correct images (I had to end up doing it manually because the http://files.ettus.com/binaries/uhd/uhd_003.007.001-release/uhd-images_003.007.001-release.zip images file on the ettus website is a tarball, not a zipfile like the script wants). Is there a step I'm missing to actually upload the image to the B200? I thought that's what was done at runtime. The HDSDR install was done by the combined ExtIO_USRP+FCD+RTL2832U+BorIP_Setup installer, and it seems to have put the necessary files like usrp_b200_fpga.bin into the HDSDR directory, and they seem the same as the ones that came with the UHD 3.7.1 kit from Ettus. So, what am I missing? -- Chris 'Xenon' Hanson, omo sanza lettere. Xenon@AlphaPixel.com http://www.alphapixel.com/ Training • Consulting • Contracting 3D • Scene Graphs (Open Scene Graph/OSG) • OpenGL 2 • OpenGL 3 • OpenGL 4 • GLSL • OpenGL ES 1 • OpenGL ES 2 • OpenCL Legal/IP • Code Forensics • Digital Imaging • GIS • GPS • osgEarth • Terrain • Telemetry • Cryptography • LIDAR • Embedded • Mobile • iPhone/iPad/iOS • Android @alphapixel <https://twitter.com/alphapixel> facebook.com/alphapixel (775) 623-PIXL [7495]

Hi Chris, First off, there is a live image that has GNU Radio and UHD already installed that you can boot into from a USB stick. Its a pretty nice way to try things out without messing with your Windows install: https://gnuradio.org/redmine/projects/gnuradio/wiki/GNURadioLiveDVD How new is your B200? If you just got it within the last few months, it will not be compatible with the older version of UHD. There was a slight hardware change that requires an up to date UHD install. -Trip On Wed, Jan 6, 2016 at 10:20 AM, Chris Hanson via USRP-users < usrp-users@lists.ettus.com> wrote: > So, I've got a new USRP B200 for some signals analysis work, and while > I'll probably be using GNU Radio on Linux eventually, I was trying to get > something simple going on a Windows machine to start and to make sure it > could do what I want it to do. > > > I have the B200 installed and working. uhd_usrp_probe shows (truncated) > > Win32; Microsoft Visual C++ version 10.0; Boost_105400; > UHD_003.007.001-release > > > -- Operating over USB 3. > -- Initialize CODEC control... > -- Initialize Radio control... > -- Performing register loopback test... pass > -- Performing CODEC loopback test... pass > -- Asking for clock rate 32 MHz > -- Actually got clock rate 32 MHz > -- Performing timer loopback test... pass > | | Mboard: B200 > | | revision: 5 > | | product: 1 > | | serial: xxxxxx > | | name: MyB200 > | | **FW Version: 4.0** > | | **FPGA Version: 3.0** > > > I chose the 003.007.001 release because I wanted to try HDSDR, and the > Balint 1.6 beta 3 Windows binaries ( > http://wiki.spench.net/wiki/USRP_Interfaces ) use UHD 3.7.1. > > > So, why, when I try to start HDSDR, do I get > > Failed to create device without device hint: > > While creating the UHD device: RuntimeError: Expected firmware > compatability number 8.0, but got 4.0: The firmware build it not compatible > with the host code build. As an administrator, please run "C:\Program > Files\UHD\lib\utils\uhd_images_downloader.py" > > I believe I have downloaded the correct images (I had to end up doing it > manually because the > http://files.ettus.com/binaries/uhd/uhd_003.007.001-release/uhd-images_003.007.001-release.zip images > file on the ettus website is a tarball, not a zipfile like the script > wants). > > Is there a step I'm missing to actually upload the image to the B200? I > thought that's what was done at runtime. > > The HDSDR install was done by the combined > ExtIO_USRP+FCD+RTL2832U+BorIP_Setup installer, and it seems to have put the > necessary files like usrp_b200_fpga.bin into the HDSDR directory, and they > seem the same as the ones that came with the UHD 3.7.1 kit from Ettus. So, > what am I missing? > > > > -- > Chris 'Xenon' Hanson, omo sanza lettere. Xenon@AlphaPixel.com > http://www.alphapixel.com/ > Training • Consulting • Contracting > 3D • Scene Graphs (Open Scene Graph/OSG) • OpenGL 2 • OpenGL 3 • OpenGL 4 > • GLSL • OpenGL ES 1 • OpenGL ES 2 • OpenCL > Legal/IP • Code Forensics • Digital Imaging • GIS • GPS • > osgEarth • Terrain • Telemetry • Cryptography • LIDAR • Embedded • Mobile • > iPhone/iPad/iOS • Android > @alphapixel <https://twitter.com/alphapixel> facebook.com/alphapixel (775) > 623-PIXL [7495] > > _______________________________________________ > USRP-users mailing list > USRP-users@lists.ettus.com > http://lists.ettus.com/mailman/listinfo/usrp-users_lists.ettus.com > >

Hello Chris, >From your output I can see that you have a Revision 5 B200. As Trip said, this was a minor hardware update which is only supported in UHD 3.8.4 and above. The EXTIO interface currently does not support the B200 revision 5, and a number of other USRPs, but that page also mentions an EXTIO 1.7 version which will have UHD 3.10 (currently the development version) support. I'm afraid you will have to wait until EXTIO updates or modify it to use the newer UHD. I'd recommend using the LiveUSB environment which Trip refers to. That's the easiest way to get started. GNU Radio is currently unsupported in Windows, though there is an experimental binary release here: http://www.gcndevelopment.com/gnuradio/ It only works on modern CPUs with the AVX2 instruction set extension. I hope this gets you going. Please feel free to ask any questions. Regards, Derek On Wed, Jan 6, 2016 at 10:52 AM, James Humphries via USRP-users < usrp-users@lists.ettus.com> wrote: > Hi Chris, > > First off, there is a live image that has GNU Radio and UHD already > installed that you can boot into from a USB stick. Its a pretty nice way to > try things out without messing with your Windows install: > > https://gnuradio.org/redmine/projects/gnuradio/wiki/GNURadioLiveDVD > > > How new is your B200? If you just got it within the last few months, it > will not be compatible with the older version of UHD. There was a slight > hardware change that requires an up to date UHD install. > > -Trip > > On Wed, Jan 6, 2016 at 10:20 AM, Chris Hanson via USRP-users < > usrp-users@lists.ettus.com> wrote: > >> So, I've got a new USRP B200 for some signals analysis work, and while >> I'll probably be using GNU Radio on Linux eventually, I was trying to get >> something simple going on a Windows machine to start and to make sure it >> could do what I want it to do. >> >> >> I have the B200 installed and working. uhd_usrp_probe shows (truncated) >> >> Win32; Microsoft Visual C++ version 10.0; Boost_105400; >> UHD_003.007.001-release >> >> >> -- Operating over USB 3. >> -- Initialize CODEC control... >> -- Initialize Radio control... >> -- Performing register loopback test... pass >> -- Performing CODEC loopback test... pass >> -- Asking for clock rate 32 MHz >> -- Actually got clock rate 32 MHz >> -- Performing timer loopback test... pass >> | | Mboard: B200 >> | | revision: 5 >> | | product: 1 >> | | serial: xxxxxx >> | | name: MyB200 >> | | **FW Version: 4.0** >> | | **FPGA Version: 3.0** >> >> >> I chose the 003.007.001 release because I wanted to try HDSDR, and the >> Balint 1.6 beta 3 Windows binaries ( >> http://wiki.spench.net/wiki/USRP_Interfaces ) use UHD 3.7.1. >> >> >> So, why, when I try to start HDSDR, do I get >> >> Failed to create device without device hint: >> >> While creating the UHD device: RuntimeError: Expected firmware >> compatability number 8.0, but got 4.0: The firmware build it not compatible >> with the host code build. As an administrator, please run "C:\Program >> Files\UHD\lib\utils\uhd_images_downloader.py" >> >> I believe I have downloaded the correct images (I had to end up doing it >> manually because the >> http://files.ettus.com/binaries/uhd/uhd_003.007.001-release/uhd-images_003.007.001-release.zip images >> file on the ettus website is a tarball, not a zipfile like the script >> wants). >> >> Is there a step I'm missing to actually upload the image to the B200? I >> thought that's what was done at runtime. >> >> The HDSDR install was done by the combined >> ExtIO_USRP+FCD+RTL2832U+BorIP_Setup installer, and it seems to have put the >> necessary files like usrp_b200_fpga.bin into the HDSDR directory, and they >> seem the same as the ones that came with the UHD 3.7.1 kit from Ettus. So, >> what am I missing? >> >> >> >> -- >> Chris 'Xenon' Hanson, omo sanza lettere. Xenon@AlphaPixel.com >> http://www.alphapixel.com/ >> Training • Consulting • Contracting >> 3D • Scene Graphs (Open Scene Graph/OSG) • OpenGL 2 • OpenGL 3 • OpenGL 4 >> • GLSL • OpenGL ES 1 • OpenGL ES 2 • OpenCL >> Legal/IP • Code Forensics • Digital Imaging • GIS • GPS • >> osgEarth • Terrain • Telemetry • Cryptography • LIDAR • Embedded • Mobile • >> iPhone/iPad/iOS • Android >> @alphapixel <https://twitter.com/alphapixel> facebook.com/alphapixel (775) >> 623-PIXL [7495] >> >> _______________________________________________ >> USRP-users mailing list >> USRP-users@lists.ettus.com >> http://lists.ettus.com/mailman/listinfo/usrp-users_lists.ettus.com >> >> > > _______________________________________________ > USRP-users mailing list > USRP-users@lists.ettus.com > http://lists.ettus.com/mailman/listinfo/usrp-users_lists.ettus.com > >

> > > First off, there is a live image that has GNU Radio and UHD already > installed that you can boot into from a USB stick. Its a pretty nice way to > try things out without messing with your Windows install: > > https://gnuradio.org/redmine/projects/gnuradio/wiki/GNURadioLiveDVD > > Ok, I'll check that out. I was hoping to try out HDSDR. > How new is your B200? If you just got it within the last few months, it > will not be compatible with the older version of UHD. There was a slight > hardware change that requires an up to date UHD install. > I just got it in late December. So that must be the conflict. I will see if there will be a newer binary release of the Balint code. I gotta say, the user experience getting started has been kinda rough. The Ettus UHD driver kit seems to malfunction if not installed into "C:\Program Files" (some paths seem hard coded to that and can't handle the "Program Files (x86)" of a typical x64 Windows install). The python scripts need the "requests" module, but don't install it. They also rely on a "HOME" environment variable that doesn't exist on Windows. It kinda feels like nobody has actually used/tested this product on Windows in a long time. My actual development will be done on Linux, but as far as being able to plug it in and try it out on Windows, it's been pretty frustrating. -- Chris 'Xenon' Hanson, omo sanza lettere. Xenon@AlphaPixel.com http://www.alphapixel.com/ Training • Consulting • Contracting 3D • Scene Graphs (Open Scene Graph/OSG) • OpenGL 2 • OpenGL 3 • OpenGL 4 • GLSL • OpenGL ES 1 • OpenGL ES 2 • OpenCL Legal/IP • Code Forensics • Digital Imaging • GIS • GPS • osgEarth • Terrain • Telemetry • Cryptography • LIDAR • Embedded • Mobile • iPhone/iPad/iOS • Android @alphapixel <https://twitter.com/alphapixel> facebook.com/alphapixel (775) 623-PIXL [7495]

Hello Chris, The requests issue I believe is resolved in the 3.9.2 release. The incorrect path being filled as the default during installation of the 32 bit version is also a known bug, but my understanding was that if you change the path during installation it should operate correctly. If this is not the case then please let me know what issues you saw and I'll test it. I'll also look into the issue with uhd_images_downloader not working correctly due to the archive extension. Regards, Derek On Wed, Jan 6, 2016 at 11:03 AM, Chris Hanson via USRP-users < usrp-users@lists.ettus.com> wrote: > >> First off, there is a live image that has GNU Radio and UHD already >> installed that you can boot into from a USB stick. Its a pretty nice way to >> try things out without messing with your Windows install: >> >> https://gnuradio.org/redmine/projects/gnuradio/wiki/GNURadioLiveDVD >> >> > Ok, I'll check that out. I was hoping to try out HDSDR. > > >> How new is your B200? If you just got it within the last few months, it >> will not be compatible with the older version of UHD. There was a slight >> hardware change that requires an up to date UHD install. >> > > I just got it in late December. So that must be the conflict. I will see > if there will be a newer binary release of the Balint code. > > I gotta say, the user experience getting started has been kinda rough. > The Ettus UHD driver kit seems to malfunction if not installed into > "C:\Program Files" (some paths seem hard coded to that and can't handle the > "Program Files (x86)" of a typical x64 Windows install). The python scripts > need the "requests" module, but don't install it. They also rely on a > "HOME" environment variable that doesn't exist on Windows. It kinda feels > like nobody has actually used/tested this product on Windows in a long time. > > My actual development will be done on Linux, but as far as being able to > plug it in and try it out on Windows, it's been pretty frustrating. > > -- > Chris 'Xenon' Hanson, omo sanza lettere. Xenon@AlphaPixel.com > http://www.alphapixel.com/ > Training • Consulting • Contracting > 3D • Scene Graphs (Open Scene Graph/OSG) • OpenGL 2 • OpenGL 3 • OpenGL 4 > • GLSL • OpenGL ES 1 • OpenGL ES 2 • OpenCL > Legal/IP • Code Forensics • Digital Imaging • GIS • GPS • > osgEarth • Terrain • Telemetry • Cryptography • LIDAR • Embedded • Mobile • > iPhone/iPad/iOS • Android > @alphapixel <https://twitter.com/alphapixel> facebook.com/alphapixel (775) > 623-PIXL [7495] > > _______________________________________________ > USRP-users mailing list > USRP-users@lists.ettus.com > http://lists.ettus.com/mailman/listinfo/usrp-users_lists.ettus.com > >

 First off, there is a live image that has GNU Radio and UHD
 already installed that you can boot into from a USB stick. Its a
 pretty nice way to try things out without messing with your
 Windows install:

 https://gnuradio.org/redmine/projects/gnuradio/wiki/GNURadioLiveDVD

 How new is your B200? If you just got it within the last few
 months, it will not be compatible with the older version of UHD.
 There was a slight hardware change that requires an up to date UHD
 install.

Hello Chris, definitely try out GQRX (which also happens to be on the GNU Radio live DVD)! It's not as feature-rich as HDSDR, but still pretty nice (I personally always felt a little overwhelmed by all the colorful buttons in HDSDR). Assuming you want to do ham radio: Also, there's been recent discussion[1] on the GNU Radio Mailing List[2] about improving the article on using GNU Radio for Ham radio[3]; maybe you could read over that and contribute? I also remember (done this but once, and it's really a while back) that you could run the "borIP server", which, if I remember correctly, is a GNU Radio application that uses the system-installed GNU Radio/UHD, to talk to the hardware, and use the borIP client in HDSDR to talk to that, solving the extIO dilemma. Best regards, Marcus [1] http://lists.gnu.org/archive/html/discuss-gnuradio/2016-01/msg00036.html [2] https://lists.gnu.org/mailman/listinfo/discuss-gnuradio [3] http://gnuradio.org/redmine/projects/gnuradio/wiki/HamRadio On 06.01.2016 20:03, Chris Hanson via USRP-users wrote: > > > First off, there is a live image that has GNU Radio and UHD > already installed that you can boot into from a USB stick. Its a > pretty nice way to try things out without messing with your > Windows install: > > https://gnuradio.org/redmine/projects/gnuradio/wiki/GNURadioLiveDVD > > > Ok, I'll check that out. I was hoping to try out HDSDR. > > > How new is your B200? If you just got it within the last few > months, it will not be compatible with the older version of UHD. > There was a slight hardware change that requires an up to date UHD > install. > > > I just got it in late December. So that must be the conflict. I will > see if there will be a newer binary release of the Balint code. > > I gotta say, the user experience getting started has been kinda > rough. The Ettus UHD driver kit seems to malfunction if not installed > into "C:\Program Files" (some paths seem hard coded to that and can't > handle the "Program Files (x86)" of a typical x64 Windows install). > The python scripts need the "requests" module, but don't install it. > They also rely on a "HOME" environment variable that doesn't exist on > Windows. It kinda feels like nobody has actually used/tested this > product on Windows in a long time. > > My actual development will be done on Linux, but as far as being > able to plug it in and try it out on Windows, it's been pretty > frustrating. > > -- > Chris 'Xenon' Hanson, omo sanza lettere. Xenon@AlphaPixel.com > http://www.alphapixel.com/ > Training • Consulting • Contracting > 3D • Scene Graphs (Open Scene Graph/OSG) • OpenGL 2 • OpenGL 3 • > OpenGL 4 • GLSL • OpenGL ES 1 • OpenGL ES 2 • OpenCL > Legal/IP • Code Forensics • Digital Imaging • GIS • GPS • > osgEarth • Terrain • Telemetry • Cryptography • LIDAR • Embedded • > Mobile • iPhone/iPad/iOS • Android > @alphapixel <https://twitter.com/alphapixel> facebook.com/alphapixel > <http://facebook.com/alphapixel> (775) 623-PIXL [7495] > > > _______________________________________________ > USRP-users mailing list > USRP-users@lists.ettus.com > http://lists.ettus.com/mailman/listinfo/usrp-users_lists.ettus.com