ADRV 9002 Eval Board and ZCU102 platform

Hi everybody,

I need to start the evaluation board for ADRV9002.

The set-up I'm using is the following:

1.   ZCU102  FPGA carrier board ( with 1.1 revision marked on the PCB)

2.  ADRV9002XBCZ NP/W1    ( this seems to be the C0 silicon revision)

3.  SD card ( that comes with the ADRV9002 dev board) marked as :  ADRV9001  TES software R0.2  2020.12

4.  ARGO Navis 0.11.0  

Starting the set-up in the configuration above results in failure to load the SD card image ( no feedback at all ) and seems that the SoC is not configured at all.

Can you please le me know  what SD card do I need in order to get this running ?

Thank you in advance,

Cristian

Parents
  • 0
    •  Analog Employees 
    on Jun 18, 2021 7:59 AM

    Hi Cristian, 

    First thing to note is that there has been plenty of updates to the Transceiver Evaluation Software or TES (ARGO Nevis.exe) we are now on version 0.16.0 and this can be downloaded from the 'Wideband RF Transceiver Evaluation Software' link in the software section of the product page here.

    The image on that SD card might be a default one for the ZC706 platform, so to update this to the latest version of the ZCU102 to work with TES 0.16.0 you can follow this SD card imaging guide here. This will go through the step by step to reimage the SD card for your platform. 

    If you run into any other issues let me know

    Regards 

  • Hi Ruari,

    Now, the ZC102 boots up correctly.

    I have managed to see that it responds to ping so, it sees that everything is ok with ZC102.

    When I try to connect the TES, I get an error.

    Could you please take a look?

    Cristian

  • Hi Ruari,

    This is strange.

    I think I saw someone with the same problem.

    I don't know if safe to try one with the B0 board. it looks very good from hardware perspective, please see attached.

    I can not use the TES since it does not communicate with the ZCU102 board, any attempt to update the firmware or boot returns errors.

    Any other ideas ?:)

    Cristian

  • 0
    •  Analog Employees 
    on Jun 21, 2021 2:36 PM in reply to ctanase@smartegun.com

    Hi Cristian, 

    That video shows a good setup, the power LEDs on the EVB are fine and the FPGA LEDs are also doing what they should be so the SD card image is ok. 

    You can connect the B0 board to the FPGA and connect in TES it can connect, the writing to it with SDK 16 wont always work because its not supported but it can connect fine. That might eliminate TES and indicate the C0 board has an issue. 

    Another thing to try is to use PuTTY to log into the board just to make sure that the IP addresses and the firewall settings are all ok. 

    Using PuTTY start a new SSH session with the following settings (if DHCP is not being used):

    • IP address: 192.168.1.10
    • Port: 22
    • Username: root
    • Password: analog
  • Hi Ruari,

    Thank you very much for your time & support.

    In fact, the mounting the B0 board results in the same behavior. All LED's are Ok , TES does not connect.

    I am connected with putty 192.168.1.10 & port 22  but  the server still does not launch.

    Even more. I have tried with other two different SD cards made today. Same result.

    Please see attached.

    Cristian

  • 0
    •  Analog Employees 
    on Jun 21, 2021 5:33 PM in reply to ctanase@smartegun.com

    Yeah it seems there is an issue with your SD card. How did you manage to image the SD card exactly?
    When I look in the folder there should be the following files

    root@linaro-developer:/home/analog/adrv9001_server/resources/Adi.Adrv9001.Server# ls
    Adrv9001Server_C0_48.8.6 adm1293Log.txt adrv9001Log.txt fpga9001Log.txt

    Looks like the server version on your SD card is not the latest one.

  • Yes,

    As I have mentioned early in the thread, it seems that I don't have the C0 server.

    The card was made following the instructions in 

    •  SD Card image (SDK 13 or higher)

    The file downloaded by the ADVRV9001 Imaging utility was : "adrv9001_sdcard_8.1.2"

         One mention would be that " Imaging utility"  tool did not start automatically the detNet Disk Imager.

        1. I have formatted the card with ADRV9001 Disk Imaging ( during this time the "adrv9001_sdcard_8.1.2" was downloaded

        2. I have opened the dotNet Disk Imager, write these files on the SD card.

        3. Last step ( step 2: in ADRV disk Imaging ), I have selected the drive and ZCU102 platform & download files.

    That's it.

    Cristian

          

Reply
  • Yes,

    As I have mentioned early in the thread, it seems that I don't have the C0 server.

    The card was made following the instructions in 

    •  SD Card image (SDK 13 or higher)

    The file downloaded by the ADVRV9001 Imaging utility was : "adrv9001_sdcard_8.1.2"

         One mention would be that " Imaging utility"  tool did not start automatically the detNet Disk Imager.

        1. I have formatted the card with ADRV9001 Disk Imaging ( during this time the "adrv9001_sdcard_8.1.2" was downloaded

        2. I have opened the dotNet Disk Imager, write these files on the SD card.

        3. Last step ( step 2: in ADRV disk Imaging ), I have selected the drive and ZCU102 platform & download files.

    That's it.

    Cristian

          

Children
  • 0
    •  Analog Employees 
    on Jun 22, 2021 11:49 AM in reply to ctanase@smartegun.com

    Hi Cristian, 

    Ok, that seems odd. I'll have a look into this today and use a clean pc to image an SD card and try recreate your issue. 

  • 0
    •  Analog Employees 
    on Jun 22, 2021 4:57 PM in reply to ctanase@smartegun.com

    Hi Cristian, 

    We could not recreate this error on a clean PC so I have logged a bug with our SW developers to see what could be causing this. In particular why the Disk Imager did not start up automatically. 
    The downloaded file is a correct version but when imaged it seems to be incorrect. I will keep you updated

    Regards

  • Hi Ruari,

    I am using Windows 10.

    The path to the folders seems to be different.

    Anyway, this does not explain why I'm not able to see on my SoC board the correct server (C0 server).

    If you download the adrv9001_sdcard_8.1.2.zip file and you have there the C0 server, this is more than strange....

    Thank you for your help,

    Cristian

  • 0
    •  Analog Employees 
    on Jun 23, 2021 1:29 PM in reply to ctanase@smartegun.com

    Hi Cristian, 

    On the imager not opening itself the only suggestion would be ensure everything is installed as elevated/admin.

    Besides that issue it looks like the ZCU102 is booting ok which is a vote of confidence on the SD card. 

    Once ZCU102 is booted the rest is up to the TES. When TES is first open it will update the home/analog/adrv9001_server folder with the necessary files, including the correct server in home/analog/adrv9001_server/Adi.Adrv9001.Server/. If a B0 board is connected a B0 server will be placed here. If a C0 board is connected a C0 server will be placed here.

    You can manually do this process with the File->Force Update Platform.

    I would suggest the following:

    • Connect C0 board to the correct FMC connector (if not connected the server won't start)
    • Open TES
    • File->Force Update Platform step
    • Connect to platform via Putty (or other) and ensure the home/analog/adrv9001_server/Adi.Adrv9001.Server/ folder is present and contains Adrv9001Server_C0_VERSION
    • Back to TES and click Connect
    • If it connects
      • Great
    • If it does not connect
      • back to putty and navigate to home/analog/adrv9001_server/resources/Adi.Adrv9001.Server/
      • run command "ps -aux | grep ./Adrv9001Server_C0_VERSION"
      • identify is a ./Adrv9001Server_C0_VERSION process exists
      • If it exists, run  command "kill -9 PROCESS_ID"
      • run "./Adrv9001Server_C0_VERSION"
      • 'VERSION' in the above commands. currently should be '48.8.6'
      • Output should look like: