Post Go back to editing

Linux driver - RF_ENABLED in TDD mode using SPI

Thread Summary

The user is using a TDD profile with RX1 and RX2 generated through TES and a Linux driver, configuring RX enable via SPI. The device remains in 'PRIMED' state until manually switched to 'RF_ENABLED' using the iio_attr binary. This is expected behavior in TDD mode, as the driver cannot determine whether to enable RX or TX first, unlike in FDD mode where the driver automatically sets the state to 'RF_ENABLED'.
AI Generated Content
Category: Software
Product Number: ADRV9002

Hello!

We are using TDD profile with RX1 and RX2 generated through TES and linux driver (not the API). RX enable is configured to be via SPI.

I noticed that mode stays in "PRIMED" until I manually switch it to RF_ENABLED using iio_attr binary from libiio.

Is this expected way of activating RX or should driver move RX mode to RF_ENABLED state automatically? I thought driver should take care of this but it never happens.

Am I missing some configuration or is this the way is should behave?

Thank you!

Thread Notes