On 08/08/2023 09:36, [email protected] wrote:
Dear Marcus,
When I type that, it prints the same run-time error:
|./usrp_burn_mb_eeprom —read-all|
*Creating USRP device from address: *
*[INFO] [UHD] linux; GNU C++ version 11.3.0; Boost_107400; DPDK_21.11;
UHD_4.3.0.0-release*
*Error: RuntimeError: B200 unknown product code: 0x3120*
What’s interesting is the device firmware can be loaded with power
cycle but the same error persists throughout the UHD utilities and
usrp related code.
I think the desired output should be similar to the following as
provided on About the Motherboard and Daughtercard EEPROM on USRP
Devices
<https://kb.ettus.com/About_the_Motherboard_and_Daughtercard_EEPROM_on_USRP_Devices>
under B200/210 and B200mini EEPROM:
Fetching current settings from EEPROM... EEPROM ["revision"] is "4"
EEPROM ["product"] is "2" EEPROM ["serial"] is "30AD2D4" EEPROM
["name"] is "MyB210"
Regards,
Eden.
_______________________________________________
USRP-users mailing list [email protected]
To unsubscribe send an email [email protected]
I think the basic problem is that when you had it load up that FPGA
image as the FX3 bootloader image, the EEPROM values were
over-written--the FX3 "load me a new bootloader" code has no idea
what the internal semantics are.
The .img file that Ettus ships in ...uhd/images doesn't include values
for the EEPROM (which makes sense, because they're
set at the factory).
I'm trying to find out if there's a bootloader image that includes
"sane" values for the EEPROM that can be loaded using
fx3_utils.
_______________________________________________
USRP-users mailing list -- [email protected]
To unsubscribe send an email to [email protected]
