cn0552.zip - Running on Win11 - IIO Oscilloscope - Error Using IIO Tools

[jwestmoreland]

Hello All,

Trying to get this to run:
https://github.com/analogdevicesinc/no-OS/releases/download/last_commit/cn0552.zip

Am seeing this:

Are there any known incompatabilities with Win 11 with the lib iio driver and/or the IIO Oscilloscope?

When I connect a serial port terminal - I don't see data being transmitted. The .hex file downloads; reboots, the DAPLink window pops up.
If I download the .elf file - it will have the FAIL.TXT file in the DAPLink window. So, apparently, the .hex file is the 'correct' file but I'm not seeing any data being transmitted back from the 3029 board.

I don't suppose there are any pyadi workarounds for this - correct?

TIA,
johnw

[jwestmoreland]

Also - with Mbed being sunsetted - and after seeing a lot with the same issue I've posted about just get their board replaced and that seems to fix the issue - how much longer will these products be supported by Aanlog?

TIA,
johnw

[rbolboac]

Hi @jwestmoreland,

Thanks for the report. The symptoms you're describing (.hex flashes fine, board reboots and re-enumerates as DAPLink, but no data on the serial terminal) usually point to the board's hardware/serial setup rather than a Win 11 or libiio incompatibility.

Could you double-check the hardware setup against the project guide first?

CN0552 README (hardware connections): https://github.com/analogdevicesinc/no-OS/blob/main/projects/cn0552/README.rst

A few things that are the usual culprits on the EVAL-ADICUP3029:

1. UART switch (S2) — make sure it's set to the USB position. If it's in the other position, the firmware runs but nothing reaches the USB serial port, which matches exactly what you're seeing.
2. Serial port settings — the IIO firmware uses the UART as a binary IIOD transport, so a plain serial terminal will show little/no human-readable output even when it's working. Confirm the COM port, baud rate, and that you're connecting to the right port that the ADICUP3029 enumerates.
3. Cable/port — USB into P10 on the ADICUP3029 (power + programming + serial), and the CN0552-PMDZ attached to P9.
4. Use the .hex, not the .elf — you already found this; the DAPLink FAIL.TXT on .elf is expected, the .hex is the correct drag-and-drop target.

Since this is the IIOD firmware, the recommended way to talk to it isn't a raw terminal but an IIO client over the serial backend. Could you try:

iio_info -u 'serial:COMxx,115200,8n1n'

(replace COMxx and the baud with your settings) and share the output? If iio_info can enumerate the context but IIO Oscilloscope can't, that narrows it to the client; if neither connects, it's the serial/hardware layer.

Thanks!

[jwestmoreland]

Hello @rbolboac - Ramona,

Here's the output from the working board:

C:\Users\john_w>iio_info --uri serial:COM21
iio_info version: 0.26 (git tag:bdd5c00)
Libiio version: 0.26 (git tag: bdd5c00) backends: xml ip usb serial
IIO context created with serial backend.
Backend version: 1.1 (git tag: 0000000)
Backend description string: no-OS/projects/cn0552 remotes/origin/c6e8ce1436f83d54e94fd3482285282039beeb5b-c6e8ce1436f
IIO context has 3 attributes:
uri: serial:COM21,115200,8n1n
serial,port: COM21
serial,description: mbed Serial Port (COM21)
IIO context has 1 devices:
iio:device0: ad7746
8 channels found:
voltage0: (input)
6 channel-specific attributes found:
attr 0: raw value: 11136
attr 1: scale value: 0.000139474
attr 2: sampling_frequency value: 50
attr 3: sampling_frequency_available value: 50 31 16 8
attr 4: calibbias_calibration ERROR: No such file or directory (2)
attr 5: calibscale_calibration ERROR: No such file or directory (2)
voltage1: (input)
6 channel-specific attributes found:
attr 0: raw value: 23904360
attr 1: scale value: 0.000139474
attr 2: sampling_frequency value: 50
attr 3: sampling_frequency_available value: 50 31 16 8
attr 4: calibbias_calibration ERROR: No such file or directory (2)
attr 5: calibscale_calibration ERROR: No such file or directory (2)
temp0: (input)
1 channel-specific attributes found:
attr 0: input value: 30812
temp1: (input)
1 channel-specific attributes found:
attr 0: input value: -249941
capacitance0: (input)
9 channel-specific attributes found:
attr 0: raw value: 168834
attr 1: scale value: 0.000000488
attr 2: offset value: 0
attr 3: sampling_frequency value: 91
attr 4: sampling_frequency_available value: 91 84 50 26 16 13 11 9
attr 5: calibscale value: 1.370895
attr 6: calibbias value: 32768
attr 7: calibbias_calibration ERROR: No such file or directory (2)
attr 8: calibscale_calibration ERROR: No such file or directory (2)
capacitance0-capacitance2: (input)
9 channel-specific attributes found:
attr 0: raw value: -806029
attr 1: scale value: 0.000000488
attr 2: offset value: 0
attr 3: sampling_frequency value: 91
attr 4: sampling_frequency_available value: 91 84 50 26 16 13 11 9
attr 5: calibscale value: 1.370895
attr 6: calibbias value: 32768
attr 7: calibbias_calibration ERROR: No such file or directory (2)
attr 8: calibscale_calibration ERROR: No such file or directory (2)
capacitance1: (input)
9 channel-specific attributes found:
attr 0: raw value: 1382293
attr 1: scale value: 0.000000488
attr 2: offset value: 0
attr 3: sampling_frequency value: 91
attr 4: sampling_frequency_available value: 91 84 50 26 16 13 11 9
attr 5: calibscale value: 1.370895
attr 6: calibbias value: 32768
attr 7: calibbias_calibration ERROR: No such file or directory (2)
attr 8: calibscale_calibration ERROR: No such file or directory (2)
capacitance1-capacitance3: (input)
9 channel-specific attributes found:
attr 0: raw value: -8388608
attr 1: scale value: 0.000000488
attr 2: offset value: 0
attr 3: sampling_frequency value: 91
attr 4: sampling_frequency_available value: 91 84 50 26 16 13 11 9
attr 5: calibscale value: 1.370895
attr 6: calibbias value: 32768
attr 7: calibbias_calibration ERROR: No such file or directory (2)
attr 8: calibscale_calibration ERROR: No such file or directory (2)
1 debug attributes found:
debug attr 0: direct_reg_access value: 7
No trigger on this device

