STM32CubeF4

@verbatim
******************** (C) COPYRIGHT 2017 STMicroelectronics *******************
* @file DMA2D/DMA2D_RegToMemWithLCD/readme.txt
* @author MCD Application Team
* @brief Description of the DMA2D Register to Memory with LCD example.
******************************************************************************
* @attention
*
* Copyright (c) 2017 STMicroelectronics.
* All rights reserved.
*
* This software is licensed under terms that can be found in the LICENSE file
* in the root directory of this software component.
* If no LICENSE file comes with this software, it is provided AS-IS.
*
******************************************************************************
@endverbatim

@par Example Description

This example provides a description of how to configure DMA2D peripheral in
Register_to_Memory transfer mode and display the result on LCD.

At the beginning of the main program the HAL_Init() function is called to reset
all the peripherals, initialize the Flash interface and the systick.
Then the SystemClock_Config() function is used to configure the system
clock (SYSCLK) to run at 180 MHz.

The Register_to_Memory transfer mode is used to fill a user defined area by a
fixed color. In this example, a green 200x200 square is displayed on the LCD.

Output offset is the number of pixel to be skipped after each transferred line

how to calculate the size of the transferred data ?
=> selected color mode gives the number of bits per pixel and we have
(ARGB4444 => 16bits/pixel) the number of pixel per line and the number of line,
therefore :

data_size = (bits per pixel) X (pixel per line + output offset) X (number of line)

STM32 Eval boards LEDs can be used to monitor the transfer status:
- LED1 is ON when the transfer is complete.
- LED2 is ON when there is a transfer error.
- LED3 is ON when there is an error in transfer/Init process.

@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.

@par Keywords

Display, Graphic, DMA2D, LCD, ARGB4444, Blending, Register to memory, LTDC, Pixel

@par Directory contents

- DMA2D/DMA2D_RegToMemWithLCD/Inc/main.h Main configuration file
- DMA2D/DMA2D_RegToMemWithLCD/Inc/stm32f4xx_it.h Interrupt handlers header file
- DMA2D/DMA2D_RegToMemWithLCD/Inc/stm32f4xx_hal_conf.h HAL configuration file
- DMA2D/DMA2D_RegToMemWithLCD/Src/main.c Main program
- DMA2D/DMA2D_RegToMemWithLCD/Src/stm32f4xx_it.c Interrupt handlers
- DMA2D/DMA2D_RegToMemWithLCD/Src/stm32f4xx_hal_msp.c HAL MSP module
- DMA2D/DMA2D_RegToMemWithLCD/Src/system_stm32f4xx.c STM32F4xx system clock configuration file

@par Hardware and Software environment

- This example runs on STM32F469xx/STM32F479xx devices.

- This example has been tested with STMicroelectronics STM32469I-EVAL RevC
evaluation 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