ADRV9009
Recommended for New Designs
The ADRV9009 is a highly integrated, radio frequency (RF), agile transceiver offering dual transmitters and receivers, integrated synthesizers, and digital...
Datasheet
ADRV9009 on Analog.com
I finally took delivery of 8 SOMs with carrier cards, after waiting over a year : )
I am having no luck getting them to do the basic boot off the SD card per the getting started wiki: ADRV9009-ZU11EG Quick Start Guide [Analog Devices Wiki] I used the SD card provided, provided a 122.88MHz ref, set mode switches per the picture on the wiki for the new rev. The PG lights on the carrier light up red but the fault ones stay dark. That is correct? On the SOM on the underside two PG LEDs light up, one green the other yellow. The PS init and PS done leds on the carrier never light up. Nothing shows up in the console on my host via the UART. For the hell of it I flipped the mode switches opposite and that seems to get it to try to boot off the QSPI and I see output on the console however it fails to progress much. Any thoughts? My carrier cards came over a year ago right when I ordered everything but the SOMs were severally backordered and took a year to get. Is it possible there is some rev mismatch or firmware update needed? My SOM is Rev-C1 and my carriers are Rev C 2 (or Z?) I have tried two of my 8 units and they both do the same thing.
I appreciate any help you can give me.
Thanks
Jeff
BTW this is the output when I got something to show up on the console:
Release 2021.2 Oct 13 2021 - 07:15:53
NOTICE: BL31: v2.4(release):xlnx_rebase_v2.4_2021.1_update1-23-g9188496b9
NOTICE: BL31: Built : 07:41:24, Oct 13 2021
U-Boot 2021.01 (Oct 12 2021 - 09:28:42 +0000)
CPU: ZynqMP
Silicon: v3
Model: Analog Devices ADRV9009-ZU11EG Rev.B
Board: Xilinx ZynqMP
DRAM: 4 GiB
PMUFW: v1.1
EL Level: EL2
Chip ID: zu11eg
NAND: 0 MiB
MMC: mmc@ff170000: 0
Loading Environment from SPIFlash... SF: Detected n25q512a with page size 512 Bytes, erase size 128 KiB, total 128 MiB
*** Warning - bad CRC, using default environment
In: serial
Out: serial
Err: serial
Bootmode: QSPI_MODE
Reset reason: EXTERNAL
Net:
ZYNQ GEM: ff0b0000, mdio bus ff0e0000, phyaddr 1, interface sgmii
Warning: ethernet@ff0b0000 (eth1) using random MAC address - aa:17:60:15:35:0b
eth1: ethernet@ff0b0000
ZYNQ GEM: ff0e0000, mdio bus ff0e0000, phyaddr 0, interface rgmii-id
Warning: ethernet@ff0e0000 (eth0) using random MAC address - 3a:5f:9b:19:4c:f1
, eth0: ethernet@ff0e0000
Hit any key to stop autoboot: 0
SF: Detected n25q512a with page size 512 Bytes, erase size 128 KiB, total 128 MiB
device 0 offset 0x3e80000, size 0x80000
SF: 524288 bytes @ 0x3e80000 Read: OK
QSPI: Trying to boot script at 20000000
## Executing script at 20000000
Wrong image format for "source" command
QSPI: SCRIPT FAILED: continuing...
JTAG: Trying to boot script at 20000000
## Executing script at 20000000
Wrong image format for "source" command
JTAG: SCRIPT FAILED: continuing...
switch to partitions #0, OK
mmc0 is current device
Scanning mmc 0:1...
libfdt fdt_check_header(): FDT_ERR_BADMAGIC
Scanning disk mmc@ff170000.blk...
** Unrecognized filesystem type **
Found 4 disks
No EFI system partition
BootOrder not defined
EFI boot manager: Cannot load any image
MMC Device 1 not found
no mmc device at slot 1
SF: Detected n25q512a with page size 512 Bytes, erase size 128 KiB, total 128 MiB
device 0 offset 0x3e80000, size 0x80000
SF: 524288 bytes @ 0x3e80000 Read: OK
QSPI: Trying to boot script at 20000000
## Executing script at 20000000
Wrong image format for "source" command
QSPI: SCRIPT FAILED: continuing...
no devices available
NAND: SCRIPT FAILED: continuing...
starting USB...
No working controllers found
USB is stopped. Please issue 'usb start' first.
starting USB...
No working controllers found
USB is stopped. Please issue 'usb start' first.
scanning bus for devices...
Device 0: unknown device
starting USB...
No working controllers found
ethernet@ff0b0000 Waiting for PHY auto negotiation to complete......................................... TIMEOUT !
ethernet@ff0e0000 Waiting for PHY auto negotiation to complete......................................... TIMEOUT !
Ok let me put this thread out of its misery since no is responding anyway. The SD card that ships with the SOM (2019 R2) now is just too old probably. I know its the typical production pipeline problem but I would think that since they just had to respin the SOM design which caused the long lead time they could update the card they send with it? I guess it comes wth the carrier anyway so that would not help.
Anyway I updated to a 2023 R2 and I am up and running now. I will switch to petalinux anyway because that is what my design is in.
Sorry for the delay in response. Good to know things are working on your side.