No worries. It may be helpful to run the target-*/calculate...
executable on the .out files for both the ADC and DAC tests to observe
whether the data looks like reasonable LFSR data. Check the arguments
on that executable, there should be an option for printing out the
0s/1s which make LFSR behavior obvious. It's also useful to parse the
output for, e.g. "1 of which had bit errors"
---------- Forwarded message ---------
From: Brian Padalino <bpadalino_at_gmail.com>
Date: Fri, Apr 3, 2020 at 2:08 PM
Subject: Re: [Discuss OpenCPI] Fwd: AD9361 ADC/DAC Test Applications
To: Davis Hoover <dhoover_at_geontech.com>
Cc: <discuss_at_lists.opencpi.org>
On Fri, Apr 3, 2020 at 1:54 PM Davis Hoover <dhoover_at_geontech.com> wrote:
>
> These tests use the ad9361_config_proxy.rcc which require setting the
> delays to a known-good value. This has been exemplified in a separate BSP
> project, which does work correctly:
> https://gitlab.com/opencpi/osp/ocpi.osp.e3xx/-/blob/develop/applications/ad9361_adc_test/scripts/run_app.sh#L97
> Are these values being set correctly for your platform?
I am setting them according to a known good set for this radio from a
different application that was run on it.
Regardless, my confusion stems from why both the ADC and DAC tests
which use the PRBS show 30% BER, but the DAC tests which do not use
the PRBS but still use the TX and RX paths show 0% BER.
My thought is that if the RX-only path doesn't work, why would the TX path?
Sorry for the confusion. Still perplexed.
Thanks,
Brian
Received on Fri Apr 03 2020 - 18:16:22 CDT