STM32U545NET3QTR datasheet(70/283 Pages) STMICROELECTRONICS

70 / 283 page

Functional overview

STM32U545xx

70/283

DS14216 Rev 1

•

Additional chaining modes supported by AES only:

–

Counter (CTR) mode

–

Galois counter mode (GCM)

–

Galois message authentication code (GMAC) mode

–

Counter with CBC-MAC (CCM) mode

•

528 or 743 clock cycle latency in ECB encryption mode for SAES processing one

128-bit block of data with, respectively, 128-bit or 256-bit key

•

51 or 75 clock cycle latency in ECB encryption mode for AES processing one 128-bit

block of data with, respectively, 128-bit or 256-bit key

•

Integrated round key scheduler to compute the last round key for AES ECB/CBC

decryption

•

256-bit register for storing the cryptographic key (four 32-bit registers), with key

atomicity enforcement

•

128-bit registers for storing initialization vectors (four 32-bit registers)

•

One 32-bit input buffer and one 32-bit output buffer

•

Automatic data flow control with support of single-transfer direct memory access (DMA)

using two channels (one for incoming data, one for processed data)

•

Data swapping logic to support 1-, 8-, 16- or 32-bit data

•

Possibility for software to suspend a message if the SAES/AES needs to process

another message with a higher priority (suspend/resume operation)

•

SAES additional features:

–

Security context enforcement for keys

–

Hardware secret key encryption/ decryption (wrapped key mode) and sharing with

faster AES peripheral (Shared key mode)

–

Protection against differential power analysis (DPA) and related side-channel

attacks

–

Optional hardware loading of two hardware secret keys (BHK, DHUK) that can be

XORed together

On top of standard AES encryption and decryption with a key loaded by software, SAES

peripheral allows the following advanced use cases:

•

Allow or deny the sharing of a key between a secure and a nonsecure application,

enforced by hardware

•

Encrypt once a key using side-channel resistant AES, then share it to a faster AES

engine by decrypting it (Shared key mode)

•

On-chip encrypted storage using chip-unique secret DHUK

•

Transport key generation by encrypting the device public unique ID with the application

secret BHK

•

Binding of device secure storage keys, using the silicon unique secret key (DHUK)

XORed with the boot secret key (BHK). If BHK is lost, the whole device secure storage

is lost.

Note:

Encrypted storage or derived keys that are using DHUK or BHK, cannot be used anymore

when a security breach is detected.

STM32U545NET3QTR 数据表(PDF) 70 Page - STMicroelectronics

STM32U545NET3QTR 数据表(HTML) 70 Page - STMicroelectronics

Html Pages

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 ...More

数据表下载