Copyright 2017 STMicroelectronics
The STM32CubeF4 Firmware package comes with a rich set of examples running on STMicroelectronics boards, organized by board and provided with preconfigured projects for the main supported toolchains.
The examples are classified depending on the STM32Cube level they apply to, and are named as follows:
The examples are located under STM32Cube_FW_STM32CubeF4_VX.Y.Z\Projects\, and all of them have the same structure:
To run the example, you have to do the following:
The provided examples can be tailored to run on any compatible hardware; user simply need to update the BSP drivers for his board, if it has the same hardware functions (LED, LCD display, pushbuttons...etc.). The BSP is based on a modular architecture that allows it to be ported easily to any hardware by just implementing the low level routines.
The table below contains the list of examples provided within STM32CubeF4 Firmware package.
| Level | Module Name | Project Name | Description | STM324x9I_EVAL | STM32F401RE-Nucleo | STM32446E_EVAL | STM32F429ZI-Nucleo | STM32F429I-Discovery | STM32F412G-Discovery | STM32F413ZH-Nucleo | STM32469I_EVAL | STM32F412ZG-Nucleo | STM32F411E-Discovery | STM32F446ZE-Nucleo | STM32446E-Nucleo | STM32F411RE-Nucleo | STM32469I-Discovery | STM32F410xx-Nucleo | STM32F4-Discovery | STM32F401-Discovery | STM32F413H-Discovery | STM324xG_EVAL |
Templates |
- |
Starter project |
This directory provides a reference template project that can be used to build any firmware application for STM32F4xx devices using STM32CubeF4 HAL and running on STM32F4 boards from STMicroelectronics. | X | X | X | X | X | X | X | X | X | X | X | X | X | X | X | X | X | X | X |
| Total number of templates: 19 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | |||
Templates_LL |
- |
Starter project |
This projects provides a reference template through the LL API that can be used to build any firmware application. | X | X | X | X | X | X | X | X | X | X | X | X | X | X | X | X | X | X | X |
| Total number of templates_ll: 19 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | |||
Examples |
- |
BSP |
This example provides a description of how to use the different BSP drivers. | X | - | X | X | X | X | X | X | X | X | X | - | - | X | - | X | X | X | X |
ADC |
ADC_DualModeInterleaved |
How to use two ADC peripherals to perform conversions in dual interleaved mode. | X | - | X | - | - | - | - | X | - | - | - | - | - | - | - | - | - | - | X | |
ADC_InjectedConversion_Interrupt |
How to interrupt continuous ADC regular channel conversion using ADC injected channels, and how to get the result of this conversion. | X | - | X | - | - | - | - | X | - | - | - | - | - | - | - | - | - | - | X | ||
ADC_RegularConversion_DMA |
How to use the ADC1 and DMA to transfer continuously converted data from ADC1 to memory. | X | - | X | X | X | X | X | X | X | X | X | - | - | X | - | X | X | X | X | ||
ADC_RegularConversion_Interrupt |
How to use the ADC in interrupt mode to convert data through the HAL API. | X | - | X | X | - | X | X | X | X | - | X | - | - | - | - | - | - | X | X | ||
ADC_RegularConversion_Polling |
How to use the ADC in Polling mode to convert data through the HAL API. | X | - | X | - | - | - | X | X | - | - | - | - | - | - | - | - | - | - | X | ||
ADC_TriggerMode |
How to use ADC and TIM8 to continuously convert data from an ADC channel. | X | - | X | - | - | - | - | X | - | - | - | - | - | - | - | - | - | - | X | ||
ADC_TripleModeInterleaved |
How to use the ADC peripheral to convert a regular channel in Triple interleaved mode. | X | - | X | - | - | - | - | X | - | - | - | - | - | - | - | - | - | - | X | ||
CAN |
CAN_LoopBack |
How to set up a communication with the CAN in loopback mode. | X | - | - | - | - | - | - | - | - | - | - | - | - | - | - | - | - | - | X | |
CAN_Loopback |
How to set up a communication with the CAN in loopback mode. | - | - | X | - | - | - | - | X | - | - | - | - | - | - | - | - | - | - | - | ||
CAN_Networking |
How to configure the CAN peripheral to send and receive CAN frames in normal mode. | X | - | - | - | - | - | - | - | - | - | - | - | - | - | - | - | - | - | X | ||
CEC |
CEC_DataExchange |
How to configure and use the CEC peripheral to receive and transmit messages. | - | - | X | - | - | - | - | - | - | - | - | - | - | - | - | - | - | - | - | |
CEC_ListenMode |
How to configure and use the CEC peripheral to receive and transmit messages between two boards, while a third board (the spy device) listens but doesn't acknowledge the received messages. | - | - | X | - | - | - | - | - | - | - | - | - | - | - | - | - | - | - | - | ||
CEC_MultiAddress |
How to configure and use the CEC peripheral to receive and transmit messages in the case where one device supports two distinct logical addresses at the same time. | - | - | X | - | - | - | - | - | - | - | - | - | - | - | - | - | - | - | - | ||
CRC |
CRC_Example |
This example guides you through the different configuration steps by means of the HAL API. The CRC (Cyclic Redundancy Check) calculation unit computes the CRC code of a given buffer of 32-bit data words, using a fixed generator polynomial (0x4C11DB7). | X | - | X | X | - | X | X | X | X | - | X | - | - | - | - | - | - | X | X | |
CRYP |
CRYP_AESModes |
This example provides a short description of how to use the CRYPTO peripheral to encrypt and decrypt data using AES in chaining modes (ECB, CBC, CTR) and all key sizes (128, 192, 256) Algorithm. | X | - | - | - | - | - | - | X | - | - | - | - | - | - | - | - | - | - | X | |
CRYP_AES_CCM |
This example provides a short description of how to use the CRYPTO peripheral to encrypt data using AES with Combined Cipher Machine (CCM). | X | - | - | - | - | - | - | X | - | - | - | - | - | - | - | - | - | - | - | ||
CRYP_AES_DMA |
This example provides a short description of how to use the CRYPTO peripheral to encrypt and decrypt data using AES-128 Algorithm with ECB chaining mode. | X | - | - | - | - | - | - | X | - | - | - | - | - | - | - | - | - | - | X | ||
CRYP_AES_GCM |
This example provides a description of how to use the CRYPTO peripheral to encrypt and decrypt data using AES with Galois/Counter Mode (GCM). | X | - | - | - | - | - | - | X | - | - | - | - | - | - | - | - | - | - | - | ||
CRYP_DESTDESmodes |
This example provides a short description of how to use the CRYPTO peripheral to encrypt and decrypt data using DES and TDES in all modes (ECB, CBC) Algorithm. | X | - | - | - | - | - | - | X | - | - | - | - | - | - | - | - | - | - | X | ||
CRYP_TDES_DMA |
This example provides a short description of how to use the CRYPTO peripheral to encrypt data using TDES Algorithm. | X | - | - | - | - | - | - | X | - | - | - | - | - | - | - | - | - | - | X | ||
Cortex |
CORTEXM_MPU |
This example presents the MPU feature. Its purpose is to configure a memory area as privileged read-only area and attempt to perform read and write operations in different modes. | X | - | X | X | - | X | X | X | X | - | X | - | - | - | - | - | - | - | X | |
CORTEXM_ModePrivilege |
This example shows how to modify Thread mode privilege access and stack. Thread mode is entered on reset or when returning from an exception. | X | - | X | - | - | - | X | X | - | - | - | - | - | - | - | - | - | - | X | ||
CORTEXM_ProcessStack |
This example shows how to modify Thread mode stack. Thread mode is entered on Reset, and can be entered as a result of an exception return. | - | - | - | - | - | - | X | - | - | - | - | - | - | - | - | - | - | - | - | ||
CORTEXM_SysTick |
This example shows how to use the default configuration of SysTick with a time base equal to 1 ms in order to insert a delay between LEDs toggling. | X | - | X | X | - | X | X | X | X | - | X | - | - | - | - | - | - | X | X | ||
DAC |
DAC_SignalsGeneration |
This example provides a short description of how to use the DAC peripheral to generate several signals using DMA controller. | X | - | X | - | X | - | - | X | - | - | - | - | - | X | - | X | - | X | X | |
DAC_SimpleConversion |
This example provides a short description of how to use the DAC peripheral to do a simple conversion. | X | - | X | - | - | - | - | X | - | - | - | - | - | - | - | - | - | - | X | ||
DCMI |
DCMI_CaptureMode |
This example provides a short description of how to use the DCMI to interface with camera module and display in continuous mode the picture on LCD. | X | - | X | - | - | - | - | X | - | - | - | - | - | - | - | - | - | - | X | |
DCMI_SnapshotMode |
This example provides a short description of how to use the DCMI to interface with camera module and display in snapshot mode the picture on LCD. | X | - | X | - | - | - | - | X | - | - | - | - | - | - | - | - | - | - | X | ||
DFSDM |
DFSDM_AudioRecord |
This example shows how to use the DFSDM HAL API to perform stereo audio recording. | - | - | - | - | - | X | - | - | - | - | - | - | - | - | - | - | - | - | - | |
DFSDM_PulseSkipper |
This example shows how to use the DFSDM HAL API to perform stereo audio recording. | - | - | - | - | - | - | - | - | - | - | - | - | - | - | - | - | - | X | - | ||
DMA |
DMA_FIFOMode |
This example provides a description of how to use a DMA to transfer a word data buffer from Flash memory to embedded SRAM with FIFO mode enabled through the HAL API. | X | - | X | - | - | - | X | X | - | - | - | - | - | - | - | - | - | X | X | |
DMA_FLASHToRAM |
This example provides a description of how to use a DMA channel to transfer a word data buffer from Flash memory to embedded SRAM through the HAL API. | X | - | X | X | X | X | X | X | X | X | X | - | - | X | - | X | X | X | X | ||
DMA2D |
DMA2D_MemToMemWithBlending |
This example provides a description of how to configure DMA2D peripheral in Memory_to_Memory with blending transfer mode. | X | - | - | - | X | - | - | X | - | - | - | - | - | X | - | - | - | - | - | |
DMA2D_MemToMemWithLCD |
This example provides a description of how to configure DMA2D peripheral in Memory_to_Memory transfer mode and display the result on LCD. | X | - | - | - | - | - | - | X | - | - | - | - | - | - | - | - | - | - | - | ||
DMA2D_MemToMemWithPFC |
This example provides a description of how to configure DMA2D peripheral for transfer in Memory-to-memory with Pixel Format Conversion (PFC) Mode. | X | - | - | - | X | - | - | X | - | - | - | - | - | X | - | - | - | - | - | ||
DMA2D_MemoryToMemory |
This example provides a description of how to configure DMA2D peripheral in Memory_to_Memory transfer mode. | X | - | - | - | - | - | - | X | - | - | - | - | - | - | - | - | - | - | - | ||
DMA2D_RegToMemWithLCD |
This example provides a description of how to configure DMA2D peripheral in Register_to_Memory transfer mode and display the result on LCD. | X | - | - | - | - | - | - | X | - | - | - | - | - | - | - | - | - | - | - | ||
FLASH |
FLASH_DualBoot |
This example guides you through the different configuration steps to program the internal flash memory bank 1 and bank 2 and to swap between both of them by mean of the FLASH HAL API. | X | - | - | - | - | - | - | - | - | - | - | - | - | - | - | - | - | - | - | |
FLASH_EraseProgram |
This example describes how to configure and use the FLASH HAL API to erase and program the internal Flash memory. | X | - | X | X | X | - | X | X | X | X | X | - | - | X | - | X | X | - | X | ||
FLASH_WriteProtection |
This example describes how to configure and use the FLASH HAL API to enable and disable the write protection of the internal Flash memory. | X | - | X | - | - | X | - | X | - | - | - | - | - | - | - | - | - | X | X | ||
FMC |
FMC_NOR |
This example describes how to configure the FMC controller to access the NOR memory. | - | - | - | - | - | - | - | X | - | - | - | - | - | - | - | - | - | - | - | |
FMC_PSRAM |
This example describes how to configure the FMC controller to access the PSRAM memory. | - | - | - | - | - | - | - | - | - | - | - | - | - | - | - | - | - | X | - | ||
FMC_PSRAM_PreInitConfig |
This example describes how to execute a part of the code from the PSRAM external memory. | - | - | - | - | - | - | - | - | - | - | - | - | - | - | - | - | - | X | - | ||
FMC_SDRAM |
This example describes how to configure the FMC controller to access the SDRAM memory. | X | - | X | - | X | - | - | X | - | - | - | - | - | X | - | - | - | - | - | ||
FMC_SDRAM_DataMemory |
This example describes how to configure the FMC controller to access the SDRAM memory including heap and stack. | X | - | X | - | - | - | - | X | - | - | - | - | - | - | - | - | - | - | - | ||
FMC_SDRAM_LowPower |
This example describes how to configure the FMC controller to access the SDRAM memory in low power mode (SDRAM Self Refresh mode). | X | - | X | - | X | - | - | X | - | - | - | - | - | X | - | - | - | - | - | ||
FMC_SRAM |
This example describes how to configure the FMC controller to access the SRAM memory. | X | - | - | - | - | - | - | X | - | - | - | - | - | - | - | - | - | - | - | ||
FMC_SRAM_DataMemory |
This example guides you through the different configuration steps by mean of HAL API to configure the FMC controller to access the SRAM mounted on evaluation board (including heap and stack). | X | - | - | - | - | - | - | X | - | - | - | - | - | - | - | - | - | - | - | ||
FSMC |
FSMC_SRAM |
This example describes how to configure the FSMC controller to access the SRAM memory. | - | - | - | - | - | - | - | - | - | - | - | - | - | - | - | - | - | - | X | |
FSMC_SRAM_DataMemory |
This example describes how to configure the FSMC controller to access the SRAM memory including heap and stack. | - | - | - | - | - | - | - | - | - | - | - | - | - | - | - | - | - | - | X | ||
GPIO |
GPIO_EXTI |
How to configure external interrupt lines. | X | - | X | X | X | X | X | X | X | X | X | - | - | X | - | X | X | X | X | |
GPIO_IOToggle |
How to configure and use GPIOs through the HAL API. | X | X | X | X | - | X | X | X | X | - | X | X | X | - | X | - | - | X | X | ||
HAL |
HAL_TimeBase_RTC_ALARM |
This example describes how to customize the HAL time base using RTC Alarm instead of Systick as main source of time base. The nucleo board user button (connected to EXTI Line13) will be used to Suspend or Resume tick increment. | X | X | X | X | X | X | X | X | X | X | X | X | X | X | X | X | X | X | X | |
HAL_TimeBase_RTC_WKUP |
This example describes how to customize the HAL time base using RTC wakeup instead of Systick as main source of time base. The nucleo board user button (connected to EXTI Line13) will be used to Suspend or Resume tick increment. | X | X | X | X | X | X | X | X | X | X | X | X | X | X | X | X | X | X | X | ||
HAL_TimeBase_TIM |
This example describes how to customize the HAL time base using a general purpose timer(TIM6) instead of Systick as main source of time base. | X | X | X | X | X | X | X | X | X | X | X | X | X | X | X | X | X | X | X | ||
HASH |
HASH_HMAC_SHA1MD5 |
How to use the HASH peripheral to hash data with HMAC SHA-1 and HMAC MD5 algorithms. | X | - | - | - | - | - | - | X | - | - | - | - | - | - | - | - | - | - | X | |
HASH_SHA1MD5 |
How to use the HASH peripheral to hash data with SHA-1 and MD5 algorithms. | X | - | - | - | - | - | - | X | - | - | - | - | - | - | - | - | - | - | X | ||
HASH_SHA1MD5_DMA |
How to use the HASH peripheral to hash data using SHA-1 and MD5 algorithms when data are fed to the HASH unit with DMA. | X | - | - | - | - | - | - | X | - | - | - | - | - | - | - | - | - | - | X | ||
HASH_SHA224SHA256_DMA |
How to use the HASH peripheral to hash data with SHA224 and SHA256 algorithms. | X | - | - | - | - | - | - | X | - | - | - | - | - | - | - | - | - | - | - | ||
I2C |
FMPI2C_EEPROM |
How to handle I2C data buffer transmission/reception with DMA. In the example, the device communicates with an I2C EEPROM memory. | - | - | X | - | - | - | - | - | - | - | - | - | - | - | - | - | - | - | - | |
I2C_EEPROM |
How to handle I2C data buffer transmission/reception with DMA. In the example, the device communicates with an I2C EEPROM memory. | - | - | - | - | - | - | - | X | - | - | - | - | - | - | - | - | - | - | - | ||
I2C_TwoBoards_AdvComIT |
How to handle I2C data buffer transmission/reception between two boards, using an interrupt. | - | - | - | - | X | X | X | - | X | X | - | X | - | X | X | X | X | - | - | ||
I2C_TwoBoards_ComDMA |
How to handle I2C data buffer transmission/reception between two boards, via DMA. | - | - | - | - | X | X | X | - | X | X | - | X | - | X | X | X | X | - | - | ||
I2C_TwoBoards_ComIT |
How to handle I2C data buffer transmission/reception between two boards, using an interrupt. | - | - | - | - | X | X | X | - | X | X | - | X | - | X | X | X | X | - | - | ||
I2C_TwoBoards_ComPolling |
How to handle I2C data buffer transmission/reception between two boards, in polling mode. | - | - | - | - | X | X | X | - | X | X | - | X | - | X | X | X | X | - | - | ||
I2C_TwoBoards_RestartAdvComIT |
How to perform multiple I2C data buffer transmission/reception between two boards, in interrupt mode and with restart condition. | - | - | - | - | X | X | - | - | - | X | - | - | - | X | - | X | X | - | - | ||
I2C_TwoBoards_RestartComIT |
How to handle single I2C data buffer transmission/reception between two boards, in interrupt mode and with restart condition. | - | - | - | - | X | X | - | - | - | X | - | - | - | X | - | X | X | - | - | ||
I2S |
I2S_Audio |
Basic implementation of audio features. This example allows playing an audio file with an external codec on the STM32F412G-Discovery board through the I2S peripheral using DMA transfer. | - | - | - | - | - | X | - | - | - | - | - | - | - | - | - | - | - | - | X | |
IWDG |
IWDG_Example |
How to handle the IWDG reload counter and simulate a software fault that generates an MCU IWDG reset after a preset laps of time. | X | - | X | X | - | X | X | X | X | - | X | - | - | X | - | - | - | - | X | |
LCD_DSI |
LCD_DSI_CmdMode_DoubleBuffering |
This example provides a description of how to use the embedded LCD DSI controller (using IPs LTDC and DSI Host) to drive the KoD LCD mounted on board. | - | - | - | - | - | - | - | X | - | - | - | - | - | X | - | - | - | - | - | |
LCD_DSI_CmdMode_PartialRefresh |
This example provides a description of how to use the embedded LCD DSI controller (using IPs LTDC and DSI Host) to drive the KoD LCD mounted on board. | - | - | - | - | - | - | - | X | - | - | - | - | - | X | - | - | - | - | - | ||
LCD_DSI_CmdMode_SingleBuffer |
This example provides a description of how to use the embedded LCD DSI controller (using IPs LTDC and DSI Host) to drive the KoD LCD mounted on board. | - | - | - | - | - | - | - | X | - | - | - | - | - | X | - | - | - | - | - | ||
LCD_DSI_CmdMode_TearingEffect |
This example provides a description of how to use the embedded LCD DSI controller (using IPs LTDC and DSI Host) to drive the KoD LCD mounted on board. | - | - | - | - | - | - | - | X | - | - | - | - | - | X | - | - | - | - | - | ||
LCD_DSI_CmdMode_TearingEffect_ExtPin |
This example provides a description of how to use the embedded LCD DSI controller (using IPs LTDC and DSI Host) to drive the KoD LCD mounted on board. | - | - | - | - | - | - | - | X | - | - | - | - | - | X | - | - | - | - | - | ||
LCD_DSI_ULPM_Data |
This example provides a description of how to use the embedded LCD DSI controller (using IPs LTDC and DSI Host) to drive the KoD LCD mounted on board and manage entry and exit in DSI ULPM mode on data lane only. In this mode, the DSI PHY state machine is entering a low power state on data lane and allows to save some power when the LCD does not need to display. | - | - | - | - | - | - | - | X | - | - | - | - | - | X | - | - | - | - | - | ||
LCD_DSI_ULPM_DataClock |
This example provides a description of how to use the embedded LCD DSI controller (using IPs LTDC and DSI Host) to drive the KoD LCD mounted on board and manage entry and exit in DSI ULPM mode on data lane and clock lane. | - | - | - | - | - | - | - | X | - | - | - | - | - | X | - | - | - | - | - | ||
LCD_DSI_VideoMode_DoubleBuffering |
This example provides a description of how to use the embedded LCD DSI controller (using IPs LTDC and DSI Host) to drive the KoD LCD mounted on board. | - | - | - | - | - | - | - | X | - | - | - | - | - | X | - | - | - | - | - | ||
LCD_DSI_VideoMode_SingleBuffer |
This example provides a description of how to use the embedded LCD DSI controller (using IPs LTDC and DSI Host) to drive the KoD LCD mounted on board. | - | - | - | - | - | - | - | X | - | - | - | - | - | X | - | - | - | - | - | ||
LTDC |
LTDC_ColorKeying |
This example describe how to enable and use the color keying functionality. | X | - | - | - | - | - | - | - | - | - | - | - | - | - | - | - | - | - | - | |
LTDC_Display_1Layer |
This example provides a description of how to configure LTDC peripheral to display BMP image on LCD using only one layer. | X | - | - | - | - | - | - | - | - | - | - | - | - | - | - | - | - | - | - | ||
LTDC_Display_2Layers |
How to configure the LTDC peripheral to display two layers at the same time. | X | - | - | - | X | - | - | - | - | - | - | - | - | - | - | - | - | - | - | ||
PWR |
PWR_BOR |
This example shows how to configure the programmable BOR thresholds using the FLASH option bytes. | X | - | - | - | - | - | - | - | - | - | - | - | - | - | - | - | - | - | X | |
PWR_CurrentConsumption |
How to configure the system to measure the current consumption in different low-power modes. | X | X | - | X | X | X | X | - | X | X | X | X | X | X | X | X | X | - | X | ||
PWR_PVD |
How to configure the programmable voltage detector by using an external interrupt line. External DC supply must be used to supply Vdd. | X | - | - | - | - | - | - | - | - | - | - | - | - | - | - | - | - | - | X | ||
PWR_STANDBY |
How to enter the Standby mode and wake up from this mode by using an external reset or the WKUP pin. | X | - | X | - | - | X | X | X | X | - | - | - | - | X | - | - | - | - | X | ||
PWR_STOP |
How to enter the Stop mode and wake up from this mode by using the RTC wakeup timer event or an interrupt. | X | - | X | - | - | X | X | X | X | - | - | - | - | X | - | - | - | - | X | ||
QSPI |
QSPI_ExecuteInPlace |
How to execute code from QSPI memory after code loading. | - | - | X | - | - | X | - | X | - | - | - | - | - | X | - | - | - | - | - | |
QSPI_MemoryMapped |
How to use a QSPI memory in memory-mapped mode. | - | - | X | - | - | X | - | X | - | - | - | - | - | - | - | - | - | - | - | ||
QSPI_PreInitConfig |
How to configure the QSPI IP in order to have access to external memory just after reset. | - | - | X | - | - | X | - | X | - | - | - | - | - | X | - | - | - | - | - | ||
QSPI_ReadWrite_DMA |
How to use a QSPI memory in DMA mode. | - | - | X | - | - | X | - | X | - | - | - | - | - | - | - | - | - | X | - | ||
QSPI_ReadWrite_IT |
How to use a QSPI memory in interrupt mode. | - | - | X | - | - | X | - | X | - | - | - | - | - | - | - | - | - | X | - | ||
RCC |
RCC_ClockConfig |
This example describes how to use the RCC HAL API to configure the system clock (SYSCLK) and modify the clock settings in Run mode. | X | - | X | X | X | X | X | X | X | X | X | X | X | X | X | X | X | X | X | |
RNG |
RNG_MultiRNG |
Configuration of the RNG using the HAL API. This example uses the RNG to generate 32-bit long random numbers. | X | - | - | - | - | X | X | X | X | - | - | - | - | - | - | - | - | X | X | |
RTC |
RTC_Alarm |
This example guides you through the different configuration steps by means of the RTC HAL API to configure and generate an RTC alarm. | X | - | X | - | - | - | X | X | - | - | - | - | - | - | - | - | - | - | X | |
RTC_Calendar |
This example guides you through the different configuration steps by mean of HAL API to ensure Calendar configuration using the RTC peripheral. | X | - | X | X | - | X | X | X | X | - | X | X | X | - | X | - | - | X | X | ||
RTC_Tamper |
This example guides you through the different configuration steps by means of the RTC HAL API to write/read data to/from RTC Backup registers. It also demonstrates the tamper detection feature. | X | - | X | X | - | - | X | X | X | - | X | - | - | - | - | - | - | - | X | ||
RTC_TimeStamp |
This example guides you through the different configuration steps by means of the RTC HAL API to demonstrate the timestamp feature. | X | - | X | - | - | X | - | X | - | - | - | - | - | - | - | - | - | X | X | ||
SAI |
SAI_Audio |
Basic implementation of audio features using BSP_AUDIO. | X | - | X | - | - | - | - | - | - | - | - | - | - | - | - | - | - | - | - | |
SAI_AudioPlay |
Use of the SAI HAL API to play an audio file in DMA circular mode and handle the buffer update. | - | - | X | - | - | - | - | X | - | - | - | - | - | - | - | - | - | - | - | ||
SMARTCARD |
SMARTCARD_T0 |
This example describes a firmware Smartcard Interface based on the USART peripheral. The main purpose of this firmware example is to provide resources facilitating the development of an application using the USART peripheral in smartcard mode. | - | - | - | - | - | - | - | - | - | - | - | - | - | - | - | - | - | - | X | |
SPI |
SPI_FullDuplex_AdvComIT |
This example guides you through the different configuration steps by mean of HAL API to transmit/receive SPI data buffer using Interrupt, in an advanced communication mode : The master board always sends the command to the slave before any transmission is performed. | - | - | - | - | - | X | X | - | X | - | - | - | - | X | - | X | - | - | - | |
SPI_FullDuplex_AdvComPolling |
This example guides you through the different configuration steps by mean of HAL API to transmit/receive SPI data buffer in Polling mode and in an advanced communication mode: the master board always sends the command to the slave before any transmission is performed. | - | - | - | - | - | X | X | - | X | - | - | - | - | X | - | X | - | - | - | ||
SPI_FullDuplex_ComDMA |
This example shows how to perform SPI data buffer transmission/reception between two boards via DMA. | - | - | - | - | X | X | X | - | X | X | - | - | - | X | - | X | X | - | - | ||
SPI_FullDuplex_ComIT |
This example shows how to ensure SPI data buffer transmission/reception between two boards by using an interrupt. | - | - | - | - | X | X | X | - | X | X | - | - | - | X | - | X | X | - | - | ||
SPI_FullDuplex_ComPolling |
This example shows how to ensure SPI data buffer transmission/reception in Polling mode between two boards. | - | - | - | - | X | X | X | - | X | X | - | - | - | X | - | X | X | - | - | ||
SRAM |
SRAM_ExecuteInPlace |
This example describes how to execute a part of the code from the SRAM2 memory. To do this, a section is created where the function is stored. | - | - | - | - | - | - | X | - | - | - | - | - | - | - | - | - | - | - | - | |
TIM |
TIM_6Steps |
This example shows how to configure the TIM1 peripheral to generate 6 Steps. | X | - | X | - | - | - | - | X | - | - | - | - | - | - | - | - | - | - | X | |
TIM_7PWMOutput |
This example shows how to configure the TIM1 peripheral to generate 7 PWM signals with 4 different duty cycles (50%, 37.5%, 25% and 12.5%). | X | - | X | - | - | - | - | X | - | - | - | - | - | - | - | - | - | - | X | ||
TIM_CascadeSynchro |
This example shows how to synchronize TIM2 and Timers (TIM3 and TIM4) in cascade mode. | X | - | X | - | - | - | - | X | - | - | - | - | - | - | - | - | - | - | X | ||
TIM_ComplementarySignals |
This example shows how to configure the TIM1 peripheral to generate three complementary TIM1 signals, to insert a defined dead time value, to use the break feature and to lock the desired parameters. | X | - | X | - | - | - | - | X | - | - | - | - | - | - | - | - | - | - | X | ||
TIM_DMA |
This example provides a description of how to use DMA with TIMER Update request to transfer Data from memory to TIMER Capture Compare Register 3 (CCR3). | X | - | X | X | - | X | X | X | X | - | X | - | - | - | - | - | - | X | X | ||
TIM_DMABurst |
This example shows how to update the TIM1 channel1 period and the duty cycle using the TIM1 DMA burst feature. | X | - | X | - | - | - | - | X | - | - | - | - | - | - | - | - | - | - | X | ||
TIM_Encoder |
This example shows how to configure the TIM1 peripheral in encoder mode to determinate the rotation direction. | X | - | X | - | - | - | - | X | - | - | - | - | - | - | - | - | - | - | X | ||
TIM_ExtTriggerSynchro |
This example shows how to synchronize TIM peripherals in cascade mode with an external trigger. | X | - | X | - | - | - | - | X | - | - | - | - | - | - | - | - | - | - | X | ||
TIM_InputCapture |
This example shows how to use the TIM peripheral to measure the frequency of an external signal. | X | - | X | X | - | X | X | X | X | - | X | - | - | - | - | - | - | X | X | ||
TIM_OCActive |
This example shows how to configure the TIM peripheral to generate four different signals with four different delays. | X | - | X | X | - | X | X | X | X | - | X | - | - | - | - | - | - | X | X | ||
TIM_OCInactive |
This example shows how to configure the TIM peripheral in Output Compare Inactive mode with the corresponding Interrupt requests for each channel. | X | - | X | - | - | - | - | X | - | - | - | - | - | - | - | - | - | - | X | ||
TIM_OCToggle |
This example shows how to configure the TIM peripheral to generate four different signals with four different frequencies. | X | - | X | X | - | X | X | X | X | - | X | - | - | - | - | - | - | - | X | ||
TIM_OnePulse |
This example shows how to use the TIM peripheral to generate a single pulse when a rising edge of an external signal is received on the timer Input pin. | X | - | X | X | - | X | X | X | X | - | X | - | - | - | - | - | - | - | X | ||
TIM_PWMInput |
This example shows how to use the TIM peripheral to measure the frequency and duty cycle of an external signal. | X | X | X | X | X | X | X | X | X | X | X | X | X | X | X | X | X | - | X | ||
TIM_PWMOutput |
This example shows how to configure the TIM peripheral in PWM (Pulse Width Modulation) mode. | X | - | X | X | - | X | X | X | X | - | X | - | - | - | - | - | - | - | X | ||
TIM_ParallelSynchro |
This example shows how to synchronize TIM2 and Timers (TIM3 and TIM4) in parallel mode. | X | - | X | - | - | - | - | X | - | - | - | - | - | - | - | - | - | - | X | ||
TIM_PrescalerSelection |
This example shows how to configure the TIM peripheral in PWM (Pulse Width Modulation) mode with clock prescaler selection feature activated using __HAL_RCC_TIMCLKPRESCALER() which allows to double the output frequency. | - | - | X | - | - | - | - | X | - | - | - | - | - | - | - | - | - | - | - | ||
TIM_Prescaler_Selection |
This example shows how to configure the TIM peripheral in PWM (Pulse Width Modulation) mode with clock prescaler selection feature activated using __HAL_RCC_TIMCLKPRESCALER() which allow to double the output frequency. | X | - | - | - | - | - | - | - | - | - | - | - | - | - | - | - | - | - | - | ||
TIM_Synchronization |
This example shows how to synchronize TIM1 and Timers (TIM3 and TIM4) in parallel mode. | X | - | X | - | - | - | - | X | - | - | - | - | - | - | - | - | - | - | X | ||
TIM_TimeBase |
This example shows how to configure the TIM peripheral to generate a time base of one second with the corresponding Interrupt request. | X | - | X | - | X | - | - | X | - | X | - | - | - | X | - | X | X | - | X | ||
UART |
UART_HyperTerminal_DMA |
This example describes an UART transmission (transmit/receive) in DMA mode between a board and an HyperTerminal PC application. | - | - | X | - | - | - | - | X | - | - | - | - | - | - | - | - | - | - | - | |
UART_HyperTerminal_IT |
This example describes an UART transmission (transmit/receive) between a board and an Hyperterminal PC application by using an interrupt. | - | - | X | - | - | - | - | X | - | - | - | - | - | - | - | - | - | - | - | ||
UART_Hyperterminal_DMA |
This example describes an UART transmission (transmit/receive) in DMA mode between a board and an Hyperterminal PC application. | X | - | - | - | - | - | - | - | - | - | - | - | - | - | - | - | - | - | X | ||
UART_Hyperterminal_IT |
This example describes an UART transmission (transmit/receive) between a board and an Hyperterminal PC application by using an interrupt. | X | - | - | - | - | - | - | - | - | - | - | - | - | - | - | - | - | - | X | ||
UART_Printf |
This example shows how to re-route the C library printf function to the UART. | X | X | X | X | - | X | X | X | X | - | X | X | X | - | X | - | - | X | X | ||
UART_TwoBoards_ComDMA |
This example describes an UART transmission (transmit/receive) in DMA mode between two boards. | - | - | - | - | X | X | X | - | X | X | - | - | - | X | X | X | X | - | - | ||
UART_TwoBoards_ComIT |
This example describes an UART transmission (transmit/receive) in interrupt mode between two boards. | - | - | - | - | X | X | X | - | X | X | - | - | - | X | X | X | X | - | - | ||
UART_TwoBoards_ComPolling |
This example describes an UART transmission (transmit/receive) in polling mode between two boards. | - | - | - | - | X | X | X | - | X | X | - | - | - | X | X | X | X | - | - | ||
WWDG |
WWDG_Example |
This example guides you through the different configuration steps by means of the HAL API to perform periodic WWDG counter update and simulate a software fault that generates an MCU WWDG reset when a predefined time period has elapsed. | X | - | X | X | - | X | X | X | X | - | X | - | - | X | - | - | - | - | X | |
| Total number of examples: 743 | 87 | 7 | 71 | 27 | 30 | 51 | 48 | 95 | 42 | 24 | 27 | 13 | 9 | 46 | 16 | 27 | 24 | 27 | 72 | |||
Examples_LL |
ADC |
ADC_AnalogWatchdog |
This example describes how to use a ADC peripheral with ADC analog watchdog to monitor a channel and detect when the corresponding conversion data is out of window thresholds; This example is based on the STM32F4xx ADC LL API; peripheral initialization done using LL unitary services functions for optimization purpose (performance and size). | - | - | - | - | - | - | - | - | - | - | - | - | X | - | - | - | - | - | - |
ADC_ContinuousConversion_TriggerSW |
This example describes how to use a ADC peripheral to perform continuous ADC conversions of a channel, from a SW start; This example is based on the STM32F4xx ADC LL API; peripheral initialization done using LL unitary services functions for optimization purpose (performance and size). | - | - | - | - | - | - | - | - | - | - | - | - | X | - | - | - | - | - | - | ||
ADC_ContinuousConversion_TriggerSW_Init |
This example describes how to use a ADC peripheral to perform continuous ADC conversions of a channel, from a SW start; This example is based on the STM32F4xx ADC LL API; peripheral initialization done using LL unitary services functions for optimization purpose (performance and size). | - | - | - | - | - | - | - | - | - | - | - | - | X | - | - | - | - | - | - | ||
ADC_GroupsRegularInjected |
This example describes how to use a ADC peripheral with both ADC groups (ADC group regular and ADC group injected) in their intended use case; This example is based on the STM32F4xx ADC LL API; peripheral initialization done using LL unitary services functions for optimization purpose (performance and size). | - | - | - | - | - | - | - | - | - | - | - | - | X | - | - | - | - | - | - | ||
ADC_MultiChannelSingleConversion |
This example describes how to use a ADC peripheral to convert several channels, ADC conversions are performed successively in a scan sequence; This example is based on the STM32F4xx ADC LL API; peripheral initialization done using LL unitary services functions for optimization purpose (performance and size). | - | - | - | - | - | - | - | - | - | - | - | - | X | - | - | - | - | - | - | ||
ADC_SingleConversion_TriggerSW |
This example describes how to use a ADC peripheral to perform a single ADC conversion of a channel, at each software start; Example using programming model: polling (for programming models interrupt or DMA transfer, refer to other examples); This example is based on the STM32F4xx ADC LL API; peripheral initialization done using LL unitary services functions for optimization purpose (performance and size). | - | - | - | - | - | - | - | - | - | - | - | - | X | - | - | - | - | - | - | ||
ADC_SingleConversion_TriggerSW_DMA |
This example describes how to use a ADC peripheral to perform a single ADC conversion of a channel, at each software start; Example using programming model: DMA transfer (for programming models polling or interrupt, refer to other examples); This example is based on the STM32F4xx ADC LL API; peripheral initialization done using LL unitary services functions for optimization purpose (performance and size). | - | - | - | - | - | - | - | - | - | - | - | - | X | - | - | - | - | - | - | ||
ADC_SingleConversion_TriggerSW_IT |
This example describes how to use a ADC peripheral to perform a single ADC conversion of a channel, at each software start; Example using programming model: interrupt (for programming models polling or DMA transfer, refer to other examples); This example is based on the STM32F4xx ADC LL API; peripheral initialization done using LL unitary services functions for optimization purpose (performance and size). | - | - | - | - | - | - | - | - | - | - | - | - | X | - | - | - | - | - | - | ||
ADC_SingleConversion_TriggerTimer_DMA |
This example describes how to use a ADC peripheral to perform a single ADC conversion of a channel, at each trigger event from timer; Conversion data are transferred by DMA into a table, indefinitely (circular mode); This example is based on the STM32F4xx ADC LL API; peripheral initialization done using LL unitary services functions for optimization purpose (performance and size). | - | - | - | - | - | - | - | - | - | - | - | - | X | - | - | - | - | - | - | ||
ADC_TemperatureSensor |
This example describes how to use a ADC peripheral to perform a single ADC conversion of the internal temperature sensor and to calculate the temperature in Celsius degrees; Example using programming model: polling (for programming models interrupt or DMA transfer, refer to other examples); This example is based on the STM32F4xx ADC LL API; peripheral initialization done using LL unitary services functions for optimization purpose (performance and size). | - | - | - | - | - | - | - | - | - | - | - | - | X | - | - | - | - | - | - | ||
CORTEX |
CORTEX_MPU |
This example presents the MPU feature. Its purpose is to configure a memory area as privileged read-only area and attempt to perform read and write operations in different modes. | - | - | - | X | - | - | - | - | - | - | - | - | - | - | - | - | - | - | - | |
CRC |
CRC_CalculateAndCheck |
This example shows how to configure CRC calculation unit to get a CRC code of a given data buffer, based on a fixed generator polynomial (default value 0x4C11DB7). Peripheral initialization done using LL unitary services functions for optimization purpose (performance and size). | - | - | - | - | - | - | - | - | - | - | - | - | X | - | - | - | - | - | - | |
DAC |
DAC_GenerateConstantSignal_TriggerSW |
This example describes how to use the DAC peripheral to generate a constant voltage signal; This example is based on the STM32F4xx DAC LL API; peripheral initialization done using LL unitary services functions for optimization purpose (performance and size). | - | - | - | X | - | - | - | - | - | - | - | - | - | - | - | - | - | - | - | |
DAC_GenerateWaveform_TriggerHW |
This example describes how to use the DAC peripheral to generate a waveform voltage from digital data stream transfered by DMA; This example is based on the STM32F4xx DAC LL API; peripheral initialization done using LL unitary services functions for optimization purpose (performance and size). | - | - | - | X | - | - | - | - | - | - | - | - | - | - | - | - | - | - | - | ||
DAC_GenerateWaveform_TriggerHW_Init |
This example describes how to use the DAC peripheral to generate a waveform voltage from digital data stream transfered by DMA; This example is based on the STM32F4xx DAC LL API; peripheral initialization done using LL initialization function to demonstrate LL init usage. | - | - | - | X | - | - | - | - | - | - | - | - | - | - | - | - | - | - | - | ||
DMA |
DMA_CopyFromFlashToMemory |
This example describes how to use a DMA to transfer a word data buffer from Flash memory to embedded SRAM. Peripheral initialization done using LL unitary services functions for optimization purpose (performance and size). | - | - | - | - | - | - | - | - | - | - | - | - | X | - | - | - | - | - | - | |
DMA_CopyFromFlashToMemory_Init |
This example describes how to use a DMA to transfer a word data buffer from Flash memory to embedded SRAM. Peripheral initialization done using LL initialization function to demonstrate LL init usage. | - | - | - | - | - | - | - | - | - | - | - | - | X | - | - | - | - | - | - | ||
DMA2D |
DMA2D_MemoryToMemory |
This example describes how to configure the DMA2D peripheral in Memory-to-Memory transfer mode. The example is based on the STM32F4xx DMA2D LL API. Peripheral initialization is done using LL unitary services functions for optimization purpose (performance and size). | - | - | - | X | - | - | - | - | - | - | - | - | - | - | - | - | - | - | - | |
EXTI |
EXTI_ToggleLedOnIT |
This example describes how to configure the EXTI and use GPIOs to toggle the user LEDs available on the board when a user button is pressed. It is based on the STM32F4xx LL API. Peripheral initialization is done using LL unitary services functions for optimization purpose (performance and size). | - | - | - | - | - | - | - | - | - | - | - | - | X | - | - | - | - | - | - | |
EXTI_ToggleLedOnIT_Init |
This example describes how to configure the EXTI and use GPIOs to toggle the user LEDs available on the board when a user button is pressed. This example is based on the STM32F4xx LL API. Peripheral initialization is done using LL initialization function to demonstrate LL init usage. | - | - | - | - | - | - | - | - | - | - | - | - | X | - | - | - | - | - | - | ||
GPIO |
GPIO_InfiniteLedToggling |
This example describes how to configure and use GPIOs to toggle every 250 ms the user LEDs available on the board. This example is based on the STM32F4xx LL API. Peripheral initialization is done using LL unitary services functions for optimization purpose (performance and size). | - | - | - | - | - | - | - | - | - | - | - | - | X | - | - | - | - | - | - | |
GPIO_InfiniteLedToggling_Init |
This example describes how to configure and use GPIOs to toggle every 250 ms the user LEDs available on the board. This example is based on the STM32F4xx LL API. Peripheral initialization is done using LL initialization function to demonstrate LL init usage. | - | - | - | - | - | - | - | - | - | - | - | - | X | - | - | - | - | - | - | ||
I2C |
I2C_OneBoard_AdvCommunication_DMAAndIT |
This example describes how to exchange data between an I2C Master device in DMA mode and an I2C Slave device in Interrupt mode. Peripheral initialization is done using LL unitary services functions for optimization purpose (performance and size). | - | - | - | - | - | - | - | - | - | - | - | - | X | - | - | - | - | - | - | |
I2C_OneBoard_Communication_DMAAndIT |
This example describes how to transmit data bytes from an I2C Master device using DMA mode to an I2C Slave device using Interrupt mode. Peripheral initialization is done using LL unitary services functions for optimization purpose (performance and size). | - | - | - | - | - | - | - | - | - | - | - | - | X | - | - | - | - | - | - | ||
I2C_OneBoard_Communication_IT |
This example describes how to receive one data byte from an I2C Slave device to an I2C Master device. Both devices operate in Interrupt mode. Peripheral initialization is done using LL unitary services functions for optimization purpose (performance and size). | - | - | - | - | - | - | - | - | - | - | - | - | X | - | - | - | - | - | - | ||
I2C_OneBoard_Communication_IT_Init |
This example describes how to receive one data byte from an I2C Slave device to an I2C Master device. Both devices operate in Interrupt mode. Peripheral initialization is done using LL initialization function to demonstrate LL init usage. | - | - | - | - | - | - | - | - | - | - | - | - | X | - | - | - | - | - | - | ||
I2C_OneBoard_Communication_PollingAndIT |
This example describes how to transmit data bytes from an I2C Master device using Polling mode to an I2C Slave device using Interrupt mode. Peripheral initialization is done using LL unitary services functions for optimization purpose (performance and size). | - | - | - | - | - | - | - | - | - | - | - | - | X | - | - | - | - | - | - | ||
I2C_TwoBoards_MasterRx_SlaveTx_IT |
This example describes how to receive one data byte from an I2C Slave device to an I2C Master device. Both devices operate in Interrupt mode. Peripheral initialization is done using LL unitary services functions for optimization purpose (performance and size). | - | - | - | - | - | - | - | - | - | - | - | - | X | - | - | - | - | - | - | ||
I2C_TwoBoards_MasterTx_SlaveRx |
This example describes how to transmit data bytes from an I2C Master device using Polling mode to an I2C Slave device using Interrupt mode. Peripheral initialization is done using LL unitary services functions for optimization purpose (performance and size). | - | - | - | - | - | - | - | - | - | - | - | - | X | - | - | - | - | - | - | ||
I2C_TwoBoards_MasterTx_SlaveRx_DMA |
This example describes how to transmit data bytes from an I2C Master device using DMA mode to an I2C Slave device using DMA mode. Peripheral initialization is done using LL unitary services functions for optimization purpose (performance and size). | - | - | - | - | - | - | - | - | - | - | - | - | X | - | - | - | - | - | - | ||
IWDG |
IWDG_RefreshUntilUserEvent |
This example describes how to configure the IWDG to ensure period counter update and generate an MCU IWDG reset when a user button is pressed. Peripheral initialization is done using LL unitary services functions for optimization purpose (performance and size). | - | - | - | - | - | - | - | - | - | - | - | - | X | - | - | - | - | - | - | |
LPTIM |
LPTIM_PulseCounter |
This example describes how to use the LPTIM in counter mode to generate a PWM output signal and update PWM duty cycle. This example is based on the STM32F4xx LPTIM LL API; peripheral initialization is done using LL unitary services functions for optimization purpose (performance and size). | - | - | - | - | - | - | - | - | - | - | - | - | - | - | X | - | - | - | - | |
LPTIM_PulseCounter_Init |
This example describes how to use the LPTIM in counter mode to generate a PWM output signal and update PWM duty cycle. This example is based on the STM32F4xx LPTIM LL API; peripheral initialization is done using LL initialization function to demonstrate LL init usage. | - | - | - | - | - | - | - | - | - | - | - | - | - | - | X | - | - | - | - | ||
PWR |
PWR_EnterStandbyMode |
This example shows how to enter the system in STANDBY mode and wake-up from this mode using external RESET or wake-up interrupt. | - | - | - | - | - | - | - | - | - | - | - | - | X | - | - | - | - | - | - | |
PWR_EnterStopMode |
This example shows how to enter the system in STOP_MAINREGU mode. | - | - | - | - | - | - | - | - | - | - | - | - | X | - | - | - | - | - | - | ||
RCC |
RCC_OutputSystemClockOnMCO |
This example describes how to configure MCO pins (PA8 and PC9) to output the system clock. | - | - | - | - | - | - | - | - | - | - | - | - | X | - | - | - | - | - | - | |
RCC_UseHSEasSystemClock |
This example describes how to use the RCC LL API how to start the HSE and use it as system clock. | - | - | - | - | - | - | - | - | - | - | - | - | X | - | - | - | - | - | - | ||
RCC_UseHSI_PLLasSystemClock |
This example shows how to modify the PLL parameters in run time. | - | - | - | - | - | - | - | - | - | - | - | - | X | - | - | - | - | - | - | ||
RNG |
RNG_GenerateRandomNumbers |
This example shows how to configure RNG peripheral to allow generation of 32-bit long Random Numbers. Peripheral initialization done using LL unitary services functions for optimization purpose (performance and size). | - | - | - | X | - | - | - | - | - | - | - | - | - | - | - | - | - | - | - | |
RNG_GenerateRandomNumbers_IT |
This example shows how to configure RNG peripheral to allow generation of 32-bit long Random Numbers, using interrupts. Peripheral initialization done using LL unitary services functions for optimization purpose (performance and size). | - | - | - | X | - | - | - | - | - | - | - | - | - | - | - | - | - | - | - | ||
RTC |
RTC_Alarm |
This example guides you through the different configuration steps by mean of LL API to ensure Alarm configuration and generation using the RTC peripheral. Peripheral initialization done using LL unitary services functions for optimization purpose (performance and size). | - | - | - | - | - | - | - | - | - | - | - | - | X | - | - | - | - | - | - | |
RTC_Alarm_Init |
This example guides you through the different configuration steps by mean of LL API to ensure Alarm configuration and generation using the RTC peripheral. Peripheral initialization done using LL initialization function to demonstrate LL init usage. | - | - | - | - | - | - | - | - | - | - | - | - | X | - | - | - | - | - | - | ||
RTC_Calendar |
This example guides you through the different configuration steps by mean of HAL API to configure the RTC calendar. Peripheral initialization done using LL unitary services functions for optimization purpose (performance and size). | - | - | - | - | - | - | - | - | - | - | - | - | X | - | - | - | - | - | - | ||
RTC_ExitStandbyWithWakeUpTimer |
This example shows how to configure the RTC in order to wake up from Standby mode using RTC Wakeup Timer. Peripheral initialization is done using LL unitary services functions for optimization purpose (performance and size). | - | - | - | - | - | - | - | - | - | - | - | - | X | - | - | - | - | - | - | ||
RTC_Tamper |
This example guides you through the different configuration steps by mean of LL API to ensure Tamper configuration using the RTC peripheral. Peripheral initialization done using LL unitary services functions for optimization purpose (performance and size). | - | - | - | - | - | - | - | - | - | - | - | - | X | - | - | - | - | - | - | ||
RTC_TimeStamp |
This example guides you through the different configuration steps by mean of LL API to ensure Time Stamp configuration using the RTC peripheral. Peripheral initialization done using LL unitary services functions for optimization purpose (performance and size). | - | - | - | - | - | - | - | - | - | - | - | - | X | - | - | - | - | - | - | ||
SPI |
SPI_OneBoard_HalfDuplex_DMA |
This example shows how to configure GPIO and SPI peripherals to transmit bytes from an SPI Master device to an SPI Slave device in DMA mode. The example is based on the STM32F4xx SPI LL API. Peripheral initialization is done using LL unitary services functions for optimization purpose (performance and size). | - | - | - | - | - | - | - | - | - | - | - | - | X | - | - | - | - | - | - | |
SPI_OneBoard_HalfDuplex_DMA_Init |
This example shows how to configure GPIO and SPI peripherals to transmit bytes from an SPI Master device to an SPI Slave device in DMA mode. The example is based on the STM32F4xx SPI LL API. Peripheral initialization is done using LL initialization function to demonstrate LL init usage. | - | - | - | - | - | - | - | - | - | - | - | - | X | - | - | - | - | - | - | ||
SPI_OneBoard_HalfDuplex_IT |
This example shows how to configure GPIO and SPI peripherals to transmit bytes from an SPI Master device to an SPI Slave device in Interrupt mode. The example is based on the STM32F4xx SPI LL API. Peripheral initialization is done using LL unitary services functions for optimization purpose (performance and size). | - | - | - | - | - | - | - | - | - | - | - | - | X | - | - | - | - | - | - | ||
SPI_TwoBoards_FullDuplex_DMA |
This example shows how to ensure SPI data buffer transmission and reception in DMA mode. The example is based on the STM32F4xx SPI LL API. Peripheral initialization is done using LL unitary services functions for optimization purpose (performance and size). | - | - | - | - | - | - | - | - | - | - | - | - | X | - | - | - | - | - | - | ||
SPI_TwoBoards_FullDuplex_IT |
This example shows how to ensure SPI Data buffer transmission and reception in Interrupt mode. The example is based on the STM32F4xx SPI LL API. Peripheral initialization is done using LL unitary services functions for optimization purpose (performance and size). | - | - | - | - | - | - | - | - | - | - | - | - | X | - | - | - | - | - | - | ||
TIM |
TIM_BreakAndDeadtime |
This example shows how to configure the TIMER to perform the following: â€“ generate three center-aligned PWM and complementary PWM signals â€“ insert a defined dead time value â€“ use the break feature â€“ lock the desired parameters This example is based on the STM32F4xx TIM LL API; peripheral initialization is done using LL unitary services functions for optimization purpose (performance and size). | - | - | - | - | - | - | - | - | - | - | - | - | X | - | - | - | - | - | - | |
TIM_DMA |
This example provides a description of how to use DMA with TIMER update request to transfer Data from memory to TIMER Capture Compare Register 3 (TIMx_CCR3); Example using the STM32F4xx TIM LL API, peripheral initialization done using LL unitary services functions for optimization purpose (performance and size). | - | - | - | - | - | - | - | - | - | - | - | - | X | - | - | - | - | - | - | ||
TIM_InputCapture |
This example shows how to use the TIM peripheral to measure the frequency of a periodic signal provided either by an external signal generator or by another timer instance; Example using the STM32F4xx TIM LL API, peripheral initialization done using LL unitary services functions for optimization purpose (performance and size). | - | - | - | - | - | - | - | - | - | - | - | - | X | - | - | - | - | - | - | ||
TIM_OnePulse |
This example shows how to configure a timer to generate a positive pulse in Output Compare mode with a length of tPULSE and after a delay of tDELAY; This example is based on the STM32F4xx TIM LL API; peripheral initialization is done using LL unitary services functions for optimization purpose (performance and size). | - | - | - | - | - | - | - | - | - | - | - | - | X | - | - | - | - | - | - | ||
TIM_OutputCompare |
This example shows how to configure the TIM peripheral to generate an output waveform in different output compare modes; Example using the STM32F4xx TIM LL API, peripheral initialization done using LL unitary services functions for optimization purpose (performance and size). | - | - | - | - | - | - | - | - | - | - | - | - | X | - | - | - | - | - | - | ||
TIM_PWMOutput |
This example describes how to use a timer peripheral to generate a PWM output signal and update PWM duty cycle; Example using the STM32F4xx TIM LL API, peripheral initialization done using LL unitary services functions for optimization purpose (performance and size). | - | - | - | - | - | - | - | - | - | - | - | - | X | - | - | - | - | - | - | ||
TIM_PWMOutput_Init |
This example describes how to use a timer peripheral to generate a PWM output signal and update PWM duty cycle; Example using the STM32F4xx TIM LL API, peripheral initialization done using LL initialization function to demonstrate LL init usage. | - | - | - | - | - | - | - | - | - | - | - | - | X | - | - | - | - | - | - | ||
TIM_TimeBase |
This example shows how to configure the TIM peripheral to generate a time base; Example using the STM32F4xx TIM LL API, peripheral initialization done using LL unitary services functions for optimization purpose (performance and size). | - | - | - | - | - | - | - | - | - | - | - | - | X | - | - | - | - | - | - | ||
USART |
USART_Communication_Rx_IT |
This example shows how to configure GPIO and USART peripheral for receiving characters from HyperTerminal (PC) in Asynchronous mode using Interrupt mode. Peripheral initialization is done using LL unitary services functions for optimization purpose (performance and size). | - | - | - | - | - | - | - | - | - | - | - | - | X | - | - | - | - | - | - | |
USART_Communication_Rx_IT_Continuous |
This example shows how to configure GPIO and USART peripheral for continuously receiving characters from HyperTerminal (PC) in Asynchronous mode using Interrupt mode. Peripheral initialization is done using LL unitary services functions for optimization purpose (performance and size). | - | - | - | - | - | - | - | - | - | - | - | - | X | - | - | - | - | - | - | ||
USART_Communication_Rx_IT_Init |
This example shows how to configure GPIO and USART peripheral for receiving characters from HyperTerminal (PC) in Asynchronous mode using Interrupt mode. Peripheral initialization is done using LL initialization function to demonstrate LL init usage. | - | - | - | - | - | - | - | - | - | - | - | - | X | - | - | - | - | - | - | ||
USART_Communication_Tx |
This example shows how to configure GPIO and USART peripherals to send characters asynchronously to an HyperTerminal (PC) in Polling mode. If the transfer could not be completed within the allocated time, a timeout allows to exit from the sequence with a Timeout error code. This example is based on STM32F4xx USART LL API. Peripheral initialization is done using LL unitary services functions for optimization purpose (performance and size). | - | - | - | - | - | - | - | - | - | - | - | - | X | - | - | - | - | - | - | ||
USART_Communication_TxRx_DMA |
This example shows how to configure GPIO and USART peripheral to send characters asynchronously to/from an HyperTerminal (PC) in DMA mode. This example is based on STM32F4xx USART LL API. Peripheral initialization is done using LL unitary services functions for optimization purpose (performance and size). | - | - | - | - | - | - | - | - | - | - | - | - | X | - | - | - | - | - | - | ||
USART_Communication_Tx_IT |
This example shows how to configure GPIO and USART peripheral to send characters asynchronously to HyperTerminal (PC) in Interrupt mode. This example is based on STM32F4xx USART LL API. Peripheral initialization is done using LL unitary services functions for optimization purpose (performance and size). | - | - | - | - | - | - | - | - | - | - | - | - | X | - | - | - | - | - | - | ||
USART_HardwareFlowControl |
This example shows how to configure GPIO and USART peripheral to receive characters asynchronously from HyperTerminal (PC) in Interrupt mode with Hardware Flow Control feature enabled. This example is based on STM32F4xx USART LL API. Peripheral initialization is done using LL unitary services functions for optimization purpose (performance and size). | - | - | - | - | - | - | - | - | - | - | - | - | X | - | - | - | - | - | - | ||
USART_SyncCommunication_FullDuplex_DMA |
This example shows how to configure GPIO, USART, DMA and SPI peripherals for transmitting bytes from/to an USART peripheral to/from an SPI peripheral (in slave mode) by using DMA mode through the STM32F4xx USART LL API. Peripheral initialization is done using LL unitary services functions for optimization purpose (performance and size). | - | - | - | - | - | - | - | - | - | - | - | - | X | - | - | - | - | - | - | ||
USART_SyncCommunication_FullDuplex_IT |
This example shows how to configure GPIO, USART, DMA and SPI peripherals for transmitting bytes from/to an USART peripheral to/from an SPI peripheral (in slave mode) by using Interrupt mode through the STM32F4xx USART LL API (SPI is using DMA for receving/transmitting characters sent from/received by USART). Peripheral initialization is done using LL unitary services functions for optimization purpose (performance and size). | - | - | - | - | - | - | - | - | - | - | - | - | X | - | - | - | - | - | - | ||
UTILS |
UTILS_ConfigureSystemClock |
This example describes how to use UTILS LL API to configure the system clock using PLL with HSI as source clock. The user application just needs to calculate PLL parameters using STM32CubeMX and call the UTILS LL API. | - | - | - | - | - | - | - | - | - | - | - | - | X | - | - | - | - | - | - | |
UTILS_ReadDeviceInfo |
This example describes how to read UID, Device ID and Revision ID and save them into a global information buffer. | - | - | - | - | - | - | - | - | - | - | - | - | X | - | - | - | - | - | - | ||
WWDG |
WWDG_RefreshUntilUserEvent |
This example describes how to configure the WWDG, periodically update the counter, and generate an MCU WWDG reset when a user button is pressed. Peripheral initialization is done using LL unitary services functions for optimization purpose (performance and size). | - | - | - | - | - | - | - | - | - | - | - | - | X | - | - | - | - | - | - | |
| Total number of examples_ll: 71 | 0 | 0 | 0 | 7 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 62 | 0 | 2 | 0 | 0 | 0 | 0 | |||
Examples_MIX |
ADC |
ADC_SingleConversion_TriggerSW_IT |
This example describes how to use the ADC to perform a single ADC channel conversion, at each software start. This example uses the interrupt programming model (for programming models in Polling or DMA mode, refer to other examples). This example is based on the STM32F4xx ADC HAL and LL API (LL API usage for performance improvement). | - | - | - | X | - | - | - | - | - | - | - | - | - | - | - | - | - | - | - |
CRC |
CRC_CalculateAndCheck |
This example provides a description of how to use CRC peripheral through the STM32F4xx CRC HAL & LL API (LL API used for performance improvement); Fixed generator polynomial used in CRC IP is CRC-32 (Ethernet) polynomial: 0x4C11DB7. | - | - | - | - | - | - | - | - | - | - | - | - | X | - | - | - | - | - | - | |
DMA |
DMA_FLASHToRAM |
This example provides a description of how to use a DMA to transfer a word data buffer from Flash memory to embedded SRAM through the STM32F4xx DMA HAL and LL API (LL API used for performance improvement). | - | - | - | - | - | - | - | - | - | - | - | - | X | - | - | - | - | - | - | |
DMA2D |
DMA2D_MemToMemWithLCD |
This example provides a description of how to configure the DMA2D peripheral in Memory_to_Memory transfer mode and display the result on LCD, in resorting to DMA2D LL APIs for performance improvement. | - | - | - | X | - | - | - | - | - | - | - | - | - | - | - | - | - | - | - | |
I2C |
I2C_OneBoard_ComSlave7_10bits_IT |
This example describes how to perform I2C data buffer transmission/reception between one master and 2 slaves with different address sizes (7-bit or 10-bit) and different Max speed support (400Khz or 100Khz). This example uses the STM32F4xx I2C HAL and LL API (LL API usage for performance improvement) and an interrupt. | - | - | - | - | - | - | - | - | - | - | - | - | X | - | - | - | - | - | - | |
PWR |
PWR_STANDBY_RTC |
This example shows how to enter Standby mode and wake up from this mode using an external RESET or the RTC Wakeup Timer through the STM32F4xx RTC and RCC HAL and LL API (LL API usage for performance improvement). | - | - | - | - | - | - | - | - | - | - | - | - | X | - | - | - | - | - | - | |
PWR_STOP |
This example shows how to enter the system in STOP with Low power regulator mode and wake-up from this mode using external RESET or wake-up interrupt (all the RCC functions calls use RCC LL API for footprint and performance improvements). | - | - | - | - | - | - | - | - | - | - | - | - | X | - | - | - | - | - | - | ||
SPI |
SPI_FullDuplex_ComPolling |
This example shows how to ensure SPI data buffer transmission/reception in Polling mode between two boards. | - | - | - | - | - | - | - | - | - | - | - | - | X | - | - | - | - | - | - | |
SPI_HalfDuplex_ComPollingIT |
This example shows how to ensure SPI data buffer transmission/reception between two boards by using Polling (LL Driver) an interrupt mode (HAL Driver). | - | - | - | - | - | - | - | - | - | - | - | - | X | - | - | - | - | - | - | ||
TIM |
TIM_6Steps |
This example shows how to configure the TIM1 peripheral to generate 6 Steps PWM signal. The STM32F4xx TIM1 peripheral allows programming in advance the configuration for the next TIM1 output behavior (or step) and changing the configuration of all the channels simultaneously. This operation is possible when the COM (commutation) event is used. This example is based on the STM32F4xx TIM HAL and LL API (LL API usage for performance improvement). | - | - | - | - | - | - | - | - | - | - | - | - | X | - | - | - | - | - | - | |
TIM_PWMInput |
This example shows how to use the TIM peripheral to measure the frequency and duty cycle of an external signal. | - | - | - | - | - | - | - | - | - | - | - | - | X | - | - | - | - | - | - | ||
UART |
UART_HyperTerminal_IT |
This example describes how to use an UART to transmit data (transmit/receive) between a board and an HyperTerminal PC application in Interrupt mode. This example provides a description of how to use USART peripheral through the STM32F4xx UART HAL and LL API (LL API usage for performance improvement). | - | - | - | - | - | - | - | - | - | - | - | - | X | - | - | - | - | - | - | |
UART_HyperTerminal_TxPolling_RxIT |
This example describes how to use an UART to transmit data (transmit/receive) between a board and an HyperTerminal PC application both in Polling and Interrupt modes. This example provides a description of how to use USART peripheral through the STM32F4xx UART HAL and LL API (LL API usage for performance improvement). | - | - | - | - | - | - | - | - | - | - | - | - | X | - | - | - | - | - | - | ||
| Total number of examples_mix: 13 | 0 | 0 | 0 | 2 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 11 | 0 | 0 | 0 | 0 | 0 | 0 | |||
Applications |
Audio |
Audio_playback_and_record |
This application shows how to use the different functionalities of Audio device and ST MEMS microphones. | X | - | X | - | - | - | - | X | - | X | - | - | - | X | - | X | X | - | - |
Camera |
Camera_To_USBDisk |
This application provides a short description of how to use the DCMI to interface with camera module and display in continuous mode the picture on LCD and to save a picture in USB device. | X | - | X | - | - | - | - | X | - | - | - | - | - | - | - | - | - | - | X | |
Display |
LCD_AnimatedPictureFromSDCard |
This application describes how to display an animated picture on LCD saved under microSD. | - | - | - | - | - | - | - | X | - | - | - | - | - | X | - | - | - | - | - | |
LCD_DSI_ImagesSlider |
This application aims to show the outstanding capability of Display Serial Interface (DSI) periphiral to display images with high resolution (800x480). With a simple movement of finger, the content of GRAM is directly updated and displayed on DSI LCD. | - | - | - | - | - | - | - | X | - | - | - | - | - | X | - | - | - | - | - | ||
LCD_Paint |
This application describes how to configure LCD touch screen and attribute an action related to configured touch zone and how to save BMP picture in SDCard. | - | - | - | - | - | - | - | X | - | - | - | - | - | X | - | - | - | - | X | ||
LCD_PicturesFromSDCard |
This application describes how to display on LCD pictures saved under SD card. | - | - | - | - | - | X | - | X | - | - | - | - | - | - | - | - | - | X | - | ||
LTDC_AnimatedPictureFromSDCard |
This application describes how to display on LCD an animated picture saved under microSD. | X | - | - | - | - | - | - | - | - | - | - | - | - | - | - | - | - | - | - | ||
LTDC_AnimatedPictureFromUSB |
This application describes how to display on LCD pictures saved under USB mass storage. | - | - | - | - | X | - | - | - | - | - | - | - | - | - | - | - | - | - | - | ||
LTDC_Paint |
This application describes how to configure LCD touch screen and attribute an action related to configured touch zone. | X | - | - | - | X | - | - | - | - | - | - | - | - | - | - | - | - | - | - | ||
LTDC_PicturesFromSDCard |
This application describes how to display on LCD pictures saved under SD card. | X | - | - | - | - | - | - | - | - | - | - | - | - | - | - | - | - | - | - | ||
EEPROM |
EEPROM_Emulation |
This application describes the software solution for substituting standalone EEPROM by emulating the EEPROM mechanism using the on-chip Flash of STM32F4xx device. | X | X | X | X | X | X | X | X | X | X | X | X | X | X | X | X | X | - | X | |
FatFs |
FatFs_MultiDrives |
This application provides a description on how to use STM32Cube firmware with FatFs middleware component as a generic FAT file system module, in order to develop an application exploiting FatFs offered features with multidrives (RAMDisk, uSD) configuration. | X | - | X | - | - | - | - | - | - | - | - | - | - | - | - | - | - | - | X | |
FatFs_RAMDisk |
This application provides a description on how to use STM32Cube firmware with FatFs middleware component as a generic FAT file system module, in order to develop an application exploiting FatFs offered features with RAM disk (SDRAM) drive configuration. | X | - | X | - | X | - | - | X | - | - | - | - | - | X | - | - | - | - | X | ||
FatFs_RAMDisk_RTOS |
This application provides a description on how to use STM32Cube firmware with FatFs middleware component as a generic FAT file system module, in order to develop an application exploiting FatFs offered features with RAM disk (SRAM) drive in RTOS mode configuration. | X | - | X | - | - | - | - | - | - | - | - | - | - | - | - | - | - | - | X | ||
FatFs_USBDisk |
This application provides a description on how to use STM32Cube firmware with FatFs middleware component as a generic FAT file system module and STM32 USB On-The-Go (OTG) host library, in Full Speed (FS) mode, in order to develop an application exploiting FatFs offered features with USB disk drive configuration. | X | - | X | X | X | X | X | X | X | X | X | - | - | X | - | X | X | X | X | ||
FatFs_USBDisk_MultipleAccess_RTOS |
This application provides a description on how to use STM32Cube firmware with FatFs middleware component as a generic FAT file system module, FreeRTOS as an RTOS module based on using CMSIS-OS wrapping layer common APIs, and also STM32 USB On-The-Go (OTG) host library, in Full Speed (FS), in order to develop an application exploiting FatFs offered features with USB disk drive in RTOS mode configuration. | X | - | X | - | - | X | - | - | - | - | - | - | - | - | - | - | - | X | X | ||
FatFs_USBDisk_RTOS |
This application provides a description on how to use STM32Cube firmware with FatFs middleware component as a generic FAT file system module, FreeRTOS as an RTOS module based on using CMSIS-OS wrapping layer common APIs, and also STM32 USB On-The-Go (OTG) host library, in Full Speed (FS) mode, in order to develop an application exploiting FatFs offered features with USB disk drive in RTOS mode configuration. | X | - | X | - | - | X | - | - | - | - | - | - | - | - | - | - | - | X | X | ||
FatFs_uSD |
This application provides a description on how to use STM32Cube firmware with FatFs middleware component as a generic FAT file system module, in order to develop an application exploiting FatFs offered features with microSD drive configuration. | X | - | X | - | - | X | X | X | X | - | - | - | - | X | - | - | - | X | X | ||
FatFs_uSD_RTOS |
This application provides a description on how to use STM32Cube firmware with FatFs middleware component as a generic FAT file system module. | X | - | X | - | - | X | - | X | - | - | - | - | - | - | - | - | - | X | X | ||
FreeRTOS |
FreeRTOS_LowPower |
How to enter and exit low-power mode with CMSIS RTOS API. | X | - | X | - | - | X | X | X | - | - | - | - | - | - | - | - | - | - | X | |
FreeRTOS_MPU |
How to use the MPU feature of FreeRTOS. | X | - | X | - | X | X | X | X | - | - | - | - | - | X | - | - | - | X | X | ||
FreeRTOS_Mail |
How to use mail queues with CMSIS RTOS API. | - | - | - | - | - | X | X | - | - | - | - | - | - | - | - | - | - | - | - | ||
FreeRTOS_Mutexes |
How to use mutexes with CMSIS RTOS API. | X | - | X | - | - | X | X | X | - | - | - | - | - | - | - | - | - | - | X | ||
FreeRTOS_Queues |
How to use message queues with CMSIS RTOS API. | X | - | X | - | - | X | X | X | - | - | - | - | - | - | - | - | - | - | X | ||
FreeRTOS_Semaphore |
How to use semaphores with CMSIS RTOS API. | X | - | X | - | - | X | X | X | - | - | - | - | - | - | - | - | - | - | X | ||
FreeRTOS_SemaphoreFromISR |
How to use semaphore from ISR with CMSIS RTOS API. | X | - | X | - | - | X | X | X | - | - | - | - | - | - | - | - | - | - | X | ||
FreeRTOS_Signal |
How to perform thread signaling using CMSIS RTOS API. | - | - | - | - | - | X | X | - | - | - | - | - | - | - | - | - | - | X | - | ||
FreeRTOS_SignalFromISR |
How to perform thread signaling from an interrupt using CMSIS RTOS API. | - | - | - | - | - | X | X | - | - | - | - | - | - | - | - | - | - | - | - | ||
FreeRTOS_ThreadCreation |
How to implement thread creation using CMSIS RTOS API. | X | - | X | - | X | X | X | X | - | - | - | - | - | X | - | - | - | - | X | ||
FreeRTOS_Timers |
How to use timers of CMSIS RTOS API. | X | - | X | - | - | X | X | X | - | - | - | - | - | - | - | - | - | X | X | ||
IAP |
IAP_Main |
This directory contains a set of sources files and pre-configured projects that describes how to build an application to be loaded into Flash memory using In-Application Programming (IAP, through USART). | X | - | X | - | - | - | - | X | - | - | - | - | - | - | - | - | - | - | X | |
IAP_binary_template |
This directory contains a set of sources files that build the application to be loaded into Flash memory using In-Application Programming (IAP, through USART). | X | - | X | - | - | - | - | X | - | - | - | - | - | - | - | - | - | - | X | ||
LibJPEG |
LibJPEG_Decoding |
This application demonstrates how to read jpeg file from USB disk, decode it and display the final BMP image on the LCD. | X | - | X | - | X | X | - | X | - | - | - | - | - | X | - | - | - | X | X | |
LibJPEG_Encoding |
This application demonstrates how to read BMP file from USB disk, encode it, save the jpeg file in USB disk then decode the jpeg file and display the final BMP image on the LCD. | X | - | X | - | X | X | - | X | - | - | - | - | - | X | - | - | - | X | X | ||
LwIP |
LwIP_HTTP_Server_Netconn_RTOS |
This application guides STM32Cube HAL API users to run a http server application based on Netconn API of LwIP TCP/IP stack The communication is done with a web browser application in a remote PC. | X | - | - | X | - | - | - | X | - | - | - | - | - | - | - | - | - | - | X | |
LwIP_HTTP_Server_Raw |
This application guides STM32Cube HAL API users to run a http server application based on Raw API of LwIP TCP/IP stack The communication is done with a web browser application in a remote PC. | X | - | - | - | - | - | - | - | - | - | - | - | - | - | - | - | - | - | X | ||
LwIP_HTTP_Server_Socket_RTOS |
This application guides STM32Cube HAL API users to run a http server application based on Socket API of LwIP TCP/IP stack The communication is done with a web browser application in a remote PC. | X | - | - | - | - | - | - | - | - | - | - | - | - | - | - | - | - | - | X | ||
LwIP_IAP |
This application guides STM32Cube HAL API users to run In-Application Programming (IAP) over Ethernet. | X | - | - | - | - | - | - | - | - | - | - | - | - | - | - | - | - | - | X | ||
LwIP_TCP_Echo_Client |
This application guides STM32Cube HAL API users to run TCP Echo Client application based on Raw API of LwIP TCP/IP stack To run this application, On the remote PC, open a command prompt window. | X | - | - | - | - | - | - | X | - | - | - | - | - | - | - | - | - | - | X | ||
LwIP_TCP_Echo_Server |
This application guides STM32Cube HAL API users to run TCP Echo Server application based on Raw API of LwIP TCP/IP stack To run this application, On the remote PC, open a command prompt window. | X | - | - | - | - | - | - | X | - | - | - | - | - | - | - | - | - | - | X | ||
LwIP_TFTP_Server |
This application guides STM32Cube HAL API users to run a tftp server demonstration for STM32F4xx devices. | X | - | - | - | - | - | - | X | - | - | - | - | - | - | - | - | - | - | X | ||
LwIP_UDPTCP_Echo_Server_Netconn_RTOS |
This application guides STM32Cube HAL API users to run a UDP/TCP Echo Server application based on Netconn API of LwIP TCP/IP stack To run this application, On the remote PC, open a command prompt window. | X | - | - | - | - | - | - | X | - | - | - | - | - | - | - | - | - | - | X | ||
LwIP_UDP_Echo_Client |
This application guides STM32Cube HAL API users to run a UDP Echo Client application based on Raw API of LwIP TCP/IP stack To run this application, On the remote PC, open a command prompt window. | X | - | - | - | - | - | - | X | - | - | - | - | - | - | - | - | - | - | X | ||
LwIP_UDP_Echo_Server |
This application guides STM32Cube HAL API users to run UDP Echo Server application based on Raw API of LwIP TCP/IP stack To run this application, On the remote PC, open a command prompt window. | X | - | - | - | - | - | - | X | - | - | - | - | - | - | - | - | - | - | X | ||
STemWin |
STemWin_Acceleration |
This directory contains a set of source files that implement a simple "acceleration" application based on STemWin for STM32F4xx devices. | X | - | - | - | X | - | - | X | - | - | - | - | - | X | - | - | - | - | - | |
STemWin_Animation |
This directory contains a set of source files that implement a simple "animation" application based on STemWin for STM32F4xx devices. | X | - | - | - | X | - | - | X | - | - | - | - | - | X | - | - | - | - | - | ||
STemWin_Fonts |
This directory contains a set of source files that implement a simple "fonts" application based on STemWin for STM32F4xx devices. | X | - | - | - | X | - | - | X | - | - | - | - | - | X | - | - | - | - | - | ||
STemWin_HelloWorld |
Simple "Hello World" example based on STemWin for STM32F4xx devices. | X | - | X | - | X | X | - | X | - | - | - | - | - | X | - | - | - | X | X | ||
STemWin_MemoryDevice |
This directory contains a set of source files that implement a simple "memory device" application based on STemWin for STM32F4xx devices. | X | - | - | - | X | - | - | X | - | - | - | - | - | X | - | - | - | - | - | ||
STemWin_SampleDemo |
This application shows how to implement a sample demonstration example allowing to show some of the STemWin Library capabilities. | X | - | X | - | X | - | - | X | - | - | - | - | - | X | - | - | - | - | X | ||
USB_Device |
AUDIO_Standalone |
This application shows how to use the implementation of the audio streaming (Out: Speaker/Headset) capability on the STM32F4xx devices. | X | - | X | - | - | - | - | - | - | - | - | - | - | X | - | - | - | - | X | |
CDC_Standalone |
This application shows how to use the USB device application based on the Device Communication Class (CDC) following the PSTN subprotocol using the USB Device and UART peripherals. | X | - | X | - | - | - | - | X | - | - | - | - | - | - | - | - | - | - | X | ||
CustomHID_Standalone |
This application shows how to use the USB device application based on the Human Interface (HID) on the STM32F4xx devices. | X | - | X | - | - | - | - | - | - | - | - | - | - | - | - | - | - | - | X | ||
DFU_Standalone |
This application presents a compliant implementation of the Device Firmware Upgrade (DFU) capability for programming the embedded flash memory through the USB peripheral on the STM32F4xx devices. | X | - | X | X | - | - | X | X | - | - | X | - | - | X | - | - | - | X | X | ||
DualCore_Standalone |
This application is a part of the USB Device Library package using STM32Cube firmware. It describes how to use USB device application based on the STM32F4xx multi core support feature integrating Mass Storage (MSC) and Human Interface (HID) in the same project. | X | - | X | - | - | - | - | X | - | - | - | - | - | - | - | - | - | - | X | ||
HID_BCD_Standalone |
The the STM32F4xx devices integrated battery charger detection circuitry supports USB-IF Battery Charger Detection, BCD,(revision 1.2). The hpcd.Init.battery_charging_enable in the usbd_conf.c should be set to 1 to enable the support for BCD. | - | - | - | - | - | - | - | - | - | - | - | - | - | - | - | - | - | X | - | ||
HID_LPM_Standalone |
The STM32F4xx devices support the USB Link Power Management Protocol (LPM-L1) and complies with the USB 2.0 LPM-L1 ECN. The hpcd.Init.lpm_enable in the usbd_conf.c should be set to 1 to enable the support for LPM-L1 protocol in the USB stack. | - | - | X | - | - | - | - | X | - | - | - | - | - | X | - | - | - | - | - | ||
HID_Standalone |
This application shows how to use the USB device application based on the Human Interface (HID) on the STM32F4xx devices. | X | - | X | X | - | X | X | X | X | - | X | - | - | X | - | - | - | X | X | ||
MSC_Standalone |
This application shows how to use the USB device application based on the Mass Storage Class (MSC) on the STM32F4xx devices. | X | - | X | - | - | X | X | X | - | - | - | - | - | X | - | - | - | X | X | ||
USB_Host |
AUDIO_Standalone |
This application shows how to use the USB host application based on the Audio OUT class on the STM32F4xx devices. | X | - | - | - | - | X | - | - | - | - | - | - | - | - | - | - | - | - | X | |
CDC_Standalone |
This application shows how to use the USB host application based on the Communication Class (CDC) on the STM32F4xx devices. | X | - | - | - | - | - | - | - | - | - | - | - | - | X | - | - | - | - | X | ||
DualCore_Standalone |
This application is a part of the USB Host Library package using STM32Cube firmware. It describes how to use USB host application based on the STM32F4xx multi core support feature integrating Mass Storage (MSC) and Human Interface (HID) in the same project. | X | - | - | - | - | - | - | X | - | - | - | - | - | - | - | - | - | - | X | ||
DynamicSwitch_Standalone |
This application is a part of the USB Host Library package using STM32Cube firmware. It describes how to use dynamically switch, on the same port, between available USB host applications on the STM32F4xx devices. | X | - | - | - | - | - | - | - | - | - | - | - | - | X | - | - | - | - | X | ||
FWupgrade_Standalone |
The firmware upgrade application or In-Application programming (IAP) is a feature that allows a user application to erase and write to on-chip flash memory. | X | - | X | - | X | - | - | - | - | - | - | - | - | X | - | - | - | - | X | ||
HID_RTOS |
This application shows how to use the USB host application based on the HID class on the STM32F4xx devices. | X | - | X | - | - | - | - | X | X | - | - | - | - | X | - | - | - | - | X | ||
HID_Standalone |
This application shows how to use the USB host application based on the HID class on the STM32F4xx device. | X | - | X | X | - | X | X | X | X | - | X | - | - | X | - | - | - | X | X | ||
MSC_RTOS |
This application shows how to use the USB host application based on the Mass Storage Class (MSC) on the STM32F4xx devices in RTOS mode configuration. | X | - | X | - | - | - | - | - | X | - | - | - | - | X | - | - | - | - | X | ||
MSC_Standalone |
This application shows how to use the USB host application based on the Mass Storage Class (MSC) on the STM32F4xx device. | X | - | X | X | - | - | X | X | X | - | X | - | - | X | - | - | - | X | X | ||
MTP_Standalone |
This application shows how to use the USB host application based on the Media Transfer Protocol (MTP) on the STM32F4xx devices. | X | - | - | - | - | - | - | - | - | - | - | - | - | - | - | - | - | - | X | ||
WIFI |
WiFi_Client_Server |
This application shows how to use the Es-WiFi module to perform a TCP client mode using STM32 Cube HAL. It demonstrates how to set up a client program, connect it to a TCP server. | - | - | - | - | - | - | - | - | - | - | - | - | - | - | - | - | - | X | - | |
WiFi_HTTP_Server |
This application shows how to make HTTP requests using the Es-WiFi module based on STM32 Cube HAL. | - | - | - | - | - | - | - | - | - | - | - | - | - | - | - | - | - | X | - | ||
mbedTLS |
SSL_Client |
This application describes how to run an SSL client application based on mbedTLS crypto library and LwIP TCP/IP stack on STM32F4 family. | X | - | - | - | - | - | - | X | - | - | - | - | - | - | - | - | - | - | X | |
SSL_Server |
This application guides STM32Cube HAL API users to run an SSL Server application based on mbedTLS crypto library and LwIP TCP/IP stack. | X | - | - | - | - | - | - | X | - | - | - | - | - | - | - | - | - | - | X | ||
| Total number of applications: 345 | 61 | 1 | 38 | 7 | 16 | 25 | 19 | 48 | 8 | 3 | 6 | 1 | 1 | 30 | 1 | 3 | 3 | 20 | 54 | |||
Demonstrations |
- |
Demo |
The provided demonstration firmware based on STM32Cube helps you to discover STM32 Cortex-M devices that can be plugged on a STM32NUCLEO board. | - | - | - | X | - | - | X | - | X | X | X | - | X | - | - | X | X | - | - |
STemWin |
The STM32Cube Demonstration platform comes on top of the STM32CubeTM as a firmware package that offers a full set of software components based on a modules architecture allowing re-using them separately in standalone applications. All these modules are managed by the STM32Cube Demonstration kernel allowing to dynamically adding new modules and access to common resources (storage, graphical components and widgets, memory management, Real-Time operating system) The demonstration firmware is built around the graphical library STemWin and the FreeRTOS real time operating system and uses almost the whole STM32 capability to offer a large scope of usage based on the STM32Cube HAL, BSP and several Middleware components. | X | - | X | - | X | X | - | X | - | - | - | - | - | X | - | - | - | X | X | ||
TouchGFX |
This is a demonstration from Draupner Graphics for MCUs with LCDs attached. | X | - | - | - | X | - | - | X | - | - | - | - | - | X | - | - | - | - | - | ||
| Total number of demonstrations: 20 | 2 | 0 | 1 | 1 | 2 | 1 | 1 | 2 | 1 | 1 | 1 | 0 | 1 | 2 | 0 | 1 | 1 | 1 | 1 | |||
| Total number of projects: 1230 | 152 | 10 | 112 | 46 | 50 | 79 | 70 | 147 | 53 | 30 | 36 | 16 | 86 | 80 | 21 | 33 | 30 | 50 | 129 |


Effects of Protein Adsorption and Thrombus Formation on pH Sensor Laboratory Techniques Course
This lab report covers the topic of protien absorption and thrombus formation on a pH sensor and was written in the Laboratory Techniqes course at Michigan Tech. This course focused on experimental techniques used in biomedical engineering, technical report writing, and record keeping.
This lab report covers the topic of blood flow and was written in the Laboratory Techniqes course at Michigan Tech. This course focused on experimental techniques used in biomedical engineering, technical report writing, and record keeping.
This paper showcases the final paper that I wrote for the Biomedical Ethics course I took at Michigan Tech. This class focuses on the analysis of issues that arise in medical practice as well as biomedical science. The issues studied throughout this course include euthanasia, abortion, the physician-patient relationship, experimentation involving human subjects, and allocation of scarce biomedical resources.
What is an Ethical Engineer? Engineering Ethics Course
This paper discusses the topic of what it is to be an ethical engineer. Since I am not an engineer, I took a different approach to this topic by first defining how to be ethical in the professional world and how that would apply to me as a technical writer.


I am graduate who is quick learner and thriving to achieve goals with positive attitude . I am always focused with tasks in hand and ready to learn new technologies. Well versed in Java , React and React Native .
Developed web page using React and mobile app using react native . Implemented CI/CD using jenkins in project . Developed custom algorithm for project .
Responsibilities
Professional References Available
Developed app to manage nurition intake of users and send push notifications to users . Custom algorithm was developed for suggesting users which nutients to take . All developed was in react native .
Worked on various projects as software developer . Writing code and de bugging errors . Developed customer feedback portal for company . Helped in developement of student management system .
GPA: Distinction
Grade : Distinction
Apart from being a web developer, I am competitive gamer and love to try out various genre of games . I spend my time indoor watching movies , listening to all kinds of musics , doing coding for fun , watching videos and reading blogs which are mostly related to gadgets and new technologies . I love doing investement banking and learn as much as possible .
When I do get time to go out , I like to go to beaches , do some cycling and always try out different cuisines .


Understanding Async Await In The Context Of The Event Loop
Understanding Async Await In The Context Of The Event Loop
There’s a special syntax to work with promises in a more comfortable fashion, called “async/await”. It’s surprisingly easy to understand and use.
The following excerpt comes from the phenomenally written article on the subject of the callstack and event-queue by Lidia Hallie!
JavaScript is single-threaded: only one task can run at a time.
To compensate, browsers like Google Chrome give us some features that Javascript does not provide in isolation, namely… a Web API.
When we invoke a function, it gets added to something called the call stack.
It’s a stack, meaning that it’s first in, last out (think of a pile of pancakes).
When a function returns a value, it gets popped off the stack
-
The
respond
function returns asetTimeout
function. -
The
setTimeout
is provided to us by the Web API: - it lets us delay tasks without blocking the main thread.
-
The callback function that we passed to the
setTimeout
function,
the arrow function() => { return
'Hey'
}
- gets added to the Web API.
-
In the meantime, the
setTimeout
function and the respond function get popped off the stack, they both returned their values!
In the Web API, a timer runs for as long as the second argument we passed to it, 1000ms.
The callback doesn’t immediately get added to the call stack, instead it’s passed to something called the queue.
This does not mean that the callback function gets added to the callstack (returns) after 1000ms!
This means that the function has been added to the queue after 1000ms where it will wait for it’s proper FIFO designated turn to excite.
The event loop is simply a mechanism for connecting the queue with the call stack!
An analogy to this relationship exists in facebook market place… the marketplace doesn’t actually buy or sell anything… it just provides a framework for which buyers and sellers can interface productively. It’s not a perfect analogy… the point is that the event loop is not some third tangible entity… it’s just the relationship between the stack and queue.
If the call stack is empty:
meaning all previously invoked functions have returned their values and have been popped off the stack…
The first item in the queue gets added to the call stack:
In this case, no other functions were invoked, meaning that the call stack was empty by the time the callback function was the first item in the queue.
The callback is added to the call stack
- Gets invoked… returns a value…( gets popped off the stack).
-
We invoke
bar
.bar
returns asetTimeout
function. -
The callback we passed to
setTimeout
gets added to the Web API, thesetTimeout
function andbar
get popped off the callstack. -
The timer runs, in the meantime
foo
gets invoked and logsFirst
.foo
returns (undefined),baz
gets invoked, and the callback gets added to the queue. -
baz
logsThird
. The event loop sees the callstack is empty afterbaz
returned, after which the callback gets added to the call stack. -
The callback logs
Second
.
Practice:
Async/await
There’s a special syntax to work with promises in a more comfortable fashion, called “async/await”. It’s surprisingly easy to understand and use.
Async functions
Let’s start with the
async
keyword.
It can be placed before a function, like this:
//Let's start with the async keyword. It can be placed before a function, like this:
async function f() {
return 1;
}
…We could explicitly return a promise, which would be the same:
So, `async` ensures that the function returns a promise, and wraps non-promises in it.
There’s another keyword, `await`, that works only inside `async` functions.
The syntax:
//await only works inside the lexical scope of an asynchronous function.
let value = await promise;
The keyword
await
makes
JavaScript wait until that promise settles and returns
its result.
Here’s an example with a promise that resolves in 1 second:
The function execution “pauses” at line 5 and resumes when the promise resolves, taking the promise’s eventual resolution as it’s value.
The code above shows “done!” in one second.
Await
suspends
the function execution until the promise settles, and then
resumes it with the promise result.
Summary
The
async
keyword
before a function has two effects:
- Makes it always return a promise.
-
Allows
await
to be used in it.
The
await
keyword
before a promise makes JavaScript wait until that promise
settles, and then:
TBC…


Thank you for supporting the Seattle Attic Community Workshop.
Many companies will match donations to 501(c)3 charities. Microsoft employees, for example, can go to MS Give (an intranet link) and search for Independent Arts & Media to have donations matched. Please indicate in the comments on your donation that it is intended for the Seattle Attic Community Workshop so that IAM can route it appropriately.
If you haven't already, please consider subscribing to our low-volume annoucements mailing list.
PayPal
Donate through PayPal or with your credit card!
Dwolla
Dwolla has fewer fees than PayPal, if you want to increase the amount we get for the same money! Note: the button requires Javascript from dwolla.com to work.
Many companies will match donations to 501(c)3 charities. Microsoft employees, for example, can go to MS Give (an intranet link) and search for Seattle Attic Community Workshop to have donations matched.