AM263P4: SBL OSPI Multicore example crashes when built with latest SDK/SysConfig

Tool/software:

We are attempting to use the sbl_ospi_multicore_elf/am263px-cc example project.  The following steps allow us to successfully execute the boot code:

1. Import the sbl_ospi_multicore_elf/am263px-cc project into CCS version 20.1.1.8
2. Add the line for loop_forever() immediately upon entering the main() function.
3. Build the project.
4. Use UniFlash to program the generated sbl_ospi_multicore_elf_am263px-cc_r5fss0-0_nortos_ti-arm-clang.tiimage onto the part.
5. Cycle power.
6. Back in CCS, run a debug session and connect to the Cortex_R5_0 core without gel files.
7. Load the sbl_ospi_multicore_elf_am263px-cc_r5fss0-0_nortos_ti-arm-clang.out symbols file.
8. Code successfully connects
9. Change the value of the loop value to 0 to allow the main function to continue.
10. step through and observe that main() is able to execute all the way through.

However, any change (even things aren't changes, but cause the example.syscfg to be re-saved) will cause the generated code to fail. steps to reproduce:

1. Import the sbl_ospi_multicore_elf/am263px-cc project into CCS version 20.1.1.8
2. Add the line for loop_forever() immediately upon entering the main() function.
3. open the example.syscfg
4. Change the Clock Instance to RTI1, then immediately change it back to RTI0. This will force the sysconfig file to need to be saved (even though no ACTUAL changes were made) and subsequently cause the Generated Source files to be updated.
5. Build the project.
6. Use UniFlash to program the generated sbl_ospi_multicore_elf_am263px-cc_r5fss0-0_nortos_ti-arm-clang.tiimage onto the part.
7. Cycle power.
8. Back in CCS, run a debug session and connect to the Cortex_R5_0 core without gel files.
9. Load the sbl_ospi_multicore_elf_am263px-cc_r5fss0-0_nortos_ti-arm-clang.out symbols file.
10. Code successfully connects
11. Change the value of the loop value to 0 to allow the main function to continue.
12. step through and observe that the code will crash at the Board_driversOpen() function.

I have tried this using the AM263Px SDK versions 10.01.00.31 and 10.02.00.15. I have also tried this with SysConfig versions 1.22.0, 1.23.0, and 1.24.0. all produce the same result. 

The end result is that we cannot make any changes to the SysConfig without creating code which fails in ways unrelated to changes we've made.