Post Go back to editing

How to use TES generate C99 code replace no_OS project?

Category: Software
Product Number: ZCU102+ADRV9002
Software Version: Vivado 2022.2,Vitis 2022.2,TES 0.25.0

Hello,

I downloaded hdl and no-OS from ADI's github, used vivado 2022.2 to compile the architecture of zcu102 and ADRV9002, and then used Vitis 2022.2 to do the DMA loopback of no-OS to verify that the architecture has correct transceiver.

Later, when I wanted to use C99 generated by tes to replace no-OS, I found that some files about the Linux system could not be compiled.  Are there any user guide for no-OS?

 

Thank You,

John.

Thread Notes

Top Replies

    •  Analog Employees 
    in reply to rbolboac +2 verified

    Hi ,

    The reference project that we showcase under no-OS/projects/adrv9001 does not support using C99 code generated by TES.

    However, you may use TES to generate a .json profile and use that…

  • Hello ,

    This is the user guide to build project on No-OS: https://wiki.analog.com/resources/no-os/build

    Can you please describe in more details what are you trying to do? Also some details about your setup could be useful.

    Thank you,

    Ramona

  • Hello rbolboac,

    I have successfully validated the architecture of the ZCU102+ ADRV9002 using the ADI github no-OS project.

    The TES parameters can generate c99 after they are set, so I want to verify the c99 of TES with the same HDL architecture in vitis. Can I do this?If so, is there a guide on how to use c99 for no-OS?

    Thank you,

  • Hi ,

    The reference project that we showcase under no-OS/projects/adrv9001 does not support using C99 code generated by TES.

    However, you may use TES to generate a .json profile and use that profile in the no-OS application after converting it to a C string.

    The first 2 files in the screenshot below are the 2 profiles that we converted from TES generated .json to a C string.

    To convert (on Linux or equivalent shell), use the `scripts/json2ctring path/to/file.json` command in your project directory.

    Make sure to migrate the gain tables too if you notice they are different than the ones already in use within the no-OS project.