The attached prelim details should help answer the questions.
I'm using an ADRV9009 W/PCBZ board to test AD9009 chipset, and we use IIO Oscilloscope (v0.99) on windows.
After IIO connects to the target board, I can see several devices listed ,
such as: "ad9528-1","adrv9009-phy","axi-adrv9009-tx-hpc"…
I am working on a custom board with ADRV9009.
And I get this status on TAL_DEFRAMER_A as 0x12 or 0x1A (some what random)
[ 10.987241] adrv9009 spi1.0: TAL_DEFRAMER_A deframerStatus 0x12
[ 10.993255] adrv9009 spi1.0: TALISE_readFramerStatus A successful…
Please refer below links.
That file is for the driver itself, which is already compiled into the kernel.
If you want to interface with the driver (send buffers and configure the devices) there are a few options.
- Python: https://analogdevicesinc.github.io/pyadi-iio/
Jet said: I mean : we continuously feed “static customized iq ” using iio_buffer_push(txbuf) function, and we expect these iq data could be transmitted from ADRV9009 tx port, with no gap, no data glitch
There is no guarantee of this unless you use cyclic…
There is an RFSOM that supports MCS with ADRV9009. You can refer to that for an idea on designing with AD9371. Refer to the below links: