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 <smvogel...@gmail.com> 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 outputs:
> 003.009.001<this-is-redacted>
> 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 our second X300. We need the second setup running also. I have never
> updated the UHD.
> Hopefully this is helpful, I assume our custom UHD is built from 003.009.001.
>
> Thanks so much,
> Sam
>
> On Thu, Jul 6, 2017 at 1:12 AM, Nate Temple <nate.tem...@ettus.com> wrote:
> Hi Sam,
>
> Can you run the following command send what it's output is? This will print
> out the exact version of UHD you're using: uhd_usrp_probe --version
>
> My second question was if you have changed any thing with your setup since
> the X300 has became problematic ? Have you updated the UHD version at all
> recently?
>
> Regards,
> Nate Temple
>
>
> > On Jul 5, 2017, at 9:10 PM, Sam Vogel <smvogel...@gmail.com> wrote:
> >
> > Hi Nate,
> >
> > Yes, there is a uhd_usrp_probe program in /examples/utils, perhaps this
> > means I'm using the 'uhd_usrp_probe' version? I can get more info on this
> > tomorrow when I'm in the office. We have two different X300 boards, let's
> > call them X300A and X300B. Each are a different H/W revision. We have been
> > using X300A for a while and the problem now occurs when I try to use X300B
> > with the same code base we use for X300A. The main difference in the setups
> > is the X300 board itself. A lot of the code we use is custom and I don't
> > know if starting from a fresh copy of the Ettus repository is feasible.
> >
> > Thanks,
> > Sam
> >
> > On Wed, Jul 5, 2017 at 8:29 PM, Nate Temple <nate.tem...@ettus.com> wrote:
> > Hi Sam,
> >
> > Which version of UHD are you using? (uhd_usrp_probe --version)
> >
> > Have you recently updated UHD, or has anything changed in your setup from
> > when it was previously work to now?
> >
> > Regards,
> > Nate Temple
> >
> > On Wed, Jul 5, 2017 at 3:08 PM, Sam Vogel via USRP-users
> > <usrp-users@lists.ettus.com> wrote:
> > Hi,
> >
> > This happens every time.
> >
> > Thanks,
> > Sam
> >
> > On Wed, Jul 5, 2017 at 6:01 PM, Martin Braun via USRP-users
> > <usrp-users@lists.ettus.com> wrote:
> > Does this happen intermittently? Or every time?
> >
> > -- M
> >
> > On 06/13/2017 01:55 PM, Sam Vogel via USRP-users wrote:
> > > Hi All, I’m running into an issue with our x300 revision E. Any help
> > > resolving this is greatly appreciated.
> > >
> > > Following the procedure to recover the EEPROM yields a problem.
> > >
> > > [vogels@lprbld12 utils]$ ./usrp_burn_mb_eeprom
> > > --args="recover_mb_eeprom,addr=192.167.10.111" --values="revision=5"
> > >
> > > Creating USRP device from address: recover_mb_eeprom,addr=192.167.10.111
> > >
> > > -- X300 initialization sequence...
> > >
> > > -- Determining maximum frame size... 8000 bytes.
> > >
> > > -- Setup basic communication...
> > >
> > > -- Loading values from EEPROM...
> > >
> > >
> > >
> > > UHD Warning:
> > >
> > > UHD is operating in EEPROM Recovery Mode which disables hardware
> > > version checks.
> > >
> > > Operating in this mode may cause hardware damage and unstable radio
> > > performance!
> > >
> > > -- Setup RF frontend clocking...
> > >
> > >
> > >
> > > UHD Warning:
> > >
> > > Environment variable 'USRP_X300_REFERENCE_CLOCK_RATE_HZ' not found,
> > > defaulting to reference clock rate of 10000000.000000 Hz
> > >
> > > -- Using specified reference / master clock rates of 10.0 / 200.0 MHz
> > >
> > > -- Radio 1x clock:200
> > >
> > > -- Initialize Radio0 control...
> > >
> > > -- Performing register loopback test... pass
> > >
> > > -- Initialize Radio1 control...
> > >
> > > -- Performing register loopback test... pass
> > >
> > > Error: RuntimeError: ADC self-test failed! Ramp checker status:
> > > {ADC0_I=Bit Errors!, ADC0_Q=Bit Errors!, ADC1_I=Good, ADC1_Q=Good}
> > >
> > >
> > >
> > > Thanks !
> > >
> > > -Sam
> > >
> > >
> > >
> > > _______________________________________________
> > > USRP-users mailing list
> > > USRP-users@lists.ettus.com
> > > http://lists.ettus.com/mailman/listinfo/usrp-users_lists.ettus.com
> > >
> >
> >
> > _______________________________________________
> > USRP-users mailing list
> > USRP-users@lists.ettus.com
> > http://lists.ettus.com/mailman/listinfo/usrp-users_lists.ettus.com
> >
> >
> > _______________________________________________
> > USRP-users mailing list
> > USRP-users@lists.ettus.com
> > http://lists.ettus.com/mailman/listinfo/usrp-users_lists.ettus.com
> >
> >
> >
>
>
_______________________________________________
USRP-users mailing list
USRP-users@lists.ettus.com
http://lists.ettus.com/mailman/listinfo/usrp-users_lists.ettus.com
