/**
@page MSC_Standalone USB Device Mass Storage (MSC) application
@verbatim
******************** (C) COPYRIGHT 2017 STMicroelectronics *******************
* @file USB_Device/MSC_Standalone/readme.txt
* @author MCD Application Team
* @brief Description of the USB Device MSC application.
******************************************************************************
* @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 Application Description
This application shows how to use the USB device application based on the Mass Storage Class (MSC) on the STM32F4xx devices.
This is a typical application on how to use the STM32F4xx USB OTG Device peripheral to communicate with a PC
Host using the Bulk Only Transfer (BOT) and Small Computer System Interface (SCSI) transparent commands,
while the microSD card is used as storage media. The STM32 MCU is enumerated as a MSC device using the
native PC Host MSC driver to which the STM324x9I-EVAL board is connected.
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. The user is provided with the SystemClock_Config()
function to configure the system clock (SYSCLK) to run at 168 MHz. The Full Speed (FS) USB module uses
internally a 48-MHz clock, which is generated from an integrated PLL. In the High Speed (HS) mode the
USB clock (60 MHz) is driven by the ULPI.
It's worth noting that the system clock (SYSCLK) can be configured, depending on the used USB Core:
- SYSCLK is set to 168 MHz: for FS Core (FS or HS-IN-FS), because used embedded PHY
requires 48 MHz clock, achieved only when system clock
is set to 168 MHz.
- SYSCLK is set to 180 MHz: for only HS Core, since no embedded PHY is used.
When the application is started, the user has just to plug the USB cable into a PC host and the device
is automatically detected. A new removable drive appears in the system window and write/read/format
operations can be performed as with any other removable drive.
@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 the STM32Cube USB Device library, please refer to UM1734
"STM32Cube USB Device library".
@par USB Library Configuration
To select the appropriate USB Core to work with, user must add the following macro defines within the
compiler preprocessor (already done in the preconfigured projects provided with this application):
- "USE_USB_HS" when using USB High Speed (HS) Core
- "USE_USB_FS" when using USB Full Speed (FS) Core
- "USE_USB_HS" and "USE_USB_HS_IN_FS" when using USB High Speed (HS) Core in FS mode
@par Keywords
Connectivity, USB_Device, USB, MSC, Mass Storage, Full Speed, High Speed, BOT, SCSI, Removable drive, FatFs,
File system, Write, Read, Format
@par Directory contents
- USB_Device/MSC_Standalone/Src/main.c Main program
- USB_Device/MSC_Standalone/Src/system_stm32f4xx.c STM32F4xx system clock configuration file
- USB_Device/MSC_Standalone/Src/stm32f4xx_it.c Interrupt handlers
- USB_Device/MSC_Standalone/Src/usbd_conf.c General low level driver configuration
- USB_Device/MSC_Standalone/Src/usbd_desc.c USB device MSC descriptor
- USB_Device/MSC_Standalone/Src/ubsd_storage.c Media Interface Layer
- USB_Device/MSC_Standalone/Inc/main.h Main program header file
- USB_Device/MSC_Standalone/Inc/stm32f4xx_it.h Interrupt handlers header file
- USB_Device/MSC_Standalone/Inc/stm32f4xx_hal_conf.h HAL configuration file
- USB_Device/MSC_Standalone/Inc/usbd_conf.h USB device driver Configuration file
- USB_Device/MSC_Standalone/Inc/usbd_desc.h USB device MSC descriptor header file
- USB_Device/MSC_Standalone/Inc/ubsd_storage.h Media Interface Layer header file
@par Hardware and Software environment
- This application runs on STM32F429xx/STM32F439xx devices.
- This application has been tested with STMicroelectronics STM324x9I-EVAL RevB
evaluation boards and can be easily tailored to any other supported device
and development board.
- STM324x9I-EVAL RevB Set-up
- Connect a uSD Card to the MSD connector (CN17).
- Connect the STM324x9I-EVAL board to the PC through 'USB micro A-Male
to A-Male' cable to the connector:
- CN9 : to use USB High Speed (HS)
- CN14: to use USB Full Speed (FS) with embedded PHY(U7)
Please ensure that jumper JP16 is not fitted.
- CN15: to use USB HS-IN-FS.
Note that some FS signals are shared with the HS ULPI bus, so some PCB rework is needed.
For more details, refer to section 2.8 USB OTG2 HS & FS in UM1667
@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
- In the workspace toolbar select the project configuration:
- STM324x9I-EVAL_USBH-HS: to configure the project for STM32F4xx devices using USB OTG HS peripheral
- STM324x9I-EVAL_USBH-FS: to configure the project for STM32F4xx devices using USB OTG FS peripheral
- STM324x9I-EVAL_USBH-HS-IN-FS: to configure the project for STM32F4xx devices and use USB OTG HS
peripheral In FS (using embedded PHY).
- Run the application
*/
83778d5c95