Hi! This is what appears:
itupac@itupac:/usr/local/lib/uhd/utils$ ./usrp_burn_mb_eeprom --args "addr=192.168.10.3" --read-all Creating USRP device from address: addr=192.168.10.3 [INFO] [UHD] linux; GNU C++ version 7.4.0; Boost_106501; UHD_3.14.0.HEAD-0-g6875d061 [INFO] [USRP2] Opening a USRP2/N-Series device... [INFO] [USRP2] Current recv frame size: 1472 bytes [INFO] [USRP2] Current send frame size: 1472 bytes [WARNING] [USRP2] Unable to identify device - assuming USRP2/N-Series device [WARNING] [UHD] Unable to set the thread priority. Performance may be negatively affected. Please see the general application notes in the manual for instructions. EnvironmentError: OSError: error in pthread_setschedparam Fetching current settings from EEPROM... EEPROM ["hardware"] is "" EEPROM ["revision"] is "" EEPROM ["product"] is "" EEPROM ["mac-addr"] is "00:00:00:00:40:00" EEPROM ["ip-addr"] is "192.168.10.3" EEPROM ["subnet"] is "0.0.0.104" EEPROM ["gateway"] is "255.255.255.255" EEPROM ["gpsdo"] is "none" EEPROM ["serial"] is "0" EEPROM ["name"] is "" Power-cycle the USRP device for the changes to take effect. Done [WARNING] [UHD] Unable to set the thread priority. Performance may be negatively affected. Please see the general application notes in the manual for instructions. EnvironmentError: OSError: error in pthread_setschedparam El vie, 22 oct 2021 a las 12:33, Marcus D. Leech (<patchvonbr...@gmail.com>) escribió: > On 2021-10-22 11:33 a.m., isaac mario tupac davila wrote: > > Using Device: Single USRP: > > Device: USRP2 / N-Series Device > > Mboard 0: N??? > > RX Channel: 0 > > RX DSP: 0 > > RX Dboard: A > > RX Subdev: BasicRX (AB) > > TX Channel: 0 > > TX DSP: 0 > > TX Dboard: A > > TX Subdev: Unknown (0xffff) - 0 > > If you look here: > > Using Device: Single USRP: > Device: USRP2 / N-Series Device > Mboard 0: N??? > RX Channel: 0 > RX DSP: 0 > RX Dboard: A > RX Subdev: BasicRX (AB) > TX Channel: 0 > TX DSP: 0 > TX Dboard: A > TX Subdev: Unknown (0xffff) - 0 > > You can see that it's unable to clearly identify what type of device > this is. This implies that the motherboard EEPROM contains invalid data. > > What happens if you: > > /usr/lib/uhd/utils/usrp_burn_mb_eeprom --args "addr=192.168.10.2" > --read-all > > Or substitute whatever IP address your device has. > > > > > >