Thank you for the response, Michael.
From: Michael West
Date: Thursday, October 12, 2017 at 4:57 PM
To: Mark Koenig
Cc: "usrp-users@lists.ettus.com"
Subject: Re: [USRP-users] ADC Self-Test FAILED
Hi Mark,
It is the simplest. You can always play around with the source code to commen
this the only resolution?
>
>
>
> Thank you
>
>
>
>
>
> Mark
>
>
>
> *From: *Michael West
> *Date: *Tuesday, October 10, 2017 at 4:00 PM
> *To: *Mark Koenig
> *Cc: *"usrp-users@lists.ettus.com"
> *Subject: *Re: [USRP-users] ADC Self-
Thank you for the follow up. Is this the only resolution?
Thank you
Mark
From: Michael West
Date: Tuesday, October 10, 2017 at 4:00 PM
To: Mark Koenig
Cc: "usrp-users@lists.ettus.com"
Subject: Re: [USRP-users] ADC Self-Test FAILED
Hi Mark,
Update UHD to a newer version. The h
Hi Mark,
Update UHD to a newer version. The head of the maint branch or the latest
3.10.2.0 release should work. The ADC self test is skipped when supplying
"recover_mb_eeprom" as of UHD 3.10.0.0.
Regards,
Michael
On Tue, Oct 10, 2017 at 12:32 PM, Mark Koenig via USRP-users <
usrp-users@lists.
Just following up on the message I sent out 8 days ago. Does anyone have any
resolution to this issue? I have seen other people have the problem, but have
yet to find a fix.
Thanks
Mark
From: Mark Koenig
Date: Monday, October 2, 2017 at 10:18 AM
To: "usrp-users@lists.ettus.com"
Subject: AD
All,
I am getting the following output when trying to recover the mb EEprom. Can
anyone be of assistance?
Thank you
Mark
[root@localhost utils]# ./usrp_burn_mb_eeprom
--args="recover_mb_eeprom,addr=192.168.20.2" --values="revision=4"
linux; GNU C++ version 4.8.5 20150623 (Red Hat 4.8.5-16)
Hi Sam,
Can you please email into supp...@ettus.com. We can debug further off the
mailing list.
Regards,
Nate
> On Jul 6, 2017, at 8:39 AM, Sam Vogel wrote:
>
> Hi Nate,
>
> Sure, our company is using a custom UHD and I will have to redact part of the
> text. When I run the command it outp
Hi Nate,
Sure, our company is using a custom UHD and I will have to redact part of
the text. When I run the command it outputs:
003.009.001**
This x300 has always been problematic. We have a different X300 that works
fine with this setup. The problem occurs when I duplicate the setup for use
with
