Hi all,
I'm migrating control of a CN0566 (Phaser) beamformer board from its reference Raspberry Pi host to a ZC702 (Zynq-7000), connecting over the PMOD J62/J63 headers with a ported device tree (adar1000/adf4159 nodes, xlnx,zynq-spi-r1p6 controller). The same CN0566 unit works perfectly on the Pi — ADAR1000 scratchpad read/write succeeds, and both beamformers and the ADF4159 probe correctly. On ZC702, the identical scratchpad test fails consistently — reads simply don't return the expected value.
I'm also not using the ADALM-Pluto/AD9363 SDR that normally pairs with CN0566+Raspberry Pi. Instead, I'm using FMCOMMS4 (AD9361) directly on ZC702's FMC connector, alongside CN0566 on the PMOD headers.
Hardware & System Setup
- Target board: ADI CN0566 (ADAR1000)
- FPGA board: Xilinx ZC702 (Zynq-7000), PL PMOD Headers (J62 & J63)
- Base FPGA project: AMD/Xilinx FMCOMMS2-ZC702 reference design (GitHub), extended with CN0566 SPI/PMOD connectivity
- Interface voltage: 2.5V VADJ (FPGA side) / 3.3V VCC3V3 (PMOD side)
- Software environment: Linux, in-kernel
adi,adar1000+adi,adf4159IIO drivers, libiio
What I've already ruled out, with evidence:
- CN0566's onboard SN74AVC4T245 level shifter / DIR-pin wiring — confirmed via schematic that 1DIR/2DIR are fixed correctly for their signal directions; also ruled out structurally since the same board works fine on the Pi, so any CN0566-side fault would affect both hosts identically.
- Vivado block-design connectivity — confirmed via Tcl (
get_bd_pins/get_bd_ports) thatspi1_sdi_ireaches a proper top-level port, matchingspi0_sdi_i's pattern exactly. - Wrapper HDL — confirmed
spi1_sdi_iis a clean, unbuffered top-levelinputwith no stray logic or second driver. - Internal PL pull resistor — added
PULLTYPE PULLDOWNon the MISO port in XDC; zero effect on a DC voltage measurement, ruling out the FPGA's own weak internal pull as the dominant factor. - SPI clock speed — discovered via the ZC702 user guide that PMOD signals route through an onboard TXS0108E auto-direction-sensing level shifter, documented by Xilinx as having multi-microsecond rise/fall times and a ~100 kHz practical ceiling, with FMC recommended instead for high-speed GPIO/SPI. Lowered
spi-max-frequencyto 100 kHz (confirmed via/proc/device-treereadback:00 01 86 a0) — no change; the scratchpad test still fails.
The most concrete anomaly — DC voltage on MISO:
Static multimeter measurement, powered, idle bus, comparing both sides of CN0566's level shifter on both hosts:
| 3.3V (A) side | 1.8V (B) side | |
|---|---|---|
| Raspberry Pi (working) | ~0.0006 V | ~0.436 V |
| ZC702 (failing) | ~3.335 V | ~0.843 V |
Isolation testing: disconnecting the wire at the CN0566 end drops that side to ~1.7V (consistent with the shifter's bus-hold floating state). Disconnecting at the ZC702 end and measuring the free wire end still reads ~3.3V, isolated from CN0566 entirely — confirming the high level originates on the ZC702 side of the connector, independent of CN0566 or the wiring between them.
Question for the community:
- Has anyone run CN0566 (or another ADAR1000-based SPI target device) successfully over ZC702's PMOD headers, given the TXS0108E's documented speed ceiling? Is FMC genuinely required for this, or has anyone gotten reliable SPI over PMOD at reduced clock rates?
- Any known cause for a PMOD signal configured purely as a PS7 SPI input (
spi1_sdi_i, no output driver in the block design, no BD-level pull enabled) sitting at a hard ~3.3V DC level that persists even fully disconnected from the peripheral? Suspect either a populated pull-up on the ZC702 PMOD breakout itself, or a fault in the TXS0108E's auto-sensing behavior under a floating/undriven condition — interested in whether this is a known TXS0108E quirk specifically.
Thanks in advance.



