ADRV9002 + ZCU102 workflow

Hello CD95,

I'm sorry to report that your question rather confused us. As explained in the User Guide and in the SD Card imaging guide on the SW Support documents page, TES is designed to connect to the ZCU102 using our SD card image. When you use our image, the ZCU102 hosts a server which all of our SW (including the generated Matlab code you're using) can connect to the platform and control the ADRV9002 device in real-time. We also provide details in our User Guide as to how a customer can go about replacing our code with custom code.

The code you have found on Github is support by a different forum, found here:  Linux Software Drivers  

The Github code base and our TES and SDK packages are completely separate SW packages. We recommend using our SW and SDK, as this gives you access to all the latest APIs as they are developed. It also gets you our support. If you use the Linux based control scheme we cannot support you, as we have no hand in the Linux SW's development.

I hope this helps shed light on the matter.

Best Regards,
Oisín.

Hi Team,

The discussion is really interesting for me.

Once the files are generated with TES, to control the ADRV9002 with my configuration, I need to implement my radio algorithms directly on the board. I don't need to control the board in real time with TES but I need the files generated with TES and my algorithms developed in Matlab or C to work together at system boot.

How can I do this?

Best regards.

Hi Team,

The discussion is really interesting for me.

Once the files are generated with TES, to control the ADRV9002 with my configuration, I need to implement my radio algorithms directly on the board. I don't need to control the board in real time with TES but I need the files generated with TES and my algorithms developed in Matlab or C to work together at system boot.

How can I do this?

Best regards.

Hello LF92,

We have this process detailed in the User Guide, between the System Software Architecture chapter and the Software Integration chapter. There we detail the structure of our SDK, as well as where customer development efforts should be directed.

The long in short of it is this: You use the TES to generate sample C code. You then edit the main.c file of this sample code to perform the application you are interested in, and compile it on the eval platform to ensure that it works as desired, then you go about developing a custom Hardware Abstraction Layer which will allow you to run your custom code on any platform (allowing you to remove the ZCU102 from the design)

This process is detailed in full in the User Guide. Do let me know if you have any further issues, and of course feel free to post further queries to this forum as well!

Best Regards,
Oisín.