Hi Roland,
There are options available to the ad9361 to run it in internal loopback
but this application does exercise those register options.
Does it produce a valid image with the output file with no data
degradation? Several things are going on here. In the case that it is
invalid file, the writing to file occurs when it receives 0xFACE in hex ,
and we've found that it could occur randomly in noise fairly easily, which
could explain the creation of the data file. If it is valid, there could be
some leakage between TX and RX ports internal to the E310, the RX gain is
set to AUTO in this application which could be maxing out the RX gain
enough to pick up the leakage.
Try setting RX gain to manual, and/or lowering the TX gain even further.
Aaron
On Tue, Oct 17, 2023 at 4:46 AM roland.johnson--- via discuss <
discuss_at_lists.opencpi.org> wrote:
> Hi Aaron,
>
> I just ran the fsk_dig_radio_ctrlr application using the command you
> suggested and it worked fine. So very good to know I can deploy projects to
> the E310 in standalone mode with the correct artifacts in the correct
> location, with the correct library paths!
>
> One thing however - I’m able to generate and read the output file <
> fsk_dig_radio_ctrlr_fmcomms_2_3_txrx.bin > even if I don’t connect anything
> to the TX or RX ports of the Ettus. I guess there’s the option to run the
> application using some internal loopback only, or should it always run
> using the AD9361 ADC & DAC?
>
> If the latter, do I need to change the “ocpirun†command with different
> arguments to specifically target the TX and RX ports?
>
> Best,
> Roland
> _______________________________________________
> discuss mailing list -- discuss_at_lists.opencpi.org
> To unsubscribe send an email to discuss-leave_at_lists.opencpi.org
>
Received on Tue Oct 17 2023 - 13:21:34 CDT