| Electronic Components Datasheet Search |
|
STM32U575VG Datasheet(PDF) 27 Page - STMicroelectronics |
|
|
|||||||||||||||||||||||||||||
STM32U575VG Datasheet(HTML) 27 Page - STMicroelectronics |
|
27 / 329 page ![]() DS13737 Rev 6 27/329 STM32U575xx Functional overview 88 3.5 Embedded SRAMs Five SRAMs are embedded in the STM32U575xx devices, each with specific features. SRAM1, SRAM2, and SRAM3 are the main SRAMs. SRAM4 is in the SRAM used for peripherals LPBAM (low-power background autonomous mode) in Stop 2 mode. These SRAMs are made of several blocks that can be powered down in Stop mode to reduce consumption: • SRAM1: three 64-Kbyte blocks (total 192 Kbytes) • SRAM2: 8-Kbyte + 56-Kbyte blocks (total 64 Kbytes) with optional ECC. In addition SRAM2 blocks can be retained in Standby mode. • SRAM3: eight 64-Kbyte blocks (total 512 Kbytes) with optional ECC. When ECC is enabled, 256 Kbytes support ECC and 192 Kbytes of SRAM3 can be accessed without ECC. • SRAM4: 16 Kbytes • BKPSRAM (backup SRAM): 2 Kbytes with optional ECC. The BKPSRAM can be retained in all low-power modes and when VDD is off in VBAT mode, but not in Shutdown mode. 3.5.1 SRAMs TrustZone security When the TrustZone security is enabled, all SRAMs are secure after reset. The SRAM1, SRAM2, SRAM3, SRAM4 can be programmed as secure or non-secure by blocks, using the MPCBB (block-based memory protection controller). The granularity of SRAM secure block based is a page of 512 bytes. Backup SRAM regions can be programmed as secure or non-secure with watermark, using the TZSC (TrustZone security controller) in the GTZC (global TrustZone controller). 3.5.2 SRAMs privilege protection The SRAM1, SRAM2, SRAM3, SRAM4 can be programmed as privileged or unprivileged by blocks, using the MPCBB. The granularity of SRAM privilege block based is a page of 512 bytes. Backup SRAM regions can be programmed as privileged or unprivileged with watermark, using the TZSC (TrustZone security controller) in the GTZC (global TrustZone controller). 3.6 TrustZone security architecture The security architecture is based on Arm TrustZone with the Armv8-M main extension. The TrustZone security is activated by the TZEN option bit in the FLASH_OPTR register. When the TrustZone is enabled, the SAU (security attribution unit) and IDAU (implementation defined attribution unit) define the access permissions based on secure and non-secure state. • SAU: up to eight SAU configurable regions are available for security attribution. • IDAU: It provides a first memory partition as non-secure or non-secure callable attributes. It is then combined with the results from the SAU security attribution and the higher security state is selected. |
|
Link URL |
| Does ALLDATASHEET help your business so far? [ DONATE ] |
About Alldatasheet | Advertisement | Contact us | Privacy Policy | Link to Datasheet | Link Exchange | Manufacturer List All Rights Reserved©Alldatasheet.com |
| Russian : Alldatasheetru.com | Korean : Alldatasheet.co.kr | Spanish : Alldatasheet.es | French : Alldatasheet.fr | Italian : Alldatasheetit.com Portuguese : Alldatasheetpt.com | Polish : Alldatasheet.pl | Vietnamese : Alldatasheet.vn Indian : Alldatasheet.in | Mexican : Alldatasheet.com.mx | British : Alldatasheet.co.uk | New Zealand : Alldatasheet.co.nz |
|
Family Site : ic2ic.com |
icmetro.com |