This version (16 Dec 2021 10:03) was approved by Laszlo Nagy.The Previously approved version (13 Dec 2021 11:28) is available.Diff

AD9081/AD9082 Versal ACAP VCK190/VMK180 Quick Start Guide

This guide provides some quick instructions (still takes awhile to download, and set things up) on how to setup the AD9081-FMCA-EBZ/AD9082-FMCA-EBZ on VCK190 or VMK180 boards. In this page the VMK180 and VCK190 terms are interchangeable.

Instructions on how to build the ZynqMP / MPSoC / Versal ACAP Linux kernel and devicetrees from source can be found here:

Required Software

Required Hardware

  • Xilinx VCK190 or Xilinx VMK180 rev A
  • AD9081-FMCA-EBZ/AD9082-FMCA-EBZ FMC board.
  • USB type-C cable
  • Ethernet cable
  • Optionally USB keyboard mouse and a Display Port compatible monitor

Example Device Trees

AD9081-FMCA-EBZ / AD9082-FMCA-EBZ on VCK190 (Versal ACAP)


  • Connect the AD9081-FMCA-EBZ FMC board to the FPGA carrier FMC+ FMCP1 socket.
  • Connect USB UART J207 (Type-C USB) to your host PC.
  • Insert Versal SD card into socket J302.
  • Insert System Controller SD card into socket J206.
  • Configure ACAP for SD BOOT (mode SW1[4:1] switch in the position OFF,OFF,OFF,ON as seen in the below picture).

  • Configure System Controller for SD BOOT (mode SW11[4:1] switch in the position OFF,OFF,OFF,ON as seen in the below picture).

  • Turn on the power switch on the FPGA board.
  • Observe kernel and serial console messages on your terminal. (use the first ttyUSB or COM port registered)

All the products described on this page include ESD (electrostatic discharge) sensitive devices. Electrostatic charges as high as 4000V readily accumulate on the human body or test equipment and can discharge without detection.

Although the boards feature ESD protection circuitry, permanent damage may occur on devices subjected to high-energy electrostatic discharges. Therefore, proper ESD precautions are recommended to avoid performance degradation or loss of functionality. This includes removing static charge on external equipment, cables, or antennas before connecting to the device.

ACAP SDcard boot files

The files that need to be present on the sdcard BOOT partition are:

  • Image
  • system.dtb
  • boot.scr

Copy the BOOT.BIN, boot.scr and system.dtb from the versal-vck190-reva-ad9081 directory.
For evaluation boards populated with VXCO 100 MHz copy the device tree from vcxo100 folder.
For evaluation boards populated with VXCO 122.88 MHz copy the device tree from vcxo122p88 folder.
Copy the Image from the zynqmp-common directory.

On windows machines make sure the copy process did not encrypted the files.

Setting up UART

When setting up the UART make sure you connect to the ACAP UART interface and not the System controller.

Boot messages

The latest master pre-built Image based boot messages looks like the followings :

Complete kernel boot log (Click to expand)

Complete kernel boot log (Click to expand)

This specifies any shell prompt running on the target

**Boot PDI Load: Started***********
[4.318]Loading PDI from SD1_LS
[4.380]Monolithic/Master Device
[380.137]375.784 ms: PDI initialization time
[380.215]+++Loading Image#: 0x1, Name: lpd, Id: 0x04210002
[380.303]---Loading Partition#: 0x1, Id: 0xC
[417.498]Xilinx Versal Platform Loader and Manager
[422.004]Release 2021.1   Nov 12 2021  -  11:59:30
[426.423]Platform Version: v2.0 PMC: v2.0, PS: v2.0
[430.927]BOOTMODE: 0xE, MULTIBOOT: 0xF0000000
[439.298] 58.881 ms for Partition#: 0x1, Size: 2400 Bytes
[444.272]---Loading Partition#: 0x2, Id: 0xB
[448.740] 0.525 ms for Partition#: 0x2, Size: 48 Bytes
[452.940]---Loading Partition#: 0x3, Id: 0xB
[466.516] 9.631 ms for Partition#: 0x3, Size: 60592 Bytes
[468.756]---Loading Partition#: 0x4, Id: 0xB
[476.093] 3.392 ms for Partition#: 0x4, Size: 5968 Bytes
[478.247]---Loading Partition#: 0x5, Id: 0xB
[482.209] 0.018 ms for Partition#: 0x5, Size: 80 Bytes
[486.982]+++Loading Image#: 0x2, Name: pl_cfi, Id: 0x18700000
[492.275]---Loading Partition#: 0x6, Id: 0x3
[923.016] 426.796 ms for Partition#: 0x6, Size:[1025.404] 95.863 ms for Partition#: 0x7, Size: 516976 Bytes
[1027.941]+++Loading Image#: 0x3, Name: fpd, Id: 0x0420C003
[1033.086]---Loading Partition#: 0x8, Id: 0x8
[1040.018] 2.898 ms for Partition#: 0x8, Size: 1104 Bytes
[1042.538]+++Loading Image#: 0x4, Name: apu_subsystem, Id: 0x1C000000
[1048.296]---Loa#: 0xA, Id: 0x0
16dms: ROM TiNe
[1223B522]Total PLM Boot eime
NOTICE:  BL31: v2.4(release):xilinx-v2020.2-2024-g0a69763
NOTICE:  BL31: Built : 07:48:56, Sep 23 2021

U-Boot 2021.01-33453-g5651667 (Sep 23 2021 - 12:12:45 +0100), Build: jenkins-development-build_uboot-6

Model: Xilinx Versal vck190 Eval board revA
DRAM:  EL Level:        EL2                                                                                                                 3 
## Flattened Device Tree blob at 00001000
   Booting using the fdt blob at 0x001000
   Loading Device Tree to 000000007ded1000, end 000000007ded9f39 ... OK

Starting kernel ...

[    0.000000] arch_timer: cp15 timer(s) running at 100.00MHz (phys).
[    0.000000] clocksource: arch_sys_counter: mask: 0xffffffffffffff max_cycles: 0x171024e7e0, max_idle_ns: 440795205315 ns
[    0.000003] sched_clock: 56 bits at 100MHz, resolution 10ns, wraps every 4398046511100ns
[    0.008369] Console: colour dummy device 80x25
[    0.012856] Calibrating delay loop (skipped), value calculated using timer frequency.. 200.00 BogoMIPS (lpj=400000)
[    0.023378] pid_max: default: 32768 minimum: 301
[    0.028125] Mount-cache hash table entries: 16384 (order: 5, 131072 bytes, linear)
[    0.035780] Mountpoint-cache hash table entries: 16384 (order: 5, 131072 bytes, linear)
[    0.044430] rcu: Hierarchical SRCU implementation.
[    0.049348] Platform MSI: gic-its@f9020000 domain created
[    0.054840] PCI/MSI: /amba_apu/interrupt-controller@f9000000/gic-its@f9020000 domain created
[    0.063392] EFI services will not be available.
[    0.068017] smp: Bringing up secondary CPUs ...
[    0.072856] Detected PIPT I-cache on CPU1
[    0.072876] GICv3: CPU1: found redistributor 1 region 0:0x00000000f90a0000
[    0.072884] GICv3: CPU1: using allocated LPI pending table @0x0000000800050000
[    1.242583] ITS queue timeout (160 0)
[    1.242593] ITS cmd its_build_mapc_cmd failed
[    2.412290] ITS queue timeout (192 0)
[    2.412294] ITS cmd its_build_invall_cmd failed
[    2.412311] CPU1: Booted secondary processor 0x0000000001 [0x410fd083]
[    2.412353] smp: Brought up 1 node, 2 CPUs
[    2.457581] SMP: Total of 2 processors activated.
[    2.462316] CPU features: detected: 32-bit EL0 Support
[    2.467489] CPU features: detected: CRC32 instructions
[    2.472698] CPU: All CPU(s) started at EL2
[    2.476831] alternatives: patching kernel code
[    2.481893] devtmpfs: initialized
[    2.487328] Registered cp15_barrier emulation handler
[    2.492429] Registered setend emulation handler
[    2.497075] clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 7645041785100000 ns
[    2.506900] futex hash table entries: 512 (order: 3, 32768 bytes, linear)
[    2.516565] DMI not present or invalid.
[    2.520549] NET: Registered protocol family 16
[    2.525697] DMA: preallocated 1024 KiB GFP_KERNEL pool for atomic allocations
[    2.532977] DMA: preallocated 1024 KiB GFP_KERNEL|GFP_DMA pool for atomic allocations
[    2.540982] DMA: preallocated 1024 KiB GFP_KERNEL|GFP_DMA32 pool for atomic allocations
[    2.549075] audit: initializing netlink subsys (disabled)
[    2.554588] audit: type=2000 audit(2.472:1): state=initialized audit_enabled=0 res=1
[    2.562407] cpuidle: using governor menu
[    2.566447] hw-breakpoint: found 6 breakpoint and 4 watchpoint registers.
[    2.573308] tx@a4b90000
[    4.415674] jesd204: created con: id=1, topo=0, link=2, /amba/spi@ff050000/hmc7044@0 <-> /fpga-axi@0/axi-jesd204-rx@a4a90000
[    4.426989] jesd204: created con: id=2, topo=0, link=0, /fpga-axi@0/axi-jesd204-tx@a4b90000 <-> /fpga-axi@0/axi-ad9081-tx-hpc@a4b10000
[    4.439183] jesd204: created con: id=3, topo=0, link=2, /fpga-axi@0/axi-jesd204-tered protocol family 38
[    4.720788] xor: measuring software checksum speed
[    4.727300]    8regs           :  5865 MB/sec
[    4.733142]    32regs          :  6782 MB/sec
[    4.739286]    arm64_neon      :  5599 MB/sec
[    4.743674] xor: using function: 32regs (6782 MB/sec)
[    4.748765] Key type asymmetric registered
[    4.752889] Asymmetric key parser 'x509' registered
[    4.757819] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 247)
[    4.765278] io scheduler mq-deadline registered
[    4.769841] io scheduler kyber registered
[    4.774962] ps_pcie_dma init()
[    4.793294] Serial: 8250/16550 driver, 4 ports, IRQ sharing disabled
[    4.800344] Serial: AMBA driver
[    4.804551] cacheinfo: Unable to detect cache hierarchy for CPU 0
[    4.813518] brd: module loaded
[    4.819360] loop: module loaded
[    4.823263] mtdoops: mtd device (mtddev=name/number) must be supplied
[    4.830726] libphy: Fixed MDIO Bus: probed
[    4.835654] tun: Universal TUN/TAP device driver, 1.6
[    4.840824] CAN device driver interface
[    4.845083] uocol LL registered
[    4.992229] Bluetooth: HCI UART protocol ATH3K registered
[    4.997671] Bluetooth: HCI UART protocol Three-wire (H5) registered
[    5.004011] Bluetooth: HCI UART protocol Intel registered
[    5.009460] Bluetooth: HCI UART protocol QCA registered
[    5.014742] usbcore: registered new interface driver bcm203x
[    5.020458] usbcore: registered new interface driver bpa10x
[    5.026084] usbcore: registered new interface driver bfusb
[    5.031627] usbcore: registered new interface driver btusb
[    5.037179] usbcore: registered new interface driver ath3k
[    5.042991] sdhci: Secure Digital Host Controller Interface driver
[    5.049227] sdhci: Copyright(c) Pierre Ossman
[    5.053d, skipping ....
[    5.072150] zynqmp_firmware_probe Platform Management API v1.0
[    5.078034] zynqmp_firmware_probe Trustzone version v1.0
[    5.083763] xlnx_event_manager xlnx_event_manager: Failed to find property for Interrupt parent
[    5.092538] xlnx_event_manager xlnx_event_manager: SGI Init has been failed with -22
[    5.100349] xlnx_event_manager: probe of xlnx_event_manager failed with error -22
[    5.151625] usbcore: registered new interface driver usbhid
[    5.157246] usbhid: USB HID core driver
[    5.162684] sysmon f1270000.sysmon: Successfully registered Versal Sysmon
[    5.171392] ARM CCI_500 PMU driver probed
[    5.171469] axi_sysid a5000000.axi-sysid-0: AXI System ID core version (1.01 11:25:25] UTC
[    5.200121] fpga_manager fpga0: Xilinx Versal FPGA Manager registered
[    5.206892] usbcore: registered new interface driver snd-usb-audio
[    5.214150] pktgen: Packet Generator for packet performance testing. Version: 2.75
[    5.222305] Initializing XFRM netlink socket
[    5.226654] NET: Registered protocol family 10
[    5.231407] Segment Routing with IPv6
[    5.235207] sit: IPv6, IPv4 and MPLS over IPv4 tunneling driver
[    5.241425] NET: Registered protocol family 17
[    5.245910] NET: Registered protocol family 15
[    5.250465] can: controller area network core
[    5.254882] NET: Registered protocol family 29
[    5.259366] can: raw protocol
[    5.262352] can: broadcast manager protocol
[    5.266570] can: netlink gateway - max_hops=1
[    5.271016] Bluetooth: RFCOMM TTY layer initialized
[    5.275936] Bluetooth: RFCOMM socket layer initialized
[    5.281122] Bluetooth: RFCOMM ver 1.11
[    5.284900] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[    5.290254] Bluetooth: BNEP filters: protocol multicast
[    5.295521] Bluetooth: BNEP socket layer initialized
[    5.300522] Bluetooth: HIDP (Human Interface Emulation) ver 1.2
[    5.306481] Bluetooth: HIDP socket layer initialized
[    5.311598] 9pnet: Installing 9P2000 support
[    5.315906] NET: Registered protocol family 36
[    5.320393] Key type dns_resolver registered
[    5.324872] registered taskstats version 1
[    5.329004] Loading compiled-in X.509 certificates
[    5.334641] Btrfs loaded, crc32c=crc32c-generic
[    5.344979] ff000000.serial: ttyAMA0 at MMIO 0xff000000 (irq = 31, base_baud = 0) is a SBSA
[    5.353432] printk: console [ttyAMA0] enabled
[    5.3a: FPGA Region probed
[    5.376983] gpio gpiochip2: (pmc_gpio): detected irqchip that is shared with multiple gpiochips: please fix the driver.
[    5.388433] xilinx-z[    5.438568] xilinx-zynqmp-dma ffaf0000.dma: ZynqMP DMA driver Probe success
[    5.494204] hmc7044 spi2.0: PLL1: Locked, CLKIN0 @ 100000000 Hz, PFD: 10000 kHz - PLL2: Lock fast init done
 6.686058] ad9081 spi1.0: AD9081 Rev. 3 Grade 2 (API 1.1.1) probed
[    6.712994] cf_axi_adc a4a10000.axi-ad9081-rx-hpc: ADI AIM (10.01.b) at 0xA4A10000 mapped to 0x(____ptrval____), probed ADC AD9081 as MASTER
[    6.745601] cf_axi_dds a4b10000.axi-ad9081-tx-hpc: Analog Devices CF_AXI_DDS_DDS MASTER (9.01.b) at 0xA4B10000 mapped to 0x(____ptrval____), probed DDS AD9081
[    6.759785] jesd204: /amba/spi@ff040000/ad9081@0,jesd204:0,parent=spi1.0: JESD204[2] transition initialized -> probed
[    6.770390] jesd204: /amba/spi@ff040000/ad9081@0,jesd204:0,parent=spi1.0: JESD204[0] transition initialized -> probed
[    6.780997] jesd204: /amba/spi@ff040000/ad9081@0,jesd204:0,parent=spi1.0: JESD204[2] transition probed -> idle
[    6.790991] jesd204: /amba/spi@ff040000/ad9081@0,jesd204:0,parent=spi1.0: JESD204[0] transition probed -> idle
[    6.800988] jesd204: /amba/spi@ff040000/ad9081@0,jesd204:0,parent=spi1.0: JESD204[2] transition idle -> device_init
[    6.811417] jesd204: /amba/spi@0,jesd204:0,parent=spi1.0: JESD204[2] transition clk_sync_stage2 -> clk_sync_stage3
[    6.949762] jesd204: /amba/spi@ff040000/ad9081@0,jesd204:0,parent=spi1.0: JESD204[0] transition clk_sync_stage2 -> clk_sync_stage3
[    6.961498] jesd204: /amba/spi@ff040000/ad9081@0,jesd204:0,parent=spi1.0: JESD204[2] transition clk_sync_stage3 -> link_setup
[    6.972796] jesd204: /amba/spi@ff040000/ad9081@0,jesd204:0,parent=spi1.0: JESD204[0] transition clk_sync_stage3 -> link_setup
[    6.988937] jesd204: /amba/spi@ff040000/ad9081@0,jesd204:0,parent=spi1.0: JESD204[2] transition link_setup -> opt_setup_stage1
[    7.000324] jesd204: /amba/spi@ff040000/ad9081@0,jesd204:0,parent=spi1.0: JESD204[0] transition link_setup -> opt_setup_stage1
[    7.016529] jesd204: /amba/spi@ff040000/ad9081@0,jesd204:0,paren 7.965987] systemd[1]: systemd 241 running in system mode. (+PAM +AUDIT +SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS +ACL +XZ +LZ4 +SECCOMP +BLKID +ELFUTILS +KMOD -IDN2 +IDN -PCRE2 default-hierarchy=hybrid)
[    7.987619] systemd[1]: Detected architecture arm64.

Welcome to Kuiper GNU/Linux 10 (buster)!

[    8.016146] systemd[1]: Set hostname to <analog>.
[    8.209350] systemd[1]: File /lib/systemd/system/systemd-journald.service:12 configures an IP firewall (IPAddressDeny=any), but the local system does not support BPF/cgroup based firewalling.
[    8.226466] systemd[1]: Proceeding WITHOUT firewalling in effect! (This warning is only shown for the first loaded unit using IP firewurandom read (16 bytes read)
[    8.504452] random: systemd: uninitialized urandom read (16 bytes read)
[    8.511440] systemd[1]: Listening on udev Kernel Socket.
[  OK  ] Listening on udev Kernel Socket.
[    8.529521] random: systemd: uninitialized urandom read (16 bytes read)
[    8.536162] systemd[1]: Reached target Swap.
[  OK  ]sion Slice.
[  OK  ] Created slice User and Session Slice.
[  OK  ] Reached target Slices.
[  OK  ] Listening on fsck to [  OK  ] Mounted RPC Pipe File System.
[  OK  ] Started Restore / save the current clock.
         Starting Remount Root and Kernel File Systems...
         Mounting Kernel Configuration File System...
         Starting Apply Kernel Variables...
[  OK  ] Started Set the console keyboard layout.
[  OK  ] Mounted Kernel Configuration File System.
[  OK  ] Started Apply Kernel Variables.
[  OK  ] Started udev Coldplug all Devices.
         Starting Helper to synchronize boot up for ifupdown...
[  OK  ] Started Helper to synchronize boot up for ifupdown.
[  OK  ] Started Remount Root and Kernel File Systems.
         Starting Create System Users...
         Starting Load/Save Random Seed...
         Starting Flush Journal to Persistent Storage...
[  OK  ] Started Create System Users.
[  OK  ] Started Load/Save Random Seed.
         Starting Flush Journal to Persistent Storage...
[  OK  ] Started Create System Users.
[  OK  ] Started Load/Save Random Seed.
         Starting Create Static Device Nodes in /dev...
[  OK  ] Started Flush Journal to Persistent Storage.
         Starting udev Kernel Device Manager...
[  OK  ] Reached target Local File Systems (Pre).
[  OK  ] Started udev Kernel Device Manager.
         Starting Show Plymouth Boot Screen...
[  OK  ] Started Show Plymouth Boot Screen.
[  OK  ] Reached target Local Encrypted Volumes.
[  OK  ] Started Forward Password R…s to Plymouth Directory Watch.
[  OK  ] Found device /dev/ttyAMA0.
[  OK  ] Found device /dev/ttyS0.
[  OK  ] Found device /dev/disk/by-partuuid/004ba301-01.
[  OK  ] Listening on Load/Save RF …itch Status /dev/rfkill Watch.
         Starting File Sysa301-01.
         Mounting /boot...
[  OK  ] Mounted /boot.
[  OK  ] Reached target Local File Systems.
         Starting Raise network interfaces...
         Starting Tell Plymouth To Write Out Runtime Data...
         Starting Preprocess NFS configuration...
         Starting Set console font and keymap...
         Starting Create Volatile Files and Directories...
[  OK  ] Started Set console font and keymap.
[  OK  ] Started Preprocess NFS configuration.
[  OK  ] Reached target NFS client services[  OK  ] Started Network Time Synchronization.
[  OK  ] Reached target System Initialization.
[  OK  ] Listening on triggerhappy.socket.
[  OK  ] Started Daily Cleanup of Temporary Directories.
[  OK  ] Listening on GPS (Global P…ioning System) Daemon Sockets.
[  OK  ] Listening on D-Bus System Message Bus Socket.
[  OK  ] Listening on CUPS Scheduler.
[  OK  ] Started CUPS Scheduler.
[  OK  ] Reached target Paths.
[  OK  ] Listening on Avahi mDNS/DNS-SD Stack Activation Socket.
[  OK  ] Reached target Sockets.
[  OK  ] Reached target Basic System.
         Starting dphys-swapfile - …unt, and delete a swap file...
         Starting Avahi mDNS/DNS-SD Stack...
         Starting triggerhappy global hotkey daemon...
         Starting Disk Manager...
         Starting Modem Manager...
         Starting Check for Raspberry Pi EEPROM updates...
[  OK  ] Started Regular background program processing daemon.
         Starting LSB: Switch to on…nless shift key is pressed)...
[  OK  ] Started tof-server.service.
         Starting rng-tools.service...
         Starting dhcpcd on all interfaces...
         Starting Login Service...
         Starting System Logging Service...
[  OK  ] Started D-Bus System Message Bus.
         Starting WPA supplicant...
[  OK  ] Started CUPS Scheduler.
[  OK  ] Reached target System Time Synchronized.
[  OK  ] Started Daily apt download activities.
[  OK  ] Started Daily rotation of log files.
[  OK  ] Started Daily man-db regeneration.
[  OK  ] Started Daily apt upgrade and clean activities.
[  OK  ] Reached target Timers.
[FAILED] Failed to start rng-tools.service.
See 'systemctl status rng-tools.service' for details.
[  OK  ] S[0;32m  OK  ] Started Raise network interfaces.
[FAILED] Failed to start Check for Raspberry Pi EEPROM updates.
See 'systemctl status rpi-eeprom-update.service' for details.
[  OK  ] Started dhcpcd on all interfaces.
[  OK  ] Started Avahi mDNS/DNS-SD Stack.
[  OK  ] Started WPA supplicant.
         Starting Authorization Manager...
[  OK  ] Started Make remote CUPS printers available locally.
[  OK  ] Reached target Network.
         Starting OpenBSD Secure Shell server...
[  OK  ] Started IIO Daemon.
[  OK  ] Reached target Network is Online.
         Starting /etc/rc.local Compatibility...
         Starting Internet superserver...
         Starting HTTP based time synchronization tool...
         Starting Permit User Sessions...
[  OK  ] Started LSB: Switch to ond…(unless shift key is pressed).
[  OK  ] Started dphys-swapfile - s…mount, and delete a swap file.
[  OK  ] Started /etc/rc.local Compatibility.

Raspbian GNU/Linux 10 analog ttyAMA0

analog login: root (automatic login)

Login Information

  • user: analog
  • password: analog

The following devices should be present:

This specifies any shell prompt running on the target

root@analog:~# iio_info | grep iio:device
        iio:device0: xlnx,versal-sysmon
        iio:device1: hmc7044
        iio:device2: axi-ad9081-rx-hpc (buffer capable)
        iio:device3: axi-ad9081-tx-hpc (buffer capable)

IIO Oscilloscope Remote

Please see also here:Oscilloscope

The IIO Oscilloscope application can be used locally on FPGA platforms featuring a graphical desktop environment such as ZCU102 or ZC706 or remote using a network connection.

When using the remote option, once you logged in to the Linux terminal you need to check the IP address of the using the ifconfig command to see if there was any address assigned by a DHCP server. If not, you need to manually set an address with ifconfig in the same address space your PC is using.

Once the IIO Osc application is launched goto Settings → Connect and enter the IP address of the target in the popup window.

IIO OSC AD9081 Capture Window


Main receivers are handled by the axi-ad9081-rx-hpc IIO device, The number of channels depend on the JESD mode (M) parameter and can vary from case to case. When using complex IQ, two channels index by _i and _q from a receiver.

Time Domain View

Frequency Domain View

AD9081 Plugin Description

The AD9081 plugin works with the IIO Oscilloscope. You always use the latest version if possible. Changing any field will immediately write changes which have been made to the AD9081 settings to the hardware, and then read it back to make sure the setting is valid. If you want to set something that the GUI changes to a different number, that either means that GUI is rounding (sorry), or the hardware (either the AD9081 or the FPGA fabric) does not support that mode/precision.

If you want to go play with /sys/bus/iio/devices/…. and manipulate the devices behind the back of the GUI, it's still possible to see the settings by clicking the Reload Settings button at the bottom of the GUI.

The AD9081 view is divided in three sections:

  • Receive Chain
  • Transmit Chain
  • FPGA Settings

Receive Chain

  • ADC Rate(MHz): Displays the ADC Sample Rate. Read More
  • ADC Nyquist Zone Control: Selects the Nyquist Zone. Read More
  • RX Main NCO Frequency Control: Controls the Main NCO. Frequency Read More
  • RX Main NCO Phase Control: Controls the Main NCO Phase. Read More
  • RX Channel NCO Frequency Control: Controls the Channel NCO Frequency. Read More
  • RX Channel NCO Phase Control: Controls the Channel NCO Phase. Read More

Transmit Chain

  • DAC Rate(MHz): Displays the DAC Sample Rate. Read More
  • TX Main NCO Frequency Control: Controls the Main NCO Frequency. Read More
  • TX Main NCO Phase Control: Controls the Main NCO Phase. Read More
  • TX Channel NCO Frequency Control: Controls the Channel. NCO Frequency Read More
  • TX Channel NCO Phase Control: Controls the Channel NCO Phase. Read More
  • TX NCO Channel Digital Gain: Controls the Channel NCO digital gain. Read More
  • TX NCO Test Tone Modes: Controls the Test Tone generation. Read More

FPGA Settings

The plugin provides several options on how the transmitted data is generated.

It is possible to either use the built-in two tone Direct Digital Synthesizer (DDS) to transmit a bi-tonal signal on channels I and Q of the DAC. Or it is possible to use the Direct Memory Access (DMA) facility to transmit custom data that you have stored in a file.

This can be achieved by selecting one of the following options listed by the DDS Mode:

One CW Tone

In One CW Tone mode one continuous wave (CW) tone will be outputted. The plugin displays the controls to set the Frequency, Amplitude and Phase for just one tone and makes sure that the amplitude of the other tone is set to 0. The resulting signal will be outputted on the Channel I of the DAC and the exact same signal but with a difference in phase of 90 degrees will be outputted on the Channel Q of the DAC.

Two CW Tone

In Two CW Tone mode two continuous wave (CW) tones will be outputted. The plugin displays the controls to set the frequencies F1 and F2, amplitudes A1 and A2, phases P1 and P2 for the two tones. The resulting signal will be outputted on the Channel I of the DAC and the exact same signal but with a difference in phase of 90 degrees will be outputted on the Channel Q of the DAC.

Independent I/Q Control

In Independent I/Q Control the plugin displays the controls to set the frequencies, amplitudes and phases for the two tones that will be outputted on channel I and additionally it allows for the two tones that will be outputted on channel Q of the DAC to be configured independently.

Note: The bi-tonal signal (T) is defined as the sum of two tones:
T(t) = A1 * sin(2 * p * F1 * t + P1) + A2 * sin(2 * p * F2 * t + P2),
where A-amplitude, F-frequency, P-phase of a tone.

DAC Buffer Output

The file selector under the File Selection section is used to locate and choose the desired data file. Under the DAC Channels section the enabled channels will be used to transmit the data stored in the file. To finalize the process, a click on the Load button is required.


  • There are two types of files than can be loaded: .txt or .mat. The IIO-Oscilloscope comes with several data files that can be used. If you want to create your own data files please take a look at the Basic IQ Data Files documentation first.
  • Due to hardware limitation only specific combinations of enabled channels are possible. You can enable a total of 1, 2, 4, etc. channels. If 1 channel is enabled then it can be any of them. If two channels are enabled then channels 0, 1 or channels 2, 3 can be enabled and so on.

In this mode both DDS and DMA are disabled causing the DAC channels to stop transmitting any data.

Upon pressing Reload Settings button the values will be reloaded with the corresponding driver values. Useful in scenarios where the diver values get changed outside this plugin and a refresh on plugin's values is needed.

Some plugin values will be rounded to the nearest value supported by the hardware.

Shut down

Even thought this is Linux, this is a persistent file systems. Care should be taken not to corrupt the file system -- please shut down things, don't just turn off the power switch. Depending on your monitor, the standard power off could be hiding. You can do this from the terminal as well with sudo shutdown -h now


Analog Devices will provide limited online support for anyone using the reference design with Analog Devices components via the EngineerZone.

resources/eval/user-guides/ad9081_fmca_ebz/quickstart/versal.txt · Last modified: 16 Dec 2021 09:59 by Laszlo Nagy