STM32CubeF4

@verbatim
******************** (C) COPYRIGHT 2017 STMicroelectronics *******************
* @file FMC/FMC_SRAM/readme.txt
* @author MCD Application Team
* @brief Description of the FMC SRAM 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 describes how to configure the FMC controller to access the SRAM
memory.

The SRAM is IS61WV102416BLL-10MLI.

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 goal of this example is to explain the different steps to configure the FMC
and make the SRAM device ready for access, without using the MSP layer.

In this example, the SRAM device is configured and initialized explicitly
following all initialization sequence steps. After initializing the device, user
can perform read/write operations on it. A data buffer is written to the SRAM
memory, then read back and checked to verify its correctness.

The user can chose his own configuration by commenting/uncommenting the defines for
undesired/desired configurations , for example, to change the data memory access width,
uncomment the define for the configuration "SRAM_MEMORY_WIDTH" in "main.h".

If the data is read correctly from SRAM, the LED1 is ON, otherwise the LED3 is ON.
In case of HAL initialization issue, LED3 will be ON.

@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 need 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 boards power off/power on or by software calling the BSP_LCD_Reset() function.

@par Keywords

Memory, FMC, SRAM, Read, Write, Initialization, Access

@par Directory contents

- FMC/FMC_SRAM/Inc/stm32f4xx_hal_conf.h HAL Configuration file
- FMC/FMC_SRAM/Inc/main.h Header for main.c module
- FMC/FMC_SRAM/Inc/stm32f4xx_it.h Header for stm32f4xx_it.c
- FMC/FMC_SRAM/Src/main.c Main program
- FMC/FMC_SRAM/Src/stm32f4xx_hal_msp.c HAL MSP module
- FMC/FMC_SRAM/Src/stm32f4xx_it.c Interrupt handlers
- FMC/FMC_SRAM/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 and validated with STMicroelectronics STM32469I-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