Hardware:
SOM: ADRV9364-Z7020
Carrier: ADRV1CRR-BOB
Power: dedicated 5V, 2A+ supply that came with the BOB connected directly to the BOB
Symptom: No /dev/ttyUSB* device is ever created, and the FTDI USB-serial device never appears in lsusb output at all — tested on two completely separate computers, connected directly (no hub), using the USB cable that shipped with the carrier board, plugged into the port labeled "USB UART / Console" on the ADRV1CRR-BOB.
LED behavior on the SOM (D3 = PGOOD, D4 = CFG_DONE):
With S1 = SDS: D3 lights and stays solid. D4 lights briefly on power-up, then turns off after ~1 second.
With S1 = SDC: D3 and D4 both light and stay solid continuously, with no flicker — but no USB enumeration and no Ethernet link (NO-CARRIER) in either mode.
Switch positions tried:
S1: tested both SDS and SDC
S3 = 1, S4 = 1
Steps already taken to rule out other causes:
Confirmed direct connection (no hub) on two separate host computers — FTDI device never appears in lsusb.
Confirmed the USB cable is the one that shipped with the carrier board.
Verified BOOT.BIN and devicetree.dtb on the SD card's boot partition are byte-for-byte identical (md5sum match) to the reference files in zynq-adrv9364-z7020-bob/lvds/ on the Kuiper image — confirming the correct board/carrier/interface-mode boot files are active at the root of the boot partition.
Confirmed devicetree.dtb correctly reports Analog Devices ADRV9364-Z7020 (Z7020/AD9364) via strings devicetree.dtb | grep -i adrv.
Reseated the SOM firmly onto all 4 micro-headers on the carrier — no change in behavior.
Confirmed power supply is rated 5V, 2A or higher — connected via the BOB's dedicated power input, not USB.
Checked ip link on the host while the board is powered — the Ethernet adapter shows NO-CARRIER, so no link is established over Ethernet either.
Ran dmesg -w while physically unplugging/replugging the USB cable at the carrier —nothing appeared
Question: Given the SD card content and switches are confirmed correct, and the console port shows zero electrical activity across two hosts and multiple cables/ports, is this indicative of a hardware fault on the ADRV1CRR-BOB's USB-UART circuitry (or the SOM itself)? Are there any additional jumper settings specific to the USB-UART port (as opposed to the USB-OTG port) on this carrier revision that could explain this? Happy to provide board revision/serial numbers and photos if useful for troubleshooting or an RMA determination.
