Code difference between the adrv9001-sdk and the Linux drivers in the 2019 release

Greetings,

    I downloaded the adrv9001-sdk-eval-software to have a poke around.  in the pkg/production directory/c_src, there is code here that seems to mirror the driver code in the linux kernel.  Is the code in the SDK the "no-os" code?  

Thank You for your reply.

Regards,

Stephen Beckwith

Parents
  • The SDK is very similar to the No-OS code.

    The No-OS code will take the API code generated by TES and provide drivers for the surrounding components like DMA, DDS cores, ... The API itself just handles the transceiver. The same support drivers are used by other projects like AD9361, AD9371, AD9081, ... 

    The adrv9001-sdk-eval-software is separate and only handles the ADRV9002->7 family.  When new releases of the adrv9001 SDK are made, No-OS and Linux get updated to use the same API eventually.

    You cannot mix adrv9001-sdk and No-OS or their related HDL.

    The Linux driver uses the API internally like No-OS, and will use the same HDL as No-OS.

    -Travis

Reply
  • The SDK is very similar to the No-OS code.

    The No-OS code will take the API code generated by TES and provide drivers for the surrounding components like DMA, DDS cores, ... The API itself just handles the transceiver. The same support drivers are used by other projects like AD9361, AD9371, AD9081, ... 

    The adrv9001-sdk-eval-software is separate and only handles the ADRV9002->7 family.  When new releases of the adrv9001 SDK are made, No-OS and Linux get updated to use the same API eventually.

    You cannot mix adrv9001-sdk and No-OS or their related HDL.

    The Linux driver uses the API internally like No-OS, and will use the same HDL as No-OS.

    -Travis

Children