947
SAM4CP [DATASHEET]
43051E–ATPL–08/14
Table 41-4
summarizes the different cases.
Notes: 1.
Depending on the mode, there are other ways of clearing the DATRDY flag. See
“AES Interrupt Status
Register” on page 961
.
Warning:
In PDC mode, reading the AES_ODATARx before the last data transfer may lead to unpredictable results.
41.4.5 Galois Counter Mode (GCM)
41.4.5.1 Description
GCM comprises the AES engine in CTR mode along with a universal hash function (GHASH engine) that is defined over
a binary Galois field to produce a message authentication tag (the AES CTR engine and the GHASH engine are depicted
in
Figure 41-5, ”GCM Block Diagram”
).
The GHASH engine processes data packets after the AES operation. GCM provides assurance of the confidentiality of
data through the AES Counter mode of operation for encryption. Authenticity of the confidential data is assured through
the GHASH engine. GCM can also provide assurance of data that is not encrypted. Refer to the
NIST Special Publication
800-38D Recommendation
for more complete information.
GCM can be used with or without the PDC master. Messages may be processed as a single complete packet of data or
they may be broken into multiple packets of data over time.
GCM processing is computed on 128-bit input data fields. There is no support for unaligned data. The AES key length
can be whatever length is supported by the AES module.
The recommended programming procedure when using PDC is described in
Section 41.4.5.3
.
Table 41-4.
Last Output Data Mode Behavior versus Start Modes
Sequence
Manual and Auto Modes
PDC Mode
AES_MR.LOD = 0
AES_MR.LOD = 1
AES_MR.LOD = 0
AES_MR.LOD = 1
DATRDY Flag Clearing
Condition
(1)
At least one
AES_ODATAR
must be read
At least one
AES_IDATAR
must
be written
Not used
Managed by the PDC
Encrypted/Decrypted
Data Result Location
In the
AES_ODATARx
In the
AES_ODATARx
At the address
specified in the
AES_RPR
In the
AES_ODATARx
End of
Encryption/Decryption
Notification
DATRDY
DATRDY
ENDRX (or RXBUFF)
ENDTX (or TXBUFE)
then DATRDY