Board: EVAL-ADICUP3029
Shield: EVAL-ADPD4100-ARDZ (SPI variant, ADPD4100)
Firmware: ADuCM3029_demo_adpd410x_spi.hex (from official EVAL-ADICUP3029 GitHub releases)
OS Tested: Windows 11, macOS M2 Pro, Linux Ubuntu 24 (VM)
libiio versions tested: 0.23, 0.24
followed these steps : User Guide : eval-adpd410x
---
ISSUE:
IIO Oscilloscope cannot connect to the board and shows "No context found". I have followed the official EVAL-ADPD410x-ARDZ user guide step by step and cannot get past the connection stage.
---
WHAT IS WORKING:
- Hex file flashes successfully via DAPLink drag and drop (no FAIL.TXT)
- DAPLink firmware updated via Maintenance Drive
- Board powers up correctly
- TinyIIOD banner is received correctly over serial at 115200 baud:
"Running TinyIIOD server...
If successful, you may connect an IIO client application by:
1. Disconnecting the serial terminal you use to view this message.
2. Connecting the IIO client application using the serial backend configured as shown:
Baudrate: 115200, Data size: 8 bits, Parity: none, Stop bits: 1, Flow control: none"
(Confirmed via PuTTY on Windows and Python pyserial on macOS)
---
TEST RESULTS:
1. iio_info output (Windows 11, libiio 0.23):
iio_info -u serial:COM4,115200
Library version: 0.23 (git tag: c14a0f8)
Compiled with backends: xml ip usb serial
ERROR: sp_blocking_read_next has timedout
ERROR: READ LINE: -138
Unable to create IIO context serial:COM4,115200: timed out (138)
Same result with: serial:COM4,115200,8n1 and serial:COM4,115200,8n1n
Same result with libiio 0.24.
Same result on Linux (built from source with -DWITH_SERIAL_BACKEND=ON).
2. Python pyserial VERSION command test (macOS, port: /dev/tty.usbmodem1102):
import serial, time
ser = serial.Serial(port='/dev/tty.usbmodem1102', baudrate=115200,
bytesize=8, parity='N', stopbits=1, timeout=5)
time.sleep(2)
for ending in [b'\n', b'\r\n', b'\r']:
ser.write(b'VERSION' + ending)
time.sleep(3)
print(f"Ending {repr(ending)} -> {repr(ser.read_all())}")
ser.close()
Output:
Ending b'\n' -> b''
Ending b'\r\n' -> b''
Ending b'\r' -> b''
No response received for any line ending combination.
3. CrossCore Serial Flash Programmer v1.8.0 (Windows 11):
Settings: Target = ADuCM302x, Port = COM4, Baud = 115200, Action = Erase
Boot mode entered by holding S3 while power cycling USB.
Status output:
"Sending second stage kernel.
Read Intel HEX application image with 668 bytes.
No autobaud response."
---
SWITCH AND JUMPER CONFIGURATION:
- S2 (UART): USB
- S5 (POWER): WALL/USB
- IOSEL jumper: Pin 1 and 2 shorted
- SPI interface resistors: R8 and R9 shorted, R6 and R7 open
- P10 jumper: Pins 1-2, 3-4, 5-6 shorted
---
WHAT I HAVE TRIED:
- Flashed correct hex (SPI variant) multiple times, pressed S1 reset after each flash
- Updated DAPLink firmware via Maintenance Drive
- Tested with 2 different USB data cables & 2 different ADPD4100
- Tested on iio_info with Windows 11, macOS M2 Pro, and Linux Ubuntu 24
- Tested libiio 0.23 and 0.24 on Windows
- Built libiio 0.23 from source on Linux with serial backend enabled
- Tried all serial URI formats documented in the user guide
- Tried IIO Oscilloscope Serial context option and Manual URI option
- Tried CrossCore Serial Flash Programmer erase with board in boot mode (S3 held during power cycle)
- Verified no other application holding the COM port during iio_info tests
---
QUESTION:
Could you please advise what might be causing this? The TinyIIOD banner is received correctly but no response is returned for any command sent to the board. CrossCore Serial Flash Programmer also returns "No autobaud response" even in boot mode. Is there a diagnostic step I may have missed, or could this be a board issue?
Thank you.
