Hello, my custom IP has multiple SLAVEBUSINTERFACES for the same cell name, "frf_dsp." When I regenerate our no-os bsp, the #define macros in xparameters only include the first element in this list. Hardcoding this seems uncessary since **almost** all the hooks are in this script to support multiple mem_range or slave_bus_interface properties for a single peripheral.
I looked through C:\Xilinx\SDK\2019.1\scripts\hsm\xillib_sw.tcl and identified that the procedure named
loops through each memory map, but only appends elements with different cell names to the returned list. I have extended this to also export the base and high address of each memrange within the peripheral ("cell").
We can easily override the default BSP scripts by listing our custom versions higher in the bsp search path. Overriding scripts is less obvious. is "xillib_sw.tcl" added to the xsct path through the SDK plugin somewhere?
Short story long, what's the easiest way to preserve my customization? can I "source" my updated procedures when XSCT loads in the sdk instance? Can I modify the script paths somewhere so that calls to ::hsi::utils::xxxx will find my updated version before it finds the distribution default?