mirror of
https://github.com/STMicroelectronics/STM32CubeF4.git
synced 2025-05-11 19:29:45 +08:00
119 lines
5.3 KiB
Plaintext
119 lines
5.3 KiB
Plaintext
/**
|
||
@page FatFs_uSD FatFs with uSD card drive application
|
||
|
||
@verbatim
|
||
******************** (C) COPYRIGHT 2017 STMicroelectronics *******************
|
||
* @file FatFs/FatFs_uSD/readme.txt
|
||
* @author MCD Application Team
|
||
* @brief Description of the FatFs with uSD card drive application
|
||
******************************************************************************
|
||
*
|
||
* Copyright (c) 2017 STMicroelectronics. All rights reserved.
|
||
*
|
||
* This software component is licensed by ST under Ultimate Liberty license
|
||
* SLA0044, the "License"; You may not use this file except in compliance with
|
||
* the License. You may obtain a copy of the License at:
|
||
* www.st.com/SLA0044
|
||
*
|
||
******************************************************************************
|
||
@endverbatim
|
||
|
||
@par Application Description
|
||
|
||
How to use STM32Cube firmware with FatFs middleware component as a generic FAT
|
||
file system module. This example develops an application exploiting FatFs
|
||
features with a microSD drive configuration.
|
||
|
||
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 SD module uses internally a 48-MHz clock
|
||
which is coming from PLL SAI. This frequency permit to reach 24 MHz clock
|
||
needed for SD operation and in line with microSD specification.
|
||
|
||
The application is based on writing and reading back a text file from a drive,
|
||
and it's performed using FatFs APIs to access the FAT volume as described
|
||
in the following steps:
|
||
|
||
- Link the uSD disk I/O driver;
|
||
- Register the file system object (mount) to the FatFs module for the uSD drive;
|
||
- Create a FAT file system (format) on the uSD drive;
|
||
- Create and Open new text file object with write access;
|
||
- Write data to the text file;
|
||
- Close the open text file;
|
||
- Open text file object with read access;
|
||
- Read back data from the text file;
|
||
- Check on read data from text file;
|
||
- Close the open text file;
|
||
- Unlink the uSD disk I/O driver.
|
||
|
||
Notice that the application manages possible errors that might occur during the
|
||
access to FAT volume, when using FatFs APIs. In addition, user can check if the
|
||
written text file is available on the uSD card.
|
||
|
||
It is possible to fine tune needed FatFs features by modifying defines values
|
||
in FatFs configuration file <20>ffconf.h<> available under the project includes
|
||
directory, in a way to fit the application requirements.
|
||
|
||
STM32 Eval board's LEDs can be used to monitor the application status:
|
||
- LED1 is ON when the application runs successfully.
|
||
- LED3 is ON when any error occurs.
|
||
|
||
|
||
@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.
|
||
|
||
For more details about FatFs implementation on STM32Cube, please refer to UM1721 "Developing Applications
|
||
on STM32Cube with FatFs".
|
||
|
||
|
||
@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 Keywords
|
||
|
||
FatFS, SD Card, File system, FAT Volume, Format, Mount, Read, Write,
|
||
|
||
@par Directory contents
|
||
|
||
- FatFs/FatFs_uSD/Inc/stm32f4xx_hal_conf.h HAL configuration file
|
||
- FatFs/FatFs_uSD/Inc/stm32f4xx_it.h Interrupt handlers header file
|
||
- FatFs/FatFs_uSD/Inc/main.h Main program header file
|
||
- FatFs/FatFs_uSD/Inc/sd_diskio.h FatFS sd diskio driver header file
|
||
- FatFs/FatFs_uSD/Inc/ffconf.h FAT file system module configuration file
|
||
- FatFs/FatFs_uSD/Src/stm32f4xx_it.c Interrupt handlers
|
||
- FatFs/FatFs_uSD/Src/main.c Main program
|
||
- FatFs/FatFs_uSD/Src/sd_diskio.c FatFS sd diskio driver implementation
|
||
- FatFs/FatFs_uSD/Src/system_stm32f4xx.c STM32F4xx system clock configuration file
|
||
|
||
|
||
@par Hardware and Software environment
|
||
|
||
- This application runs on STM32F469xx and STM32F479xx devices.
|
||
|
||
- This application has been tested with STMicroelectronics STM32469I-EVAL RevC
|
||
evaluation boards and can be easily tailored to any other supported device
|
||
and development board.
|
||
|
||
- STM32469I-EVAL Set-up
|
||
- Connect a uSD Card to the MSD connector (CN17).
|
||
|
||
@note When the uSD Card is used; the Camera module must be unplugged, this is due to
|
||
the shared pins between the two devices.
|
||
|
||
|
||
@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 application
|
||
|
||
* <h3><center>© COPYRIGHT STMicroelectronics</center></h3>
|
||
*/ |