Quite likely means that your EEPROM is damaged in some way.
Sent from my iPhone
> On Sep 12, 2019, at 10:04 PM, Javier Uranga wrote:
>
> Thank you Guys,
>
> I received a Magic word
>
> sudo /path/to/fx2_init_eeprom --type b100 --vid 04b4 --pid 8613
>
> And it's worked perfect
>
Thank you Guys,
I received a Magic word
sudo /path/to/fx2_init_eeprom --type b100 --vid 04b4 --pid 8613
And it's worked perfect
Now my old USRP B100 is alive again!
But when I power off/on the device I must to repeat the process, because
the eeprom do not remain loaded
just in case,
I recall this used to happen to some B100s.
There’s an EEPROM writer command, I think, that can restore the correct
identity.
These devices are quite obsolete now, so don’t get your hopes up too much.
I’m in the road at the moment and won’t be back until Friday. I should be able
to dig up t
Does this help?
https://kb.ettus.com/Building_and_Installing_the_USRP_Open-Source_Toolchain_(UHD_and_GNU_Radio)_on_Linux#Configuring_USB
On Wed, Sep 11, 2019 at 1:08 PM Javier Uranga via USRP-users <
usrp-users@lists.ettus.com> wrote:
> Dear Members in the List,
>
> I'm working with an old USRP B
Dear Members in the List,
I'm working with an old USRP B100 that came with a cubesat development kit,
Now suddenly stop working, no longer respond to:
uhd_find_devices
linux; GNU C++ version 5.3.1 20151219; Boost_105800;
UHD_003.009.002-0-unknown
No UHD Devices Found
uhd_usrp_probe
linux; GN
