Crypto: AES CCM¶
The AES CCM sample shows how to perform authenticated encryption and decryption operations using the CCM algorithm and a 128-bit key. The sample uses additional data and a random nonce.
Overview¶
The sample follows these steps:
First, the sample performs initialization:
The Platform Security Architecture (PSA) API is initialized.
A random AES key is generated and imported into the PSA crypto keystore.
Then, it encrypts/decrypts a sample plaintext:
A random nonce is generated.
Authenticated encryption is performed.
Authenticated decryption is performed.
Afterwards, it performs cleanup:
The AES key is removed from the PSA crypto keystore.
Requirements¶
The sample supports the following development kits:
Hardware platforms |
PCA |
Board name |
Build target |
|---|---|---|---|
PCA10095 |
|
||
PCA10095 |
|
||
PCA10090 |
|
||
PCA10090 |
|
||
PCA10056 |
|
When built for nrf5340dk_nrf5340_cpuappns and nrf9160dk_nrf9160ns targets, the sample is configured to compile and run as a non-secure application. Therefore, it automatically includes TF-M that prepares the required peripherals to be available for the application.
Building and running¶
This sample can be found under samples/crypto/aes_ccm in the nRF Connect SDK folder structure.
See Building and programming a sample application for information about how to build and program the application.
Testing¶
After programming the sample to your development kit, test it by performing the following steps:
Connect to the kit with a terminal emulator (for example, PuTTY). See How to connect with PuTTY for the required settings.
Compile and program the application.
Observe the logs from the application using an RTT Viewer or a terminal emulator.
Note
By default, the sample is configured to use both RTT and UART for logging. If you are using RTT, skip the first step of the testing procedure.