2.8. Banked SRAM subsystem

The IoT Subsystem infrastructure supports up to four 32KB SRAMs. At least one 32KB SRAM must be implemented (SRAM bank 0).

If a SRAM bank is not implemented and the corresponding MTXREMAP bits are 1, then the corresponding address space is mapped to the AHB Slave expansion port of the interconnect.

In Figure 2.5, the MTXREMAP signals from the configuration logic are static during functional operation.

The SRAM modules are outside of the IoT Subsystem. The IoT Subsystem does not implement retention or power-down supports for the SRAMs. It is the responsibility of the SoC integration to implement power domains for the SRAM, control the power modes of the SRAM banks with a SoC level PMU.

The AHB2SRAM bridge always responds with OKAY to all AHB accesses, even if the connected SRAM is not functional because for example it is powered-down or in retention mode.

It is the responsibility of the software to not read or write the SRAMs when they are not functional. If the SW tries to access non-accessible SRAM, the AHB2SRAM bridge implementation ensures that system will not go to deadlock state because of a non-responsive SRAM. Read data is implementation specific.

Figure 2.5. SRAM interface

To view this graphic, your browser must support the SVG format. Either install a browser with native support, or install an appropriate plugin such as Adobe SVG Viewer.

See also SRAM signals.

Copyright © 2015. All rights reserved.ARM DDI 0551A