On 08/08/2023 10:57, [email protected] wrote:
Dear Marcus,
I very much appreciate your help, that makes sense, it was probably
the cause…
In regards to the bootloader image that includes EEPROM values that
you pointed out, I am going to look into the files.ettus.com/
<https://files.ettus.com/> to see if I can find any suitable image.
Regards,
Eden.
_______________________________________________
USRP-users mailing list [email protected]
To unsubscribe send an email [email protected]
Loking at he code for b200_fx3_utils, it doesn't appear possible for it
to do what happened to you--it won't let you load an
image that is large enough to clobber the upper 256 bytes of EEPROM,
which is where the critical EEPROM variables are
stored.
It MIGHT be the case that it loaded that bogus bootloader, started
executing it, and through some miracle, that code actually
overwrote the top 256 bytes of the 32KB EEPROM that is on the B200.
_______________________________________________
USRP-users mailing list -- [email protected]
To unsubscribe send an email to [email protected]
