mirror of
https://github.com/STMicroelectronics/STM32CubeF7.git
synced 2025-05-09 19:29:34 +08:00
121 lines
5.5 KiB
Plaintext
121 lines
5.5 KiB
Plaintext
/**
|
||
@page FMC_SRAM FMC PSRAM memory basic functionalities use example
|
||
|
||
@verbatim
|
||
******************************************************************************
|
||
* @file FMC/FMC_PSRAM/readme.txt
|
||
* @author MCD Application Team
|
||
* @brief Description of the FMC PSRAM example.
|
||
******************************************************************************
|
||
* @attention
|
||
*
|
||
* Copyright (c) 2018 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 PSRAM
|
||
memory.
|
||
|
||
The PSRAM is IS66WV51216EBLL-55BLI.
|
||
|
||
In this example, the code is executed from QSPI external memory while data are in internal SRAM memory.
|
||
|
||
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 200 MHz.
|
||
|
||
The goal of this example is to explain the different steps to configure the FMC
|
||
and make the PSRAM 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 PSRAM
|
||
memory, then read back and checked to verify its correctness.
|
||
|
||
If the data is read correctly from PSRAM, the LED6 is ON, otherwise the LED5 is ON.
|
||
In case of HAL initialization issue, LED5 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.
|
||
|
||
@par Keywords
|
||
|
||
Memory, FMC, PSRAM, Read, Write, Initialization, Access
|
||
|
||
@Note<74>If the user code size exceeds the DTCM-RAM size or starts from internal cacheable memories (SRAM1 and SRAM2),that is shared between several processors,
|
||
<20><><EFBFBD><EFBFBD><EFBFBD>then it is highly recommended to enable the CPU cache and maintain its coherence at application level.
|
||
<EFBFBD><EFBFBD><EFBFBD><EFBFBD><EFBFBD><EFBFBD>The address and the size of cacheable buffers (shared between CPU and other masters) must be properly updated to be aligned to cache line size (32 bytes).
|
||
|
||
@Note It is recommended to enable the cache and maintain its coherence, but depending on the use case
|
||
<EFBFBD><EFBFBD><EFBFBD><EFBFBD><EFBFBD> It is also possible to configure the MPU as "Write through", to guarantee the write access coherence.
|
||
<EFBFBD><EFBFBD><EFBFBD><EFBFBD><EFBFBD><EFBFBD>In that case, the MPU must be configured as Cacheable/Bufferable/Not Shareable.
|
||
<EFBFBD><EFBFBD><EFBFBD><EFBFBD><EFBFBD><EFBFBD>Even though the user must manage the cache coherence for read accesses.
|
||
<EFBFBD><EFBFBD><EFBFBD><EFBFBD><EFBFBD><EFBFBD>Please refer to the AN4838 <20>Managing memory protection unit (MPU) in STM32 MCUs<55>
|
||
<EFBFBD><EFBFBD><EFBFBD><EFBFBD><EFBFBD><EFBFBD>Please refer to the AN4839 <20>Level 1 cache on STM32F7 Series<65>
|
||
|
||
@par Directory contents
|
||
|
||
- FMC/FMC_PSRAM/Inc/stm32f7xx_hal_conf.h HAL Configuration file
|
||
- FMC/FMC_PSRAM/Inc/main.h Header for main.c module
|
||
- FMC/FMC_PSRAM/Inc/stm32f7xx_it.h Header for stm32f7xx_it.c
|
||
- FMC/FMC_PSRAM/Src/main.c Main program
|
||
- FMC/FMC_PSRAM/Src/stm32f7xx_hal_msp.c HAL MSP module
|
||
- FMC/FMC_PSRAM/Src/stm32f7xx_it.c Interrupt handlers
|
||
- FMC/FMC_PSRAM/Src/system_stm32f7xx.c STM32F7xx system clock configuration file
|
||
|
||
|
||
@par Hardware and Software environment
|
||
|
||
- This example runs on STM32F730xx devices.
|
||
|
||
- This example has been tested with STMicroelectronics STM32F7308-DISCO
|
||
boards 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:
|
||
|
||
1. Select required configuration in memory.h in Templates\ExtMem_Boot\Inc.
|
||
The default configuration is the right one:
|
||
- DATA_AREA set to USE_INTERNAL_SRAM
|
||
- CODE_AREA set to USE_QSPI
|
||
2. Program the internal Flash with the ExtMem_Boot (see below).
|
||
3. Program the external memory with this example "Examples\FMC\FMC_PSRAM" (see below).
|
||
4. Start debugging user example or reset for free running.
|
||
|
||
In order to load the ExtMem_Boot code :
|
||
- Open your preferred toolchain :
|
||
- Open the Project
|
||
- Rebuild all files
|
||
- Load project image
|
||
|
||
In order to load this FMC example to the external memory :
|
||
- Open your preferred toolchain
|
||
- Rebuild all files.
|
||
- Run & debug the program:
|
||
- Using EWARM or MDK-ARM : Load project image from the IDE: Project->Debug
|
||
- Using SW4STM32 :
|
||
- Open the STM32CubeProgrammer tool
|
||
- Select the QSPI external flash loader "N25Q128A_STM32F7308-DISCO"
|
||
- From Erasing & Programming menu, browse and open the output binary file relative to this example
|
||
- Load the file into the external QSPI flash using "Start Programming" at the address APPLICATION_ADDRESS (0x90000000)
|
||
|
||
|
||
*/
|