ADRV9009 SOM/carrier Card issue

Jacob M on Nov 30, 2021

We are running into an issue when performing ADRV9009-ZU11EG Quick Start Guide. When checking if all devices are present we are missing adm1177:

Additionally, for the JESD204B link status we don't receive the correct printout:

When checking if there is the clock chip lock status on the carrier/som we don't receive a response:

When comparing the printout of our terminal printout vs the quick start guide I can see we are in QPSI boot mode vs the quick start guide is in boot mode LVL_SHFT_SD_MODE1. Although it prints that we are booting in QPSI mode the mode selected on the carrier card is SD1 mode(1110 for S13-S16).

We haven't changed any of the jumper configurations for the carrier card from how we received it but this could possibly be the reason we are not booting properly. Any suggestions for why we are running into this issue?

Top Replies

imoldovan
May 23, 2022 +1 suggested
Hello Jacob M ,

Apologies for the big delay, we have missed somehow your question.
I believe you managed to solve your issue in the meantime?

Best regards,
Iulia

0 mhennerich

on Dec 1, 2021 7:06 AM
You didn't say anything about the software you're using.

Can you please try to use the latest: 28 July 2021 release candidate (2019_R2) image from here:

https://wiki.analog.com/resources/tools-software/linux-software/zynq_images

-Michael
Cancel
Up 0 Down

Reply

Verify Answer

Cancel
0 Jacob M on Dec 2, 2021 12:38 AM in reply to mhennerich

Hi Michael,

I am using the newest version image. No matter which way I configure the boot pins I always boot in QSPI mode which I believe is the issue, any suggestions?

Regards,

Jacob
Cancel
Up 0 Down

Reply

Verify Answer

Cancel
0 mhennerich

on Dec 2, 2021 6:55 AM in reply to Jacob M
Can you post a picture of your carrier and all boot messages captured via the USB UART connection?

-Michael
Cancel
Up 0 Down

Reply

Verify Answer

Cancel
0 Jacob M on Dec 2, 2021 3:16 PM in reply to mhennerich

Hi Michael,

Below are the two messages that print for me, Let me know if you need any additional information.

Carrier Board:

Boot configuration: SD boot (0001 for Rev B)

U-Boot ZU11EG xilinx-v2015.1-dirty-21438-g7a118f3b49-dirty (Apr 07 2020 - 09:59:46 +0300) Analog Devices Inc. ADR9009-ZU11EG

I2C: ready
DRAM: 4 GiB
EL Level: EL2
Chip ID: zu11eg
MMC: sdhci@ff170000: 0 (SD)
Using default environment

In: serial@ff010000
Out: serial@ff010000
Err: serial@ff010000
Bootmode: QSPI_MODE
Net: ZYNQ GEM: ff0b0000, phyaddr 1, interface sgmii
i2c_mux_set: could not set mux: id: 5 chip: 74 channel: 0
I2C EEPROM MAC address read failed

Warning: ethernet@ff0b0000 (eth1) using random MAC address - 56:f3:fd:07:d3:fa
eth1: ethernet@ff0b0000ZYNQ GEM: ff0e0000, phyaddr 0, interface rgmii-id
I2C EEPROM MAC address read failed

Warning: ethernet@ff0e0000 (eth0) using random MAC address - f2:53:d3:b1:af:27
, eth0: ethernet@ff0e0000
Hit any key to stop autoboot: 2 1 0
SF: Detected n25q512a with page size 512 Bytes, erase size 128 KiB, total 128 MiB
device 0 offset 0x2000000, size 0x20000
SF: 131072 bytes @ 0x2000000 Read: OK
device 0 offset 0x2100000, size 0x1d8c29c
SF: 30982812 bytes @ 0x2100000 Read: OK
## Loading kernel from FIT Image at 03000000 ...
Using 'conf@2' configuration
Trying 'kernel@0' kernel subimage
Description: Linux Kernel
Type: Kernel Image
Compression: uncompressed
Data Start: 0x030000dc
Data Size: 27431424 Bytes = 26.2 MiB
Architecture: AArch64
OS: Linux
Load Address: 0x00080000
Entry Point: 0x00080000
Hash algo: sha1
Hash value: 53fef3eb44a4cb4c9038a3a52ca066caa924e08f
Verifying Hash Integrity ... sha1+ OK
## Loading ramdisk from FIT Image at 03000000 ...
Using 'conf@2' configuration
Trying 'ramdisk@0' ramdisk subimage
Description: ramdisk
Type: RAMDisk Image
Compression: gzip compressed
Data Start: 0x04a48118
Data Size: 3423119 Bytes = 3.3 MiB
Architecture: AArch64
OS: Linux
Load Address: unavailable
Entry Point: unavailable
Hash algo: sha1
Hash value: 1d14a853aec56172bbe3378b9eb8d1067bd80eaf
Verifying Hash Integrity ... sha1+ OK
## Loading fdt from FIT Image at 03000000 ...
Using 'conf@2' configuration
Trying 'fdt@1' fdt subimage
Description: zynqmp-adrv9009-zu11eg-revb-adrv2crr-fmc-revb
Type: Flat Device Tree
Compression: uncompressed
Data Start: 0x04a38a28
Data Size: 63035 Bytes = 61.6 KiB
Architecture: AArch64
Hash algo: sha1
Hash value: 1f712e90f8f033051af7a091586818472d0df66e
Verifying Hash Integrity ... sha1+ OK
Booting using the fdt blob at 0x4a38a28
Loading Kernel Image ... OK
Loading Ramdisk to 7db78000, end 7debbb8f ... OK
Loading Device Tree to 000000000ffed000, end 000000000ffff63a ... OK

QSPI boot(0010):

U-Boot ZU11EG xilinx-v2015.1-dirty-21438-g7a118f3b49-dirty (Apr 07 2020 - 09:59:46 +0300) Analog Devices Inc. ADR9009-ZU11EG

I2C: ready
DRAM: 4 GiB
EL Level: EL2
Chip ID: zu11eg
MMC: sdhci@ff170000: 0 (SD)
Using default environment

In: serial@ff010000
Out: serial@ff010000
Err: serial@ff010000
Bootmode: QSPI_MODE
Net: ZYNQ GEM: ff0b0000, phyaddr 1, interface sgmii
i2c_mux_set: could not set mux: id: 5 chip: 74 channel: 0
I2C EEPROM MAC address read failed

Warning: ethernet@ff0b0000 (eth1) using random MAC address - 92:f5:7b:0d:fd:be
eth1: ethernet@ff0b0000ZYNQ GEM: ff0e0000, phyaddr 0, interface rgmii-id
I2C EEPROM MAC address read failed

Warning: ethernet@ff0e0000 (eth0) using random MAC address - b2:51:51:b7:b5:04
, 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 0x2000000, size 0x20000
SF: 131072 bytes @ 0x2000000 Read: OK
device 0 offset 0x2100000, size 0x1d8c29c
SF: 30982812 bytes @ 0x2100000 Read: OK
## Loading kernel from FIT Image at 03000000 ...
Using 'conf@2' configuration
Trying 'kernel@0' kernel subimage
Description: Linux Kernel
Type: Kernel Image
Compression: uncompressed
Data Start: 0x030000dc
Data Size: 27431424 Bytes = 26.2 MiB
Architecture: AArch64
OS: Linux
Load Address: 0x00080000
Entry Point: 0x00080000
Hash algo: sha1
Hash value: 53fef3eb44a4cb4c9038a3a52ca066caa924e08f
Verifying Hash Integrity ... sha1+ OK
## Loading ramdisk from FIT Image at 03000000 ...
Using 'conf@2' configuration
Trying 'ramdisk@0' ramdisk subimage
Description: ramdisk
Type: RAMDisk Image
Compression: gzip compressed
Data Start: 0x04a48118
Data Size: 3423119 Bytes = 3.3 MiB
Architecture: AArch64
OS: Linux
Load Address: unavailable
Entry Point: unavailable
Hash algo: sha1
Hash value: 1d14a853aec56172bbe3378b9eb8d1067bd80eaf
Verifying Hash Integrity ... sha1+ OK
## Loading fdt from FIT Image at 03000000 ...
Using 'conf@2' configuration
Trying 'fdt@1' fdt subimage
Description: zynqmp-adrv9009-zu11eg-revb-adrv2crr-fmc-revb
Type: Flat Device Tree
Compression: uncompressed
Data Start: 0x04a38a28
Data Size: 63035 Bytes = 61.6 KiB
Architecture: AArch64
Hash algo: sha1
Hash value: 1f712e90f8f033051af7a091586818472d0df66e
Verifying Hash Integrity ... sha1+ OK
Booting using the fdt blob at 0x4a38a28
Loading Kernel Image ... OK
Loading Ramdisk to 7db78000, end 7debbb8f ... OK
Loading Device Tree to 000000000ffed000, end 000000000ffff63a ... OK
Cancel
Up 0 Down

Reply

Verify Answer

Cancel
0 Jacob M on Dec 7, 2021 10:03 PM in reply to mhennerich

Hi Michael,

Any updates on this issue?

regards,

Jacob
Cancel
Up 0 Down

Reply

Verify Answer

Cancel
0 Jacob M on Dec 8, 2021 9:21 PM in reply to mhennerich

Hi,

Update:

I was mistaken by the boot pin configuration based on the starting guide, the console output below is what is outputted in QSPI mode.

When I boot in SD mode, I do no receive a console output(for both carrier/SOM SD boots) with no LEDs on. after a minute of running, the error LED turns on(DS8). The carrier SD is not changed from what we received, the SOM SD should be etched with the latest SD software revision.

Regards,

Jacob
Cancel
Up 0 Down

Reply

Verify Answer

Cancel
0 imoldovan

on May 23, 2022 11:51 AM
Hello Jacob M ,

Apologies for the big delay, we have missed somehow your question.
I believe you managed to solve your issue in the meantime?

Best regards,
Iulia
Cancel
Up +1 Down

Reply

Verify Answer

Reject Answer

Cancel