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 <javier...@gmail.com> 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 > > 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, do you have any other magic word ? to make the changes > permanently > > Best Regards > Javier > >> El mié., 11 sept. 2019 a las 20:55, Marcus D Leech >> (<patchvonbr...@gmail.com>) escribió: >> 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 the magic incantations after then. Unless some other Ettus >> old-timer remembers the correct spell. >> >> >> Sent from my iPhone >> >>> On Sep 11, 2019, at 6:27 PM, Robin Coxe via USRP-users >>> <usrp-users@lists.ettus.com> wrote: >>> >>> 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 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; GNU C++ version 5.3.1 20151219; Boost_105800; >>>> UHD_003.009.002-0-unknown >>>> Error: LookupError: KeyError: No devices found for -----> >>>> Empty Device Address >>>> >>>> I must to say that, until few minutes before, the device showed no >>>> problems, but after a switch OFF/ON the device, problems came up >>>> >>>> And when I ask: >>>> >>>> $lsusb >>>> the device found is: >>>> Bus 003 Device 003: ID 04b4:8613 Cypress Semiconductor Corp. CY7C68013 >>>> EZ-USB FX2 USB 2.0 Development Kit >>>> >>>> As you can see, the detected device is not longer Ettus USRP as use to be. >>>> More over, in the front panel, new led is on, there is a new led in ON >>>> status, the LED B: FPGA loaded >>>> (in addition to: >>>> LED A: transmitting, ON >>>> LED C: receiving, ON >>>> LED D: FPGA loaded, OFF >>>> LED E: reference lock, ON >>>> LED F: board power, ON ) >>>> >>>> I already re installed the GNU RADIO 3.7.9 drivers for Ubuntu 16.04 and >>>> GNU RADIO 3.7.11 for Ubuntu 18.04, all systems where it use to work, But >>>> the USRP is no longer detected. >>>> >>>> drivers in Ubuntu 16.04: >>>> /usr/share/uhd/images$ ls >>>> usrp_b100_fw.ihx >>>> usrp_b100_fpga.bin >>>> >>>> What can be wrong ?, it's Firmware problem ? >>>> How can I solve it? >>>> >>>> I'll be very grateful with any comments or suggestions >>>> >>>> Best Regards, >>>> Javier Nicolas >>>> _______________________________________________ >>>> 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
_______________________________________________ USRP-users mailing list USRP-users@lists.ettus.com http://lists.ettus.com/mailman/listinfo/usrp-users_lists.ettus.com