C:\Users\john_w>

Here's the output from the 1st board:
C:\Users\john_w>iio_info --uri serial:COM24
ERROR: sp_blocking_read_next has timedout
ERROR: READ LINE: -138
Unable to create IIO context serial:COM24: timed out (138)

Too bad the scope trace part of the IIO Oscilloscope doesn't work - even some 'slow' plots would be better than nothing.

How long can we expect this to be supported in this fashion with Mbed going the way of the dinosaurs?
I guess there's the Arduino option.

Also - it appears pyadi-iio doesn't work for this board either - when I run the same thing:

(adi) C:\Users\john_w\pyadi-iio\examples>python ad7746.py
Traceback (most recent call last):
File "C:\Users\john_w.conda\envs\adi\Lib\site-packages\adi\context_manager.py", line 36, in init
self._ctx = iio.Context(self.uri)
~~~~~~~~~~~^^^^^^^^^^
File "C:\Users\john_w.conda\envs\adi\Lib\site-packages\iio.py", line 1328, in init
self._context = _new_uri(_context.encode("ascii"))
~~~~~~~~^^^^^^^^^^^^^^^^^^^^^^^^^^
File "C:\Users\john_w.conda\envs\adi\Lib\site-packages\iio.py", line 56, in _check_null
raise OSError(err, _strerror(err))
OSError: [Errno 0] No error

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
File "C:\Users\john_w\pyadi-iio\examples\ad7746.py", line 34, in
dev = adi.ad7746(uri="serial:COM21")
File "C:\Users\john_w.conda\envs\adi\Lib\site-packages\adi\ad7746.py", line 22, in init
context_manager.init(self, uri, self._device_name)
~~~~~~~~~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "C:\Users\john_w.conda\envs\adi\Lib\site-packages\adi\context_manager.py", line 38, in init
raise Exception("No device found")
Exception: No device found

Maybe pyadi-iio isn't compatible with this version of python:

(adi) C:\Users\john_w\pyadi-iio\examples>python --version
Python 3.14.6

Thanks,
johnw

[rbolboac]

Hi @jwestmoreland,

To figure out the difference between the two boards, could you describe both setups in a bit more detail — the working one (COM21) and the non-working one (COM24)?

For each board, please share:

• Hardware — which board is it exactly (both EVAL-ADICUP3029 / ADuCM3029, or is one a different board)?
• Software — which firmware did you flash, and exactly which file did you drag-and-drop? Is it the same .hex from the released cn0552.zip on both, or were they built/flashed differently?

Once we know whether it's identical software on the same board type, we can tell whether this is a software issue or something specific to one board.

Thanks!

[rbolboac]

Regarding the pyadi-iio failure — that one is a usage issue, not a board problem (note it was run against the working COM21 board).

In your run the call was:

dev = adi.ad7746(uri="serial:COM21")

Two things are missing there:

1. The serial URI needs the baud/config: serial:PORT,baud,bits/parity/stop. The bare serial:COM21 makes iio.Context() return NULL — which is exactly where your traceback dies (context_manager.py line 36), and pyadi then reports the generic No device found. Note that iio_info worked with a bare URI only because the CLI fills in the defaults for you (it echoed back serial:COM21,115200,8n1n); the raw context call pyadi uses does not.
2. device_name is required for adi.ad7746 — without it the wrapper raises before talking to the device.

So the correct call is:

dev = adi.ad7746(uri="serial:COM21,115200,8n1", device_name="ad7746")

Let me know if it works!