Hi Mark,
Board revision is relatively easy to narrow down: is your board white or green? If green,
yeah, 5, very likely.
> Is there any way to debug what the issue truly is?
going to be hard; usually, this is the point where we honestly say we can't.
Just to give you an understanding, 5 == FX3_STATE_UNCONFIGURED. You can find all the paths
where that can in b200_main.c in the uhd/firmware source tree. This might be something as
fundamental as the FPGA never signalling it finished programming. That would usually
indicate a hardware failure that *might* be fixable by reworking the board, or by
replacing the FPGA, or replacing the FX3, or by something else.
Sorry,
Marcus
On 01.07.24 15:39, Mark Rosenbaum wrote:
Darn, that's really unfortunate. Is there any way to debug what the issue
truly is?
--
Mark
------------------------------------------------------------------------------------------
*From:* Martin Braun <martin.br...@ettus.com>
*Sent:* Monday, July 1, 2024 3:52 AM
*To:* Mark Rosenbaum <m_ro...@mit.edu>
*Cc:* usrp-users@lists.ettus.com <usrp-users@lists.ettus.com>
*Subject:* Re: [USRP-users] Bricked B210 due to wiped EEPROM
Sorry, that error can mean a bunch of things. It might be faulty hardware,
unfortunately.
--M
On Fri, Jun 28, 2024 at 6:19 PM Mark Rosenbaum <m_ro...@mit.edu> wrote:
Martin,
I actually re-ran the command you asked me too again just to make sure and
I have a
different error now!(Not sure if that's good or bad though.) The new error
is
actually my original error I was trying to fix which got me into this whole
mess.
The message is "Error: RuntimeError: fx3 is in state 5". Any idea where to
go
from here?
--
Mark
------------------------------------------------------------------------------------------
*From:* Martin Braun <martin.br...@ettus.com>
*Sent:* Friday, June 28, 2024 12:12 PM
*To:* Mark Rosenbaum <m_ro...@mit.edu>
*Cc:* usrp-users@lists.ettus.com <usrp-users@lists.ettus.com>
*Subject:* Re: [USRP-users] Bricked B210 due to wiped EEPROM
Yeah that's probably the last resort. Just hard-code all product IDs and
whatnot
until it works. Good luck!
--M
On Fri, Jun 28, 2024 at 5:52 PM Mark Rosenbaum <m_ro...@mit.edu> wrote:
Martin,
Just tried exactly that to no avail. Gives the exact same error. Is
there any
way to maybe modify the program and recompile to bypass error/product
code
checking? It looks to me like the check is found on line 149 of
b200_impl.cpp(https://github.com/EttusResearch/uhd/blob/a5ed1872be6d0fc36de9a7e0b508933da1f119bc/host/lib/usrp/b200/b200_impl.cpp#L149C1-L149C3),
but
I may be wrong.
--
Mark
------------------------------------------------------------------------------------------
*From:* Martin Braun <martin.br...@ettus.com>
*Sent:* Friday, June 28, 2024 11:42 AM
*To:* Mark Rosenbaum <m_ro...@mit.edu>
*Subject:* Re: [USRP-users] Bricked B210 due to wiped EEPROM
Try specifying absolutely everything on the command line:
|./usrp_burn_mb_eeprom --args="fpga=/path/to/fpga/usrp_b210_fpga.bin"
--values
revision=<REV>,product=<PRODUCT_ID>,serial=<SERIAL>,name="b200name" |
|Serial number is on the PCB. PRODUCT_ID is 1, I think for B210 (see
|https://github.com/EttusResearch/uhd/blob/master/host/lib/usrp/b200/b200_iface.hpp#L20).
Revision is encoded somewhere on the PCB, I'm not sure -- just put 5 here and
see if things work. Name is up to you of course.
The most important thing is the correct FPGA bin-file.
--M
On Fri, Jun 28, 2024 at 3:05 PM Mark Rosenbaum <m_ro...@mit.edu> wrote:
Hey Martin,
Tried that as almost a first thing after the issue occurred. The
command
successfully runs with no error but the same issue persists, where
any other
command gives me the "Error: RuntimeError: B200 unknown product
code:
0xe3e0" message.
--
Mark
------------------------------------------------------------------------------------------
*From:* Martin Braun <martin.br...@ettus.com>
*Sent:* Friday, June 28, 2024 5:26 AM
*To:* Mark Rosenbaum <m_ro...@mit.edu>
*Cc:* usrp-users@lists.ettus.com <usrp-users@lists.ettus.com>
*Subject:* Re: [USRP-users] Bricked B210 due to wiped EEPROM
Hi Mark,
b2xx_fx3_utils --init-device is your friend. After you run that,
you can run
`usrp_burn_mb_eeprom` again to configure serial number etc.
--M
On Thu, Jun 27, 2024 at 8:45 PM Mark Rosenbaum <m_ro...@mit.edu>
wrote:
Hi All,
I was recently working on fixing an issue with my B210 and
accidentally
re-flashed the bootloader. In the process it seems to have
fully wiped
the EEPROM and now when attempting to perform any action on the
device I
get the following error:
"Error: RuntimeError: B200 unknown product code: 0xe3e0".
Is there any way to go back and re-flash the original values?
I've
tried to use the usrp_burn_mb_eeprom command with the
recover_mb_eeprom
but it still fails with the same error.
Thanks,
Mark
_______________________________________________
USRP-users mailing list -- usrp-users@lists.ettus.com
To unsubscribe send an email to usrp-users-le...@lists.ettus.com
_______________________________________________
USRP-users mailing list --usrp-users@lists.ettus.com
To unsubscribe send an email tousrp-users-le...@lists.ettus.com
_______________________________________________
USRP-users mailing list -- usrp-users@lists.ettus.com
To unsubscribe send an email to usrp-users-le...@lists.ettus.com
