Users can validate if the metadata was populated into the config file in the domain generated in the Platform in the Vitis IDE workspace. For example, below is the xgpio_g.c file from the compiled platform with a led_domain at platform/psu_cortexa53_0/led_domain/bsp/libsrc/gpio/src. This config file is generated using the Lopper framework using the required parameters in the drivers YAML file to create the XGpio_Config as specified in the driver YAML file too.
#include "xgpio.h"
XGpio_Config XGpio_ConfigTable[] __attribute__ ((section (".drvcfg_sec"))) = {
{
"xlnx,axi-gpio-2.0", /* compatible */
0xa0000000, /* reg */
0x0, /* xlnx,interrupt-present */
0x0, /* xlnx,is-dual */
0xffff, /* interrupts */
0xffff, /* interrupt-parent */
0x8 /* xlnx,gpio-width */
},
{
NULL
}
};
Users can see this metadata passed ot the XGpio struct used in the application in the Vitis Debugger
