While doing hand-off to the software, the security settings configured through XMPU are not handed off as expected.
For example, when a region is created through XMPU for DDR under an RPU subsystem, and RPU is added as the master, the rest of the memories and address space is accessible by all masters.
When we create an application in SDK for APU, it creates the application with the entire DDR4 space. This fails while running the application on hardware because the linker script considers the whole address space in DDR to be accessible from APU which is not the case.
User has to create own linker script by considering the XMPU settings.
This is expected to be fixed in the 2016.1 release.