AnsweredAssumed Answered

AD9361 No-OS API

Question asked by Paul.T. on Apr 2, 2014
Latest reply on Apr 2, 2014 by Paul.T.

Is there a sensible reason for this switching of fdd and rx2tx2 parameters in the ad9361_init() in ad9361_api.c?

 

/* Base Configuration */

phy->pdata->fdd = init_param->two_rx_two_tx_mode_enable;

phy->pdata->rx2tx2 = init_param->frequency_division_duplex_mode_enable;

....

 

It just looks so obviously wrong,

 

The initialisation of default_init_params in main.c doesn't help, since they are both enabled:

AD9361_InitParam default_init_param = {

    /* Reference Clock */

    40000000UL,    //reference_clk_rate

    /* Base Configuration */

    1,        //two_rx_two_tx_mode_enable *** adi,2rx-2tx-mode-enable

    1,        //frequency_division_duplex_mode_enable *** adi,frequency-division-duplex-mode-enable

...

 

The AD9361_InitParams typedef suggests that the comment in the initialisation is correct, the first Base Configuration parameter is rx2tx2 enable:

typedef struct

{

    /* Reference Clock */

    uint32_t    reference_clk_rate;

    /* Base Configuration */

    uint8_t        two_rx_two_tx_mode_enable;    /* adi,2rx-2tx-mode-enable */

    uint8_t        frequency_division_duplex_mode_enable;    /* adi,frequency-division-duplex-mode-enable */

...

}AD9361_InitParam;

Outcomes