Post Go back to editing

AD9084 + VCU118: iio_info reports ADF4030 timeouts and calibration_data I/O error despite healthy JESD links

Thread Summary

The user encountered various errors during a remote iio_info scan on the AD9084/VCU118 setup, including I/O errors, permission denied, and no data available messages. The support engineer advised that iio_info is not suitable for devices with complex properties like AD9084 and suggested avoiding it, as it can lead to odd debug states and potential MicroBlaze lockups. The ADF4030 duty_cycle and phase timeout behavior on specific channels is expected, and the calibration_data attribute is write-only. The host libiio 0.26 and target IIOD 0.21 versions are compatible, but the scan will fail on many devices with complex attributes. The user was directed to the Linux Software Drivers forum for further assistance.
AI Generated Content
Category: Software
Product Number: AD9084
Software Version: Host libiio 0.26; target IIOD/libiio 0.21; Linux 6.12.77-gb47bbbe8ca7b-dirty; AD9084 API 2.0.10 / FW 2.0.6; Vivado 2025.1

I wanted to get your perspective on a couple of behaviors I am seeing during the AD9084/VCU118 initialization.

I ran the following command as part of the bring-up:

iio_info -u ip:192.168.2.1

I attached the complete output from the command.

The scan completes, all 12 IIO devices are detected, and the JESD204 RX/TX links report DATA, SYSREF captured, and no SYSREF alignment error.

I tried troubleshooting these errors on my own and looking for similar cases online, but I was not able to find a clear solution. To make the output easier to review, I used AI to help summarize all of the errors I am seeing from the attached iio_info output:

calibration_data ERROR: Input/output error (5)

cfir_config ERROR: Permission denied (13)

jesd204_fsm_resume ERROR: Permission denied (13)

pfilt_config ERROR: Permission denied (13)

bist_2d_eyescan_jrx ERROR: Invalid argument (22)

eye_data_partial ERROR: No data available (61)

eyescan_info ERROR: No data available (61)

prbs_counter_reset ERROR: Permission denied (13)

prbs_error_counters ERROR: No data available (61)

prbs_status ERROR: No data available (61)

prbs_error_inject ERROR: Permission denied (13)

I am also seeing:

Connection timed out (110)

when iio_info reads duty_cycle and phase on these ADF4030 channels:

BSYNC4_TP56_TP57
BSYNC3_TP54_TP55
BSYNC4_TP48_TP49
BSYNC2_DEBUG_P19

Each of those channels returns a timeout for both duty_cycle and phase.

One thing I checked separately was calibration_data. When I read it locally on the MicroBlaze terminal using:

cat /sys/bus/iio/devices/iio:device10/calibration_data > /tmp/calibration_test.bin

it succeeds and generates a 60,692-byte calibration file.

Because the local read succeeds, I am unsure why the remote iio_info read returns:

calibration_data ERROR: Input/output error (5)

The ADF4030 also still reports healthy overall status afterward, including:

PLL Status: Locked
TDC Error: OK
FSM Status: Idle
TDC Status: Idle

The rest of the system also appears functional. I have successfully:

- Captured RX data through the IIO buffer
- Written TX data through the IIO buffer
- Displayed RX data in IIO Oscilloscope
- Used the AD9084 ramp and checkerboard ADC test patterns successfully

One additional behavior I have observed is that on some runs, after executing the full remote iio_info scan, the connection to 192.168.2.1 eventually becomes unreachable and requires restarting the setup. Targeted IIO reads/writes and RX/TX buffer operations otherwise work normally.

My software versions are:

Host libiio: 0.26
Target IIOD/libiio backend: 0.21
Linux kernel: 6.12.77-gb47bbbe8ca7b-dirty
AD9084 API: 2.0.10
AD9084 firmware: 2.0.6
Vivado: 2025.1

I am using locally built ADI HDL and Linux images for the VCU118 + AD9084 configuration.

Do you know whether these errors are normal during a full iio_info scan, or whether they indicate something I may have configured incorrectly?

In particular, I would appreciate guidance on:

  1. Whether the ADF4030 duty_cycle / phase timeout behavior on those four channels is expected.
  2. Whether the calibration_data remote I/O error is expected even though the same attribute reads successfully locally.
  3. Whether the Permission denied, No data available, and Invalid argument messages above are expected for these diagnostic/write-only attributes during iio_info.
  4. Whether the host libiio 0.26 / target IIOD 0.21 version difference could contribute to the behavior.
  5. Whether a normal remote iio_info scan on this reference design should complete without any attribute errors.
  6. Whether the loss of network connectivity after some full iio_info scans is something you have seen before.

If these are not expected, do you have any suggestions on what I should check next or what the likely cause could be?

Thread Notes

Parents
  • The AD9084 platform has many write only and large data block attributes so I wouldn't run iio_info against it. It may result in odd debug states. Just avoid it for now. Only read/write properties you wish to address.

    1. I don't believe these are connected to anything

    2. its write only

    3. See top comment

    4. These are fine

    5. No, it will fail on many devices that have complex properties like AD9084

    6. The microblaze may lock up when doing this since you can lock a driver.

    -Travis

Reply
  • The AD9084 platform has many write only and large data block attributes so I wouldn't run iio_info against it. It may result in odd debug states. Just avoid it for now. Only read/write properties you wish to address.

    1. I don't believe these are connected to anything

    2. its write only

    3. See top comment

    4. These are fine

    5. No, it will fail on many devices that have complex properties like AD9084

    6. The microblaze may lock up when doing this since you can lock a driver.

    -Travis

Children
No Data

Before You Switch


Switching languages will make ADI Explorer unavailable. Resume your session by switching back to English and reopening ADI Explorer.