I wanted to ask you all a question surrounding some code I saw in sdt_flow.py. For a little bit of background, our company is using the SDT workflow in AMD 2024.2 in conjunction with your K26 SoM platform on a custom carrier.
In sdt_flow.py I see the following functions:
def PmuMicroblaze(self):
''' pmu-microblaze is ALWAYS Baremetal, no domain'''
logger.info('Generating microblaze baremetal configuration for ZynqMP PMU')
self.MBTuneFeatures()
extra_conf_str = 'TARGET_CFLAGS += "-DVERSAL_PLM=1"\n' # <-- Is this an issue?
self.GenLibxilFeatures('', extra_conf_str)
def PmcMicroblaze(self):
logger.info('Generating microblaze baremetal configuration for Versal PMC (PLM)')
self.MBTuneFeatures()
extra_conf_str = 'TARGET_CFLAGS += "-DVERSAL_PLM=1"\n'
self.GenLibxilFeatures('', extra_conf_str)
def PsmMicroblaze(self):
logger.info('Generating microblaze baremetal configuration for Versal PSM')
self.MBTuneFeatures()
extra_conf_str = 'TARGET_CFLAGS += "-DVERSAL_psm=1"\n'
self.GenLibxilFeatures('', extra_conf_str)To me, it looks like we might be making a mistake by setting -DVERSAL_PLM=1 for the ZynqMP PMU, but I wanted to ask to see what you all thought, as there are quite a few pieces here I am unfamiliar with. I have confirmed that the VERSAL_PLM define is active by running bitbake -e mc:<OUR_MACHINE>-microblaze-pmu:pmu-firmware | grep '^TARGET_CFLAGS=‘.
Thank you in advance!
I wanted to ask you all a question surrounding some code I saw in
sdt_flow.py. For a little bit of background, our company is using the SDT workflow in AMD 2024.2 in conjunction with your K26 SoM platform on a custom carrier.In sdt_flow.py I see the following functions:
To me, it looks like we might be making a mistake by setting -DVERSAL_PLM=1 for the ZynqMP PMU, but I wanted to ask to see what you all thought, as there are quite a few pieces here I am unfamiliar with. I have confirmed that the VERSAL_PLM define is active by running
bitbake -e mc:<OUR_MACHINE>-microblaze-pmu:pmu-firmware | grep '^TARGET_CFLAGS=‘.Thank you in advance!