Post Go back to editing

Unable to boot ADRV9364-Z7020 with ADRV1CRR-FMC

Category: Software
Product Number: AD9364

Hello, I am trying to setup the ADRV9364-Z7020 with ADRV1CRR-FMC. I am aware that with this SOM+ FMC carrier combination I can’t unlock full functionality like HDMI, etc and as suggested here: https://ez.analog.com/fpga/f/q-a/31714/booting-linux-on-adrv9364-z7020-with-adrv1crr-fmc I have added BOB Z7020 image to the root of the BOOT FAT32 partition (basically the /boot directory).

The switches on the Carrier board are set as SW0- 1 (i.e the switch is towards label s1), SW1- 0, SW2-1, SW3-1, as seen here https://ez.analog.com/fpga/f/q-a/547711/setup-adrv9364-z7020-with-adrv1crr-fmc-using-matlab , sadly there isn't a dot on these switches on the FMC board I have, i am inserting an image for your reference- https://drive.google.com/file/d/1p7dPDONgDOoOblkGCvxP_UnjjKIGcDak/view?usp=sharing. I have also tried all switches on ON position as well as all on OFF position, noticed the same pattern as explained below. 

As soon as I switch the board on after the Hardware setup, the following is noticed:
As it is turned on- 

  • led D4 is yellow for a split second and then goes off and instantly D57 goes blue 
  • Meanwhile D3 is yellow, D58 is red and D52 is faint red.

Additionally, when I run the command:  kermit -l /dev/ttyUSB0 -b 115200  -c

I first run into this

Connecting to /dev/ttyUSB0, speed 115200

 Escape character: Ctrl-\ (ASCII 28, FS): enabled

Type the escape character followed by C to get back,

or followed by ? to see other options.

?Carrier required but not detected.

***********************************

 Hint: To CONNECT to a serial device that

 is not presenting the Carrier Detect signal,

 first tell C-Kermit to:


   SET CARRIER-WATCH OFF

***********************************

C-Kermit 9.0.305 OPEN SOURCE: Alpha.07, 24 Jan 2022, for Linux+SSL (64-bit)

 Copyright (C) 1985, 2022,

  Trustees of Columbia University in the City of New York.

Type ? or HELP for help.

After I set the carrier-watch off and run connect in c-kermit, I get this log and the zynq-uboot interactive terminal is unresponsive.

Kindly help and suggest next steps. Let me know if I have gone wrong somewhere.


  • Hi,

    You are using the wrong switches. Boot switches are on the SOM and not the carrier.

    -Travis

  • Oh I see, thanks, what would the combination be for that? Additionally, how should I leave the carrier switches? 

  • Carrier switches are not connected in HDL.

    Here are the boot modes(Same between all models): https://wiki.analog.com/resources/eval/user-guides/adrv9361-z7035/electrical-specifications#configuration_modes

    Should be on the silkscreen as well.

    -Travis

  • Hello,

    Thank you for that reference. However, even with S1 on logic 0 on the SOM (along with s3 and s4 on logic 1 as recommended), I am still witnessing the exact same behavior as stated above, any other suggestions on where I could be going wrong?

  • What version of the SD card are you using? From which subfolder did you pull boot files from?

    -Travis

  • I am using the SanDisk Ultra 16GB SD Card that came with the the FMC board (PN: AD-FMC SDCARD), I pulled the BOOT.BIN and devicetree.dtb from the zynq-adrv9364-z7020-bob folder and the uImage from the zynq-common folder.

  • Can you provide the current output of UART from power on?

    -Travis

  • Sure. Here you go-

    kermit -l /dev/ttyUSB0 -b 115200 -c
    Connecting to /dev/ttyUSB0, speed 115200
    Escape character: Ctrl-\ (ASCII 28, FS): enabled
    Type the escape character followed by C to get back,
    or followed by ? to see other options.
    ?Carrier required but not detected.
    ***********************************
    Hint: To CONNECT to a serial device that
    is not presenting the Carrier Detect signal,
    first tell C-Kermit to:
    
    SET CARRIER-WATCH OFF
    
    ***********************************
    
    C-Kermit 9.0.305 OPEN SOURCE: Alpha.07, 24 Jan 2022, for Linux+SSL (64-bit)
    Copyright (C) 1985, 2022,
    Trustees of Columbia University in the City of New York.
    Type ? or HELP for help.
    (~/) C-Kermit>set carrier-watch off
    (~/) C-Kermit>show communication
    
    Communications Parameters:
    Line: /dev/ttyUSB0, speed: 115200, mode: local, modem: generic
    Parity: none, stop-bits: (default) (8N1)
    Duplex: full, flow: rts/cts, handshake: none
    Carrier-watch: off, close-on-disconnect: off
    Lockfile: /var/lock/LCK..ttyUSB0
    Terminal bytesize: 8, escape character: 28 (^\)
    
    Carrier Detect (CD): Off
    Dataset Ready (DSR): Off
    Clear To Send (CTS): Off
    Ring Indicator (RI): Off
    Data Terminal Ready (DTR): On
    Request To Send (RTS): On
    
    Type SHOW DIAL to see DIAL-related items.
    Type SHOW MODEM to see modem-related items.
    
    (~/) C-Kermit>connect
    Connecting to /dev/ttyUSB0, speed 115200
    Escape character: Ctrl-\ (ASCII 28, FS): enabled
    Type the escape character followed by C to get back,
    or followed by ? to see other options.
    ----------------------------------------------------
    
    U-Boot 2014.07-dirty (Nov 20 2014 - 17:05:21)
    
    Board: Xilinx Zynq
    I2C: ready
    DRAM: ECC disabled 512 MiB
    MMC: zynq_sdhci: 0
    SF: Detected N25Q256A with page size 256 Bytes, erase size 4 KiB, total 32 MiB
    In: serial
    Out: serial
    Err: serial
    Net: Gem.e000b000
    Hit any key to stop autoboot: 0
    Device: zynq_sdhci
    Manufacturer ID: 3
    OEM: 5344
    Name: SB16G
    Tran Speed: 50000000
    Rd Block Len: 512
    SD version 3.0
    High Capacity: Yes
    Capacity: 14.8 GiB
    Bus Width: 4-bit
    Unknown command 'load' - try 'help'
    Copying Linux from SD to RAM...
    Unknown command 'load' - try 'help'
    switch to partitions #0, OK
    mmc0 is current device
    Unknown command 'part' - try 'help'
    env - environment handling commands
    
    Usage:
    env default [-f] -a - [forcibly] reset default environment
    env default [-f] var [...] - [forcibly] reset variable(s) to their default values
    env delete [-f] var [...] - [forcibly] delete variable(s)
    env edit name - edit environment variable
    env export [-t | -b | -c] [-s size] addr [var ...] - export environment
    env import [-d] [-t | -b | -c] addr [size] - import environment
    env print [-a | name ...] - print environment
    env run var [...] - run commands in an environment variable
    env save - save environment
    env set [-f] name [arg ...]
    
    Unknown command 'fstype' - try 'help'
    (Re)start USB...
    USB0: USB EHCI 1.00
    scanning bus 0 for devices... 1 USB Device(s) found
    USB1: usb1 wrong num MIO: 0, Index 1
    lowlevel init failed
    scanning usb for storage devices... 0 Storage Device(s) found
    
    USB device 0: unknown device
    (Re)start USB...
    USB0: USB EHCI 1.00
    scanning bus 0 for devices... 1 USB Device(s) found
    USB1: usb1 wrong num MIO: 0, Index 1
    lowlevel init failed
    scanning usb for storage devices... 0 Storage Device(s) found
    Gem.e000b000 Waiting for PHY auto negotiation to complete...... done
    BOOTP broadcast 1
    BOOTP broadcast 2
    BOOTP broadcast 3
    BOOTP broadcast 4
    BOOTP broadcast 5
    
    Retry count exceeded
    Unknown command 'pxe' - try 'help'
    (Re)start USB...
    USB0: USB EHCI 1.00
    scanning bus 0 for devices... 1 USB Device(s) found
    USB1: usb1 wrong num MIO: 0, Index 1
    lowlevel init failed
    scanning usb for storage devices... 0 Storage Device(s) found
    Gem.e000b000:0 is connected to Gem.e000b000. Reconnecting to Gem.e000b000
    Gem.e000b000 Waiting for PHY auto negotiation to complete...... done
    BOOTP broadcast 1
    BOOTP broadcast 2
    BOOTP broadcast 3
    BOOTP broadcast 4
    BOOTP broadcast 5
    
    Retry count exceeded
    Gem.e000b000:0 is connected to Gem.e000b000. Reconnecting to Gem.e000b000
    Gem.e000b000 Waiting for PHY auto negotiation to complete....... done
    BOOTP broadcast 1
    BOOTP broadcast 2
    BOOTP broadcast 3
    BOOTP broadcast 4
    BOOTP broadcast 5
    
    Retry count exceeded
    zynq-uboot>
    
    

    and the zynq-uboot terminal is unresponsive.

  • If you are having issues with ckermit I would probably use screen or putty.

    sudo screen /dev/ttyUSB0 115200

    Anyway, to me it looks like the uEnv.txt file is corrupted which tell uboot how to load things. I would recommend burning a new SD card, 2022-R2 specifically, which can be downloaded from here: https://wiki.analog.com/resources/tools-software/linux-software/kuiper-linux?redirect=1

    -Travis

  • Ok, thanks for the suggestion. I will try that and get back to you, thanks!