03-19-2019 10:35 AM
I'm working on updating our BSP and development tools to Petalinux 2018.3 from 2018.2 for our ZCU111. I've used the ZCU111 BSP on the petalinux download page as well as the BSP provided with the ZCU111 RFSoC RF Data Converter Evaluation tools.
Regardless of which BSP I use, the xparameters.h file no longer appears in the sysroot generated by Petalinux. In 2018.2 the xparamaters.h file was under /usr/include. Our applications no longer build against the sysroot with the 2018.3 crossbuild tools since xparameters.h isn't in the sysroot.
Is there a seperate command to force the xparamaters.h file be generated as part of the petalinux flow?
03-20-2019 06:13 AM
Previous to 2018.3, the rfdc used the xparams to populate the config params for the driver. However, this info is now passed via the devicetree in 2018.3
03-20-2019 06:57 AM
Does this mean that Xilinx is pulling support for other baremetal drivers from linux using libmetal?
From what I see most of the other baremetal drivers still require the xparameters file. Is there a way to generate and include the xparameters file in the sysroot in the 2018.3 petalinux flow?
03-20-2019 12:08 PM
No, for baremetal you would build the bsp. The xparameters.h would be created here.
I was answering with respect to linux as you mentioned petalinux