We are using ADRV9002 RF Transceiver for our applications. Is it possible to achieve the loopback operation in Frequency Hopping mode in ADRV9002, if it so please provide the configurations modes that need to be set.
I'll take a look into this and report back to you. My suspicion is that FH cannot be used with a loopback as FH is typically used with TDD, which precludes the separation of Tx and Rx on a time basis.
I'll return when I've investigated further!
Thanks for your response. We achieved Frequency Hopping in Tx channel of ADRV9002, but couldn't achieve Frequency hopping in Rx channel. Can you please provide me configurations or modes that need to set to achieve hopping in Rx channel.
Frequency Hopping shouldn't discriminate between Tx and Rx channels as it acts on the channel LO. Controlling Hopping times and channel assignment is best achieved in the Auto TDD tab. In the following images I setup a simple LTE demonstration. I use two frequency hopping tables provided with TES in the Examples folder. I then enable Auto TDD and use the corresponding Auto TDD timings. There are a set of extra signals provided with this table that are used to trigger external equipment captures and provide a means for the user to keep track of the frame as it cycles.
Do let me know if this info helps you get further in your development!
I was developing Frequency Hopping in ADRV9002 with 1 Frequency table in it. While Frequency hopping is going on, if I provide an interrupt, my hopping should start from initial frequency of table. Is there any API available to do so?
Hi Vijay KS,
I'm not familiar with every API provided for Frequency Hopping, your best bet for finding every API you'll need is to navigate to the production/ folder of the SDK and open the Compressed HTML document. This document contains descriptions and requirements for every public API we provide.
Off the top of my head, the answer will depend of the Table Index Control method you select:
With either Ping Pong or Loop you are offloading the indexing control to the on-board ARM, which saves you having to control the index yourself but also means you can't control it quite as finely. However with GPIO, control of indexing is kept by the FPGA or BBIC, meaning you can provide an interrupt to your FPGA/BBIC and have it restart the Hopping index very easily. This comes at the cost of additional computing responsibility on the FPGA/BBIC.
Do let me know if this helped at all!