In this brief tutorial, we shall discuss how the RFDC configuration data gets passed from Hardware to Software in both the Baremetal, and Linux using the HSI API and how the driver uses this information to initialize the RFDC driver.
| Table of Contents |
|---|
Extracting Information from HDF:
When users export to SDK from Vivado, this creates a (Hardware Definition File) HDF file. This HDF is a container file which (among other files), will contain all the Hardware Information needed to build a software application for your target.
...
For example. Here we can see the Base Address. This will be be discussed later in this wiki
Baremetal:
In SDK, the user will build the Board Support Package (BSP). The BSP will use the information in the HDF to know what IP are in hardware, and will add the respective driver for this hardware. it will also allow the user to add any
...
| Warning | ||
|---|---|---|
| ||
If the RFDC IP is added external to the Vivado IP Integrator, then the HDF will not contain this information. User will need to populate this manually |
Linux:
The configuration is passed differently when using the Linux flow. Here, this is passed via a devicetree node generated by the DeviceTree Generator (DTG). The DTG is a TCL based tool, that used the HSI API to extract the node information from the HDF file.
...