SDT Driver Support and Compilation Errors

1. SDT Driver Support and Compilation Errors

I'm developing a project on zcu106 using the 2024.2 BSP, and I've noticed that some drivers, e.g. xscugic_g.h, don't seem to fully support SDT (System Device Tree). This is leading to numerous compilation errors when I try to build my project.

In this case. Should I need to add [#ifndef] SDT before every related function​ call?

2. Duplicate Macro Definitions

When I generate a platform from an .xsa file in Vitis and then generate an xintc example. I'm encountering a confusing situation: certain macros, like XPAR_PSU_AFI_2_BASEADDR, appear to be defined twice. I am curious when only PSU AFI related has the issue.

/* Canonical definitions for peripheral PSU_AFI_3 */
#define XPAR_PSU_AFI_2_BASEADDR 0xfd390000
#define XPAR_PSU_AFI_2_HIGHADDR 0xfd39ffff

/* Definitions for peripheral PSU_AFI_2 */
#define XPAR_PSU_AFI_2_BASEADDR 0xfd380000
#define XPAR_PSU_AFI_2_HIGHADDR 0xfd38ffff

Start with xscugic_g.h and the xintc example generated from the platform; inspect how SDT-related guards and the PSU_AFI macros are generated from the .xsa platform. Reproduce the 2024.2 build to identify the source of the compilation errors and duplicate definitions, then document or correct the affected driver and generated headers.