MCUXpresso_LPC55S69/boards/lpcxpresso55s69/demo_apps/puf_hashcrypt_crypto/cm33_core0
Yilin Sun 6e8d03ec0a Updated to SDK v2.15.000
Signed-off-by: Yilin Sun <imi415@imi.moe>
2024-04-12 21:21:49 +08:00
..
armgcc Updated to SDK v2.15.000 2024-04-12 21:21:49 +08:00
board.c Stock SDK v2.11.0 2022-04-08 22:42:47 +08:00
board.h Stock SDK v2.11.0 2022-04-08 22:42:47 +08:00
clock_config.c Stock SDK v2.11.0 2022-04-08 22:42:47 +08:00
clock_config.h Stock SDK v2.11.0 2022-04-08 22:42:47 +08:00
pin_mux.c Stock SDK v2.11.0 2022-04-08 22:42:47 +08:00
pin_mux.h Stock SDK v2.11.0 2022-04-08 22:42:47 +08:00
puf_hashcrypt_crypto.c Updated to SDK v2.15.000 2024-04-12 21:21:49 +08:00
puf_hashcrypt_crypto_v3_14.xml Updated to SDK v2.15.000 2024-04-12 21:21:49 +08:00
readme.md Updated to SDK v2.15.000 2024-04-12 21:21:49 +08:00

readme.md

Overview

This demo application demonstrates how to use PUF controller which provides a secure key storage and then sends secret key via dedicated HW bus directly to Hashcrypt, which uses this key to encrypt data.

Usual use of PUF controller consists of these steps:

  1. Enroll: The controller retrieves the Startup Data (SD) from the memory (SRAM), derives a digital fingerprint, generates the corresponding Activation Code (AC) and sends it to the storage system. Perform this step only once for each device. There is a control register that can block further enrollment. This control register is write only and is reset on a power-on reset.

  2. Start: The AC generated during the enroll operation and the SD are used to reconstruct the digital fingerprint. It is done after every power-up and reset.

  3. Generate Key: The controller generates an unique key and combines it with the digital fingerprint to output a key code. Each time a Generate Key operation is executed a new unique key is generated.

  4. Set Key: The digital fingerprint generated during the Enroll/Start operations and the key provided by the Client Design (CD) are used to generate a Key Code. This KC can be stored externally. Perform this operation only once for each key.

  5. Get Key: The digital fingerprint generated during the Start operation and the KC generated during a Set Key operation are used to retrieve a stored key. Perform this operation every time a key is needed.

SDK version

  • Version: 2.15.000

Toolchain supported

  • IAR embedded Workbench 9.40.1
  • MCUXpresso 11.8.0
  • Keil MDK 5.38.1
  • GCC ARM Embedded 12.2

Hardware requirements

  • Mini/micro USB cable
  • LPCXpresso55s69 board
  • Personal Computer

Board settings

No special settings are required.

Prepare the Demo

Note: MCUXpresso IDE project default debug console is semihost

  1. Connect a micro USB cable between the PC host and the CMSIS DAP USB port (P6) on the board
  2. Open a serial terminal with the following settings (See Appendix A in Getting started guide for description how to determine serial port number):
    • 115200 baud rate
    • 8 data bits
    • No parity
    • One stop bit
    • No flow control
  3. Download the program to the target board.
  4. Either press the reset button on your board or launch the debugger in your IDE to begin running the demo.

Running the demo

The log below shows the output of the PUF driver example in the terminal window (the key value will vary):

PUF and HACHCRYPT Peripheral Driver Example

PUF Enroll success
PUF Start success

User key:
72 65 68 72 6f 66 6e 6f 6d 6d 6f 63 6e 75 79 72
65 76 73 69 64 72 6f 77 73 73 61 70 73 69 68 54

User key successfully set for HW bus crypto module

User key successfully set on PUF index 1

Successfully reconstructed secret key to HW bus for crypto module

Successfully reconstructed user key:
72 65 68 72 6f 66 6e 6f 6d 6d 6f 63 6e 75 79 72
65 76 73 69 64 72 6f 77 73 73 61 70 73 69 68 54

Setting user key for HASHCRYPT encryption

Encryption success! Printing first 16 bytes:
51 cc 90 bf b5 98 3c cc b8 6f b3 6b 12 55 2d c3

Setting HW bus secret key for HASHCRYPT encryption

Encryption success! Printing first 16 bytes:
51 cc 90 bf b5 98 3c cc b8 6f b3 6b 12 55 2d c3

Success: encrypted outputs are correct


Example end.