You will find, as in another thread, that a 'single access' (i.e., unaligned 32-bit) that attempts to CROSS the boundary nets a hard-fault:
NOTE
Burst-access cannot occur across the 0x2000_0000 boundary
that separates the two SRAM arrays. The two arrays should be
treated as separate memory ranges for burst accesses.
If 'nothing else' the split of SRAM allows two masters independent, non-interference simultaneous access (one to each) thru the crossbar switch.
The following simultaneous accesses can be made to different logical halves of the
SRAM:
• Core code and core system
• Core code and non-core master
• Core system and non-core master
The 'best' way to force particular elements to particular address is by defining them as a section thru the linker. You can 'force' an address in your compiler, but then you are 'on your own' to insure no overlap by the linked objects.
NO SRAM contents are 'directly' affected by reset, but NONE survives power-cycle. Your device MAY have a 32-byte VBAT register file that, as battery-backed, retains thru power-cycle.