STM32CubeG0 MCU Firmware Package

This application demonstrates a Type-C provider and USB Host implementation on STM32G0xx devices using STM32Cube firmware. It serves two primary functions:

1. USB HID Host: Uses the STM32G0xx USB DRD Host peripheral to interact with Human Interface Class (HID) devices like mice or keyboards. The MCU enumerates the device and extracts metadata (VID, PID, manufacturer, serial number, and product name) which is displayed via UART.
2. USB-PD Provider: Initializes Type-C port 1 in source mode with a single Power Data Object (PDO) at 5V.

The application is designed to run on STM32G0xx devices and has been validated on the STM32G0C1E-EV board.

The USBPD_Analyzer is a demonstration firmware for the STM32G071B-DISCO board that utilizes the UCPD IP for USB Power Delivery (USB-PD) communication and detection. The application operates in two distinct modes based on the physical state of the mechanical door:

1. Standalone Sink Mode: Emulates a Type C PD3 standalone sink. This mode is active when the mechanical door is closed.
2. Spy Mode: Spies on messages between two Type C devices. This mode is active when the mechanical door is opened. In this mode, traces of exchanges can be viewed using the STM32CubeMonitor tool.

The implementation is based on FreeRTOS and uses the LCD for information display and a Joystick for menu navigation.

This application demonstrates how to use timers via the CMSIS RTOS API on an STM32G0 device. It showcases the interaction between a periodic timer and a thread to control an LED (LED4) with different timing intervals.

Behavioral Logic:

1. Timer Phase: A periodic timer toggles LED4 every 200 ms for a 5-second cycle. During this time, the thread is suspended.
2. Thread Phase: After 5 seconds, the thread resumes, stops the timer, and toggles LED4 every 400 ms for a 5-second cycle.
3. Cycle: Once the thread cycle completes, it restarts the timer and suspends itself, repeating the process.

Target Hardware:

• Device: STM32G071RBTx
• Board: NUCLEO-G071RB (can be tailored to other supported boards).

This application demonstrates how to implement a USB Mass Storage Class (MSC) device using STM32G0xx hardware. It uses the USB device peripheral to communicate with a PC Host via Bulk Only Transfer (BOT) and SCSI transparent commands. In this specific implementation, a microSD card is used as the storage media, and the STM32 MCU is enumerated as a removable drive by the PC host.

Key technical details:

• USB Speed: Full Speed (FS).
• Clocking: The FS USB module requires an internal 48-MHz clock generated from an internal PLL.
• Initialization: The application uses HAL_Init() for peripheral reset and Flash/SysTick initialization, and SystemClock_Config() to configure the system clock (SYSCLK).

This example demonstrates I2C data buffer transmission and reception between one Master and two Slaves using different address sizes (10-bit and 7-bit). It utilizes the STM32G0xx I2C HAL and LL APIs (for performance) with interrupts (IT) enabled.

Key Features:

• Master-Slave Communication: One Master communicates with two Slaves.
• Mixed Addressing: Supports both 10-bit and 7-bit I2C addressing.
• Interrupt Driven: Uses interrupt-based HAL functions for non-blocking communication.
• Hardware Target: Designed for NUCLEO-G071RB (STM32G071RB), but adaptable to other STM32G0xx devices.

The STM32CubeG0 MCU Package provides a comprehensive software platform for the STM32G0 series, including:

• CMSIS modules: Core and device modules for the ARM core.
• HAL-LL drivers: Hardware Abstraction Layer (HAL) and Low-Layer (LL) drivers for maximized portability.
• BSP drivers: Board Support Package drivers for supported evaluation, demonstration, or Nucleo boards.
• Middleware libraries: RTOS, USB, FatFS, graphics, touch sensing, etc.
• Software projects: Applications, demonstrations, and basic examples located in Projects/<Board_Name>/ directories.

The Templates_LL project is a reference template designed to help developers build firmware applications using the STM32 Low-Layer (LL) API. It provides a foundational structure including clock configuration and hardware definitions, which can then be used as a base for porting specific LL examples to a target board.

What is included:

• LL Drivers: All LL drivers are included via main.h and source files. To use them in an IDE, ensure the USE_FULL_LL_DRIVER option is enabled.
• Hardware Definitions: LED and user button definitions are provided in main.h.
• Clock Configuration: The system clock setup is implemented in main.c via the SystemClock_Config() function.

What is NOT included:

• Functions to initialize or control the LED and user button.
• Functions to manage the Interrupt Request (IRQ) handler for the user button.

The STM32G0C1E-EV demonstration firmware provides application subsets for the STM32G0C1E-EV board (MB1581) depending on the connected daughter board. The firmware automatically identifies the connected board by measuring the voltage level at PB11 (ADC_IN15).

Supported Hardware Configurations

• USB-PD Sub-demo: Requires STM32G0C1E-EV (MB1581) + USB-PD daughter board (MB1352).
• Legacy Sub-demo: Requires STM32G0C1E-EV (MB1581) + Legacy daughter board (MB1351).

This application demonstrates how to use message queues using the CMSIS RTOS API on an STM32G0 device.

Application Logic

The example implements a Producer-Consumer pattern with two threads:

1. Producer Thread: Sends an incrementing number to a queue every 1 second.
2. Consumer Thread: A higher-priority thread that blocks on queue reads. As soon as the producer posts a message, the consumer unblocks, preempts the producer, and removes the item.

The queue is configured with a capacity of exactly one item.

Monitoring the Application

• LiveWatch Variables: To verify the logic, monitor ProducerValue and ConsumerValue. These variables should remain equal at all times.
• LED Status (NUCLEO-G031K8):
  • LED3 toggles: Occurs every 1 second when the producer posts a message.
  • LED3 stays ON: Indicates an error has occurred.