Post Go back to editing

ADICUP3029 + ADPD410x stuck in standby – operation_mode write times out over IIO serial backend

Thread Summary

The user encountered a timeout error when trying to switch the ADPD410x device from standby to go_mode using iio_attr with libiio v0.26 and pyadi-iio on Windows 11. The issue was resolved by using a specific hex file provided by the support engineer. The user also attempted to build their own hex file from the ADuCM3029 demo project to align with their hardware setup.
AI Generated Content
Category: Software
Product Number: EVAL-ADICUP3029

Hi everyone,

I am working with the following setup:

  • EVAL-ADPD410x-ARDZ

  • EVAL-ADICUP3029

  • Connected to Windows 11 via USB (serial backend)

  • libiio v0.26

  • pyadi-iio (latest pip version)

  • Python 3.13

The device is detected correctly over IIO. When I run: iio_info -u serial:COM4

I get:

  • IIO context created with serial backend

  • Device found: adpd410x (buffer capable)

  • 8 voltage channels detected

  • sampling_frequency = 50

  • operation_mode value = 0

  • operation_modes_available: standby go_mode

So the device is visible and readable. But i get a problem as I cannot switch the device from standby to go_mode. 

When I attempt: iio_attr -u serial:COM4 -d adpd410x operation_mode go_mode

I get: 

ERROR: sp_blocking_read_next has timedout
ERROR: READ LINE: -138
ERROR: timed out (138) while writing 'operation_mode' with 'go_mode'

I also tried: iio_attr -u "serial:COM4,115200,8n1n" -d adpd410x operation_mode go_mode and iio_attr -u serial:COM4 -d adpd410x operation_mode 1. And i still get the same timeout error

Any guidance would be greatly appreciated. thank you

Before You Switch


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