/**
  @page CRYP_AES_CCM CRYP AES CCM example
  
  @verbatim
  ******************** (C) COPYRIGHT 2017 STMicroelectronics *******************
  * @file    CRYP/CRYP_AES_CCM/readme.txt 
  * @author  MCD Application Team
  * @brief   Description of the CRYP AES CCM encryption mode example.
  ******************************************************************************
  *
  * Redistribution and use in source and binary forms, with or without modification,
  * are permitted provided that the following conditions are met:
  *   1. Redistributions of source code must retain the above copyright notice,
  *      this list of conditions and the following disclaimer.
  *   2. Redistributions in binary form must reproduce the above copyright notice,
  *      this list of conditions and the following disclaimer in the documentation
  *      and/or other materials provided with the distribution.
  *   3. Neither the name of STMicroelectronics nor the names of its contributors
  *      may be used to endorse or promote products derived from this software
  *      without specific prior written permission.
  *
  * THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS"
  * AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
  * IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
  * DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT HOLDER OR CONTRIBUTORS BE LIABLE
  * FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
  * DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
  * SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER
  * CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY,
  * OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE
  * OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
  *
  ******************************************************************************
  @endverbatim

@par Example Description 

This example provides a short description of how to use the CRYPTO peripheral to
encrypt data using AES with Combined Cipher Machine (CCM).

The AES-CCM mode requires:
1. Plain text: which will be authenticated and encrypted. Its size must be a multiple
   of 16 bytes. So if the original plain text size is not a multiple of 16 bytes, 
   it must be padded.
2. Header (associated data): that will be authenticated but not encrypted.
   The header if formatted in HBuffer[]: the header size is concatenated with the
   original header.
3. Nonce: a value that is used only once within a specified context. Its size must
   be 7, 8, 9, 10, 11, 12 or 13.
4. Key: is the parameter which determines the cipher text. In this example the key
   size is 128 bits = 16 bytes but it can be tailored to 192 bits and 256 bits.

The AES-CCM provides:
1. Cipher text: which is the encryption result of Plain text. In this example, the
   cipher text is available in OutputText.
   Its size is the same as the plain text.
2. MAC: the Message Authentication Code which is used for both message authentication
   and message tampering detection. Its size is lower or equal to 16 bytes.

STM32 Eval board's LEDs can be used to monitor the encryption status:
 - LED1 is ON when encryption is right.
 - LED2 is ON when encryption is wrong.
    
@note Care must be taken when using HAL_Delay(), this function provides accurate delay (in milliseconds)
      based on variable incremented in SysTick ISR. This implies that if HAL_Delay() is called from
      a peripheral ISR process, then the SysTick interrupt must have higher priority (numerically lower)
      than the peripheral interrupt. Otherwise the caller ISR process will be blocked.
      To change the SysTick interrupt priority you have to use HAL_NVIC_SetPriority() function.
      
@note The application needs to ensure that the SysTick time base is always set to 1 millisecond
      to have correct HAL operation.

@note The connection of the LCD reset pin to a dedicated GPIO PK7 instead of the STM32F469 NRST pin may cause residual display on LCD with applications/examples that do not require display.
	  The LCD clear can be ensured by hardware through the board's power off/power on or by software calling the BSP_LCD_Reset() function.

@par Directory contents 

  - CRYP/CRYP_AES_CCM/Inc/stm32f4xx_hal_conf.h    HAL configuration file
  - CRYP/CRYP_AES_CCM/Inc/stm32f4xx_it.h          Interrupt handlers header file
  - CRYP/CRYP_AES_CCM/Inc/main.h                  Header for main.c module  
  - CRYP/CRYP_AES_CCM/Src/stm32f4xx_it.c          Interrupt handlers
  - CRYP/CRYP_AES_CCM/Src/main.c                  Main program
  - CRYP/CRYP_AES_CCM/Src/stm32f4xx_hal_msp.c     HAL MSP module
  - CRYP/CRYP_AES_CCM/Src/system_stm32f4xx.c      STM32F4xx system source file

@par Hardware and Software environment

  - This example runs on STM32F479xx devices.

  - This example has been tested and validated with STM32479I-EVAL RevC board and can be
    easily tailored to any other supported device and development board.
 
@par How to use it ? 

In order to make the program work, you must do the following:
 - Open your preferred toolchain 
 - Rebuild all files and load your image into target memory
 - Run the example


 * <h3><center>&copy; COPYRIGHT STMicroelectronics</center></h3>
 */
