STM32CubeF1 MCU Firmware Package

This example demonstrates how to use the STM32F105x/107x USB OTG Host peripheral to interact with USB Human Interface Devices (HID), specifically mice and keyboards, within an RTOS environment (FreeRTOS with CMSIS-OS).

Key Features

• Device Enumeration: Automatically detects connected HID devices and extracts VID, PID, manufacturer name, serial number, and product name.
• Mouse Support: Moving a mouse moves a pointer on the LCD; button presses highlight rectangles in blue.
• Keyboard Support: Tapped characters are displayed on the LCD.
• RTOS Integration: Uses a normal priority thread to execute the HID routine.
• User Interface: A menu allows users to start HID applications or re-enumerate the device using joystick buttons.

The MSC Standalone example demonstrates how to use the STM32F1xx USB Device peripheral to act as a Mass Storage Class (MSC) device. It communicates with a PC Host using Bulk Only Transfer (BOT) and SCSI transparent commands, using a microSD card as the storage media.

When running, the STM32 MCU is enumerated by the PC Host as a standard removable drive, allowing standard read, write, and format operations.

This example demonstrates how to use the STM32F105x/107x USB OTG Host peripheral to interact with USB Human Interface Devices (HID), specifically mice and keyboards.

When a device is connected, the STM32 MCU acts as a HID Host, performing enumeration and extracting device metadata such as:

• VID (Vendor ID)
• PID (Product ID)
• Manufacturer name
• Serial number
• Product name

This information is displayed on the LCD screen. The application provides a menu to switch between different HID modes (Mouse or Keyboard) or to re-enumerate the device.

This example demonstrates how an I2C Master device can receive a single data byte from an I2C Slave device using a single STM32F103RB-Nucleo board. Both the Master and Slave peripherals operate in Interrupt (IT) mode.

Key characteristics:

• Peripherals: Uses LL (Low-Layer) unitary service functions for optimized performance and size.
• Master Configuration: I2C1 is configured in Master mode (400kHz clock).
• Slave Configuration: I2C2 is configured in Slave mode (400kHz clock, 7-bit address enabled).
• Trigger: A user push-button (linked via EXTI) initiates the Master's Start condition.
• Feedback:
  • LED2 is ON: Data was successfully received.
  • LED2 blinks: An error occurred during communication.

This example demonstrates how to use the STM32F105x/107x USB OTG Device peripheral to emulate a Human Interface Device (HID), specifically a mouse. The STM32 MCU is enumerated by the PC host using native HID drivers. In the provided STM3210C-EVAL implementation, joystick buttons on the board are used to emulate mouse directions.

Key technical details:

• Clock Configuration: The system clock (SYSCLK) is configured to 72 MHz. The Full Speed (FS) USB module uses an internal 48-MHz clock generated from an integrated PLL.
• Remote Wakeup: The example supports remote wakeup (the ability of a USB device to wake a suspended bus). The 'Key' button on the board serves as the remote wakeup source.
• Target Hardware: Designed for STM32F107xx/STM32F105xx devices, specifically tested on STM3210C-EVAL RevC.

This application demonstrates how to use the USB Host Mass Storage Class (MSC) on STM32F105x/107x devices using an RTOS configuration. It utilizes the USB OTG Host peripheral to interact with a USB flash disk using Bulk Only Transfer (BOT) and SCSI commands, integrated with the FatFs middleware for file system operations.

Key features include:

• Device Enumeration: Automatically detects connected USB flash disks and extracts VID, PID, manufacturer name, serial number, and product name.
• File Operations: Ability to write small text files (< 1 KB) to the disk.
• Disk Explorer: Ability to explore and display the USB flash disk content on an LCD screen.
• RTOS Integration: Built around FreeRTOS and the CMSIS-OS wrapping layer.

The Custom HID Standalone example demonstrates how to use the STM32F1xx USB Device peripheral to implement a HID (Human Interface Device) compliant device. The STM32 MCU is enumerated by the PC host using native HID drivers.

In this specific implementation:

• The STM3210C-EVAL board is used as the target hardware.
• The system clock (SYSCLK) is configured to 72 MHz.
• The Full Speed (FS) USB module uses an internal 48-MHz clock generated from an integrated PLL.
• Data is transferred to the PC host via endpoint1 IN (e.g., ADC values from a potentiometer).
• Control commands (e.g., LED control) are received from the PC via SET_REPORT or SET_FEATURE requests.

The Templates_LL project is a reference template designed to help developers build firmware applications using the STM32 Low-Layer (LL) API.

What is provided:

• Inclusion of all LL drivers (via main.h and IDE configuration).
• Definitions for LEDs and user buttons (in main.h).
• System clock configuration (in main.c).

What is NOT provided:

• Initialization or control functions for LEDs and user buttons.
• Interrupt handler (IRQ) management for the user button.

Target Hardware:

• Designed for STM32F107xC devices.
• Tested with the STM3210C-EVAL RevC board.

This example demonstrates how to use the STM32F10x USB OTG Host peripheral to operate with a USB CDC (Communication Device Class) device. It supports dynamic serial configuration and two-way data transfer:

• Transmission: The Host selects a file from an SD card via a menu and sends its content to the USB Device. Data to be transmitted is stored in the CDC_TX_Buffer.
• Reception: Data entered via a Hyperterminal (in ASCII format) is transferred from the Device to the Host and displayed on the Host's LCD screen. Data is stored in the CDC_RX_Buffer.

Upon startup, the Host enumerates the connected device and extracts metadata including VID, PID, manufacturer name, serial number, and product name, which are displayed on the LCD.