adrv9001-sdk hardware addresses

I am able to successfully build the adrv9001-sdk.

However, I have a custom platform and I do not see where the SDK gets its addressing for the IP.

The notes state that the zc706 platform is used, but I do not see any addressing for this platform.

There is no hardware importing for this sdk and no xparameters.h.

So how do I map the IP to the custom hardware addressing.

Is there an example of this?

Modifying the HAL in some way?

Thanks

  • +1
    •  Analog Employees 
    on Apr 9, 2021 10:10 AM in reply to swie

    Hi Dan,

    Yes, just got a response late yesterday evening. Here is everything the SW engineer gave me:

    There is NO Xilinx peripherals or IP cores in MPG’s design (TES SD card image). That is only in SDG (IIO scope or No-OS)

    You don’t see any AXI_QUAD_SPI or you will not find any matching registers, because it is NOT there.

    As to what you should use, it is a decision only you can make.

    All of them work same, but have different features and implementation.

    If – and only If—you use our SPI core, will we support you.

    Here is a comparison of all options you mentioned:

    1. AXI_MSPI
      1. Analog Devices IP Core/Peripheral.
      2. What is in MPG’s HDL (I think this is what you call SDK, which is not technically correct).
      3. This is fully an ADI design and supports some specific things (e.g. frequency hopping and such).
      4. Drivers only in user space.
    2. AXI_QUAD_SPI:
      1. Xilinx IP Core/Peripheral (Soft)
      2. This is used in SDG’s HDL for non SoC devices.
      3. Drivers part of Xilinx’s Kernel/User space module.
    3. PS7/PSU SPI (Zynq SPI):
      1. Part of PS7/PSU (Synopsys or Cadence?) Hard IP Core.
      2. This is used in SDG’s HDL, SoC devices.
      3. Drivers part of Xilinx’s Kernel/User space module.

    The AXI SPI engine is different (though it could be used with some tweaks), it is meant for precision converters and such where ‘data’ is collected through the SPI interface (i.e. it serves as a both control + data port, (optional)).

    I hope this clarifies things for you. If not feel free to post another response here. Do also let me know about removing your duplicate question on the Design Support Forum!

    Best Regards,
    Oisín.