Post Go back to editing

ADRV9002 + ZCU106 TES Connection Error

Hi all,

We want to use ADRV9002 Eval board with ZCU106 FPGA. 

First we generated hardware reference design by following steps wirtten here .-> https://wiki.analog.com/resources/eval/user-guides/adrv9002/reference_hdl ( Note that it is configured for ZCU106)

Then for bare-metal test, a software platform is created as written here -> https://wiki.analog.com/resources/eval/user-guides/adrv9002/no-os-setup

This created test environment works fine and we can see spectrum of signal which is provided by LUT in DAC_DMA_EXAMPLE.

The next step was, building this test environment on linux instead of bare-metal. For this purpose, we followed steps written in this page -> https://wiki.analog.com/resources/tools-software/linux-drivers/iio-transceiver/adrv9002 and we achieved successfull result as in bare-metal test.

Due to ease of use we decided to connect FPGA and configure parameters by using TES GUI. At this point we got Connection Failure on TES. An image related with this error is attached below.

Does this TES GUI work only with supported FPGA's (ZCU102 and ZC706) or can it work with other FPGA's as well? If it can work with ZCU106, what is the key point we missed?

Regards,

Emrullah C.

Top Replies

Parents
  • Hello Emrullah C.

    As detailed in our  Quick Start guide and our TES Connection Issues Debug guide, TES only connects to the ZCU102 or the ZC706 platforms using our own SD card image. No other platform can connect to our software and allow for live interaction with the device.

    However, we do recommend that all customers use TES anyway. TES has both a "Demo Mode" which allows users to design their profile in the absence of hardware, and the ability to produce Sample Code in one of 4 languages (C99, C#, Python and MATLAB). Using these 2 features, any customer can design their use-case in TES, produce the sample code, and then port our APIs to a custom platform. This approach allows users to design their own custom Hardware Abstraction Layer, meaning any platform can be used. For example, we're currently building a demo of a Raspberry Pi controlling the ADRV9002. 

    All of this is detailed in the User Guide under the System Software Architecture and Software Integration chapters. There are also multiple customers on this forum who have gone through the migration process. Feel free to read their posts for more details.

    Best Regards,
    Oisín.

Reply
  • Hello Emrullah C.

    As detailed in our  Quick Start guide and our TES Connection Issues Debug guide, TES only connects to the ZCU102 or the ZC706 platforms using our own SD card image. No other platform can connect to our software and allow for live interaction with the device.

    However, we do recommend that all customers use TES anyway. TES has both a "Demo Mode" which allows users to design their profile in the absence of hardware, and the ability to produce Sample Code in one of 4 languages (C99, C#, Python and MATLAB). Using these 2 features, any customer can design their use-case in TES, produce the sample code, and then port our APIs to a custom platform. This approach allows users to design their own custom Hardware Abstraction Layer, meaning any platform can be used. For example, we're currently building a demo of a Raspberry Pi controlling the ADRV9002. 

    All of this is detailed in the User Guide under the System Software Architecture and Software Integration chapters. There are also multiple customers on this forum who have gone through the migration process. Feel free to read their posts for more details.

    Best Regards,
    Oisín.

Children
No Data