ADRV9002 Frequency hopping in FDD with independent LOs

You can not control 2 LOs with 2 hop tables with separate GPIO pins. One way to test different configurations is with the TES tool. If the TES tool does not allow for the configuration then it is not a valid configuration.

Hi, 

Is it possible to remain in FDD mode and frequency hop the transmitter and receiver to same LO frequency?

Thanks,

Allen

Hi Allen,

Frequency hopping is not supported in FDD mode. However, you can emulate the behavior of FDD in TDD mode by configuring the frequency hopping to Dual HOP mode. In this setup, both channels operate independently, allowing you the flexibility to assign any local oscillator (LO) to either channel.

Regards

Rahul

Hi Rahul,

Thanks for your response. I will try this out in the TES. So in this mode, could we hop our LOs and TX and RX at same time? I want to accomplish an RF loopback while hopping.

Thanks,

Allen

I was able to put in "TDD" mode, and then set pin mode and RX ENABLE and TX ENABLE pins high, and do an rf loopback using only LO one at a fixed frequency.   Can I just change to hopping and do the same thing? I see for hopping that the RX ENABLE and TX ENABLE pins are repurposed as the channel setup pins.  If I do a rising edge on both, before the hop timing signal, can i retune that LO1 , and keep both rx and tx paths enabled and do rf loopback?

I was able to put in "TDD" mode, and then set pin mode and RX ENABLE and TX ENABLE pins high, and do an rf loopback using only LO one at a fixed frequency.   Can I just change to hopping and do the same thing? I see for hopping that the RX ENABLE and TX ENABLE pins are repurposed as the channel setup pins.  If I do a rising edge on both, before the hop timing signal, can i retune that LO1 , and keep both rx and tx paths enabled and do rf loopback?

Replied in this thread: Frequency Hopping in ADRV9002 - Q&A - Design Support ADRV9001 – ADRV9007 - EngineerZone 

Ok thank you. As of now though, I can't receive or transmit anything when trying to frequency hop. I'm toggling the hop signal, and using the Rx_Enable as the channel setup signal. I'm seeing all zeroes out of the adrv9002 ip core at the adc ports.

Hi, 

Are you sing the EVAL board or the custom board?and are you using TES to configure it?

Regards

Rahul

Custom board. I'm using the TES to create the json and generate the example C code. Then I am plugging the example C code in the zcu102 no-os headless example. 

I am able to transmit and receive at a fixed frequency. But when I update my json to (fhModeOn=1), then I run into problem where I don't see the ADC output any IQ data other than zeros. I'm calling the two functions to setup FH... 1) api_call(phy, adi_adrv9001_fh_Configure, &fhConfig_49); and 2) di_adrv9001_fh_HopTable_Static_Configure(phy->adrv9001, ADI_ADRV9001_FHMODE_LO_MUX_REALTIME_PROCESS, ADI_ADRV9001_FH_HOP_SIGNAL_1, ADI_ADRV9001_FHHOPTABLE_A, hopTable_50, 4).

I'm toggling the hop signal at a 5 ms rate. I'm just trying receive only for now, using the rx2_enable signal as the channel setup signal. I put rx2_enable high 30 us before hop toggles. and I put it back low 30 us after the hop toggles.

But adc doesn't seem to be outputting any data. Running on a custom board, no-os.

Please advise.

Thanks!

Hi Allen,

In my understanding, you are seeing these issues on a custom board.
Please try recreate these issues on the EVAL board if you can.

If these issues still persist, we can look deeper into this, as we would have a common debugging platform.

Regards,
Deniss

Hi Deniss,

I currently do not have access to EVAL board. However, when calling the  adi_adrv9001_fh_HopTable_Inspect() function, I noticed that I wasn't getting anything back. Digging into the no-os software some, I realized that I missed an update to the adi_hal_SpiWrite() function for my hardware. Once I did that, I am know able to see the frequency hopping occuring.

Also, I am able to run this in rf loopback and transmit and receive at same time while hopping. I am pulsing both the rx_setup and tx_setup signals at same time.

Thanks,

Allen