The firmware image on your usrp device is too old and needs updating as 
reflected by the message:


Expected protocol compatibility number [10 to 12], but got 7:


Download the firmware images for 3.11 and install onto device...


Or run the command that is suggested in the error message...


> On April 11, 2018 at 9:27 AM Jason Matusiak via USRP-users 
> <usrp-users@lists.ettus.com> wrote:
> 
>     I have been fighting for a day with issues on my N200s and N210s to no 
> avail. These were working units, but are giving me the following:
>     $ uhd_usrp_probe 
>     [INFO] [UHD] linux; GNU C++ version 4.8.5 20150623 (Red Hat 4.8.5-16); 
> Boost_105300; UHD_3.11.0.0-34-g4844f66d
>     [ERROR] [UHD] Exception caught in safe-call.
>       in virtual usrp2_iface_impl::~usrp2_iface_impl()
>       at /home/jmat/GR/src/uhd/host/lib/usrp/usrp2/usrp2_iface.cpp:81
>     this->lock_device(false); -> RuntimeError: 
>     Please update the firmware and FPGA images for your device.
>     See the application notes for USRP2/N-Series for instructions.
>     Expected protocol compatibility number [10 to 12], but got 7:
>     The firmware build is not compatible with the host code build.
>     Please run:
> 
>      "/home/jmat/GR/lib64/uhd/utils/uhd_images_downloader.py"
>      "/home/jmat/GR/bin/uhd_image_loader" \
>         --args="type=usrp2,addr=192.168.10.2"
> 
>     [INFO] [USRP2] Opening a USRP2/N-Series device...
>     [ERROR] [UHD] Exception caught in safe-call.
>       in virtual usrp2_iface_impl::~usrp2_iface_impl()
>       at /home/jmat/GR/src/uhd/host/lib/usrp/usrp2/usrp2_iface.cpp:81
>     this->lock_device(false); -> RuntimeError: 
>     Please update the firmware and FPGA images for your device.
>     See the application notes for USRP2/N-Series for instructions.
>     Expected protocol compatibility number [10 to 12], but got 7:
>     The firmware build is not compatible with the host code build.
>     Please run:
> 
>      "/home/jmat/GR/lib64/uhd/utils/uhd_images_downloader.py"
>      "/home/jmat/GR/bin/uhd_image_loader" \
>         --args="type=usrp2,addr=192.168.10.2"
> 
>     Error: RuntimeError: 
>     Please update the firmware and FPGA images for your device.
>     See the application notes for USRP2/N-Series for instructions.
>     Expected protocol compatibility number [10 to 12], but got 7:
>     The firmware build is not compatible with the host code build.
>     Please run:
> 
>      "/home/jmat/GR/lib64/uhd/utils/uhd_images_downloader.py"
>      "/home/jmat/GR/bin/uhd_image_loader" \
>         --args="type=usrp2,addr=192.168.10.2"
> 
> 
>     I have this issue with a bunch of devices that have been sitting on my 
> shelf for a while. Is it too old to do the upgrade and I need to do some sort 
> of intermediate upgrade first? 
> 
>     "./usrp_burn_mb_eeprom --args="addr=192.168.10.2" --read-all" gives the 
> same results as above.
> 
> 
>     Yet I also get this (which shows me that it can kind of see it):
>     $ uhd_find_devices 
>     [INFO] [UHD] linux; GNU C++ version 4.8.5 20150623 (Red Hat 4.8.5-16); 
> Boost_105300; UHD_3.11.0.0-34-g4844f66d
>     [ERROR] [UHD] Exception caught in safe-call.
>       in virtual usrp2_iface_impl::~usrp2_iface_impl()
>       at /home/jmat/GR/src/uhd/host/lib/usrp/usrp2/usrp2_iface.cpp:81
>     this->lock_device(false); -> RuntimeError: 
>     Please update the firmware and FPGA images for your device.
>     See the application notes for USRP2/N-Series for instructions.
>     Expected protocol compatibility number [10 to 12], but got 7:
>     The firmware build is not compatible with the host code build.
>     Please run:
> 
>      "/home/jmat/GR/lib64/uhd/utils/uhd_images_downloader.py"
>      "/home/jmat/GR/bin/uhd_image_loader" \
>         --args="type=usrp2,addr=192.168.10.2"
> 
>     --------------------------------------------------
>     -- UHD Device 0
>     --------------------------------------------------
>     Device Address:
>         serial: 
>         addr: 192.168.10.2
>         name: 
>         type: usrp2
> 
> 
>     Pings to its IP work fine. But when I run one of the commands and watch 
> it via wireshark, I see that every packet from my N210 is coming up with a 
> "ETHERNET FRAME CHECK SEQUENCE INCORRECT". That could be an issue, or it 
> could be something that always happens and I can ignore it in this care.
> 
>     Is there anyway to revive these units????
> 


 

> _______________________________________________
>     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

Reply via email to