| 数据搜索系统,热门电子元器件搜索 |
|
STM32U535NET6QTR 数据表(PDF) 26 Page - STMicroelectronics |
|
|
|||||||||||||||||||||||||||||
STM32U535NET6QTR 数据表(HTML) 26 Page - STMicroelectronics |
|
26 / 278 page ![]() Functional overview STM32U535xx 26/278 DS14217 Rev 1 3.5 Embedded SRAMs Five SRAMs are embedded in the STM32U535xx devices, each with specific features. SRAM1 and SRAM2 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. • 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, and SRAM4 can be programmed as secure or nonsecure 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 nonsecure with watermark, using the TZSC (TrustZone security controller) in the GTZC (global TrustZone controller). 3.5.2 SRAMs privilege protection The SRAM1, SRAM2, and 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 nonsecure state. • SAU: up to eight SAU configurable regions are available for security attribution. • IDAU: It provides a first memory partition as nonsecure or nonsecure callable attributes. It is then combined with the results from the SAU security attribution and the higher security state is selected. Based on IDAU security attribution, the flash memory, system SRAM and peripheral memory space is aliased twice for secure and nonsecure states. However, the external memory space is not aliased. |
|
链接网址 |
| ALLDATASHEET是否为您带来帮助? [ DONATE ] |
关于 Alldatasheet | 广告服务 | 联系我们 | 隐私政策 | 数据表链接 | 链接交换 | 制造商名单 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 |