Copyright 2017 STMicroelectronics
The STM32CubeL4 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_L4_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 STM32CubeL4 Firmware package.
| Level | Module Name | Project Name | Description | STM32L476G-EVAL | NUCLEO-L4R5ZI-P | NUCLEO-L496ZG-P | NUCLEO-L412RB-P | NUCLEO-L432KC | STM32L4R9I-EVAL | NUCLEO-L4R5ZI | NUCLEO-L433RC-P | NUCLEO-L476RG | NUCLEO-L452RE-P | 32L496GDISCOVERY | NUCLEO-L496ZG | B-L475E-IOT01A | 32L4R9IDISCOVERY | 32L476GDISCOVERY | NUCLEO-L452RE | NUCLEO-L412KB |
Templates |
- |
Starter project |
Reference template based on the STM32Cube HAL 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 |
| Total number of templates: 17 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | |||
Templates_LL |
- |
Starter project |
Reference template based on the STM32Cube 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 |
| Total number of templates_ll: 17 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | |||
Examples |
- |
BSP |
How to use the different BSP drivers of the board. | X | - | - | - | - | X | - | - | - | - | - | - | X | X | X | - | - |
ADC |
ADC_AnalogWatchdog |
How to use the ADC peripheral to perform conversions with an analog watchdog and out-of-window interrupts enabled. | X | - | - | X | - | - | - | - | - | - | - | X | - | - | - | - | - | |
ADC_DMA_Transfer |
How to configure and use the ADC to convert an external analog input and get the result using a DMA transfer through the HAL API. | X | - | - | X | X | - | X | - | - | - | - | X | - | - | - | X | - | ||
ADC_DifferentialMode |
How to use an ADC peripheral to perform a conversion in differential mode between 2 ADC channels. | - | - | - | X | - | - | - | - | - | - | - | - | - | - | - | - | - | ||
ADC_DualModeInterleaved |
How to use two ADC peripherals to perform conversions in dual interleaved mode. | X | - | - | X | - | - | - | - | - | - | - | X | - | - | - | - | - | ||
ADC_LowPower |
How to use the ADC peripheral to perform conversions in ADC auto-wait low-power mode. | - | - | - | - | - | - | - | - | - | - | - | - | - | - | - | X | - | ||
ADC_OverSampler |
How to use an ADC peripheral in oversampling mode to increase resolution. | X | - | - | - | X | - | X | - | - | - | - | X | - | - | - | X | - | ||
ADC_Oversampling |
How to use an ADC peripheral in oversampling mode to increase resolution. | - | - | - | X | - | - | - | - | - | - | - | - | - | - | - | - | - | ||
ADC_RegularConversion_Interrupt |
How to use the ADC in interrupt mode to convert data through the HAL API. | - | - | - | - | 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_Regular_injected_groups |
How to use the ADC peripheral to perform conversions using the two ADC groups: regular group for ADC conversions on the main stream, and injected group for ADC conversions limited to specific events (conversions injected into the main conversion stream). | X | - | - | - | - | - | - | - | - | - | - | X | - | - | - | - | - | ||
ADC_Sequencer |
How to use the ADC peripheral with a sequencer to convert several channels. | X | - | - | X | - | - | X | - | - | - | - | X | - | - | - | - | - | ||
CAN |
CAN_Networking |
How to configure the CAN peripheral to send and receive CAN frames in normal mode. | X | - | - | - | - | - | - | - | - | - | - | - | - | - | - | - | - | |
COMP |
COMP_AnalogWatchdog |
How to use a comparator peripheral to compare a voltage level to a threshold: the internal voltage reference (VREFINT), in interrupt mode. | X | - | - | X | - | - | - | - | - | - | - | X | - | - | - | - | - | |
COMP_Interrupt |
How to use a comparator peripheral to compare a voltage level applied on a GPIO pin to the the internal voltage reference (VREFINT), in interrupt mode. | X | - | - | - | X | - | - | - | X | - | - | X | - | - | - | X | - | ||
COMP_PWMSignalControl |
How to configure a comparator peripheral to automatically hold the TIMER PWM output in the safe state (low level) as soon as the comparator output is set to a high level. | - | - | - | X | - | - | - | - | - | - | - | - | - | - | - | - | - | ||
CRC |
CRC_Bytes_Stream_7bit_CRC |
How to configure the CRC using the HAL API. The CRC (cyclic redundancy check) calculation unit computes 7-bit CRC codes derived from buffers of 8-bit data (bytes). The user-defined generating polynomial is manually set to 0x65, that is, X^7 + X^6 + X^5 + X^2 + 1, as used in the Train Communication Network, IEC 60870-5[17]. | - | - | - | X | X | X | X | - | X | - | - | X | - | - | - | - | X | |
CRC_Data_Reversing_16bit_CRC |
How to configure the CRC using the HAL API. The CRC (cyclic redundancy check) calculation unit computes a 16-bit CRC code derived from a buffer of 8-bit data (bytes). Input and output data reversal features are enabled. The user-defined generating polynomial is manually set to 0x1021, that is, X^16 + X^12 + X^5 + 1 which is the CRC-CCITT generating polynomial. | - | - | - | X | X | X | X | - | X | - | - | X | - | - | - | - | X | ||
CRC_Example |
How to configure the CRC using 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 | ||
CRC_UserDefinedPolynomial |
How to configure and use the CRC calculation unit to compute an 8-bit CRC code for a given data buffer, based on a user-defined generating polynomial. The peripheral initialization is done using LL unitary service functions for optimization purposes (performance and size). | X | - | - | X | X | X | X | - | X | - | - | X | - | - | X | X | X | ||
CRYP |
CRYP_AESModes |
How to use the CRYP peripheral to encrypt and decrypt data using AES in chaining modes (ECB, CBC, CTR). | X | - | - | - | - | - | - | - | - | - | - | X | - | - | - | X | - | |
CRYP_AESModes_Suspension |
How to use the CRYP AES peripheral to suspend then resume the AES ECB, CBC and CTR processing of a message in order to carry out the encryption or decryption of a higher-priority message. | X | - | - | - | - | - | - | - | - | - | - | X | - | - | - | X | - | ||
CRYP_DMA |
How to use the CRYP peripheral to encrypt and decrypt data using the AES-128 algorithm with ECB chaining mode in DMA mode. | X | - | - | - | - | - | - | - | - | - | - | X | - | - | - | X | - | ||
CRYP_GCM_GMAC_CMAC_Modes |
How to encrypt and decrypt data, and compute an authentication tag with GCM, GMAC, and CMAC AES algorithms. | X | - | - | - | - | - | - | - | - | - | - | X | - | - | - | X | - | ||
CRYP_GCM_GMAC_CMAC_Suspension |
How to use the CRYP AES peripheral to suspend then resume the AES GCM, GMAC and CMAC processing of a message in order to carry out the encryption, decryption or authentication tag computation of a higher-priority message. | X | - | - | - | - | - | - | - | - | - | - | X | - | - | - | X | - | ||
Cortex |
CORTEXM_MPU |
Presentation of the MPU feature. This example configures a memory area as privileged read-only, and attempts to perform read and write operations in different modes. | X | - | - | X | X | - | - | - | X | - | - | X | - | - | - | X | - | |
CORTEXM_ModePrivilege |
How to modify the Thread mode privilege access and stack. Thread mode is entered on reset or when returning from an exception. | X | - | - | X | X | - | - | - | X | - | - | X | - | - | - | X | - | ||
CORTEXM_ProcessStack |
How to modify the Thread mode stack. Thread mode is entered on reset, and can be entered as a result of an exception return. | - | - | - | X | - | - | - | - | - | - | - | X | - | - | - | X | - | ||
CORTEXM_SysTick |
How to use the default SysTick configuration with a 1 ms timebase to toggle LEDs. | X | - | - | X | X | - | - | - | X | - | - | X | - | - | - | X | - | ||
DAC |
DAC_SignalsGeneration |
How to use the DAC peripheral to generate several signals using the DMA controller. | X | - | - | - | X | X | - | - | X | - | - | X | - | - | - | X | - | |
DAC_SimpleConversion |
How to use the DAC peripheral to do a simple conversion. | X | - | - | - | - | - | - | - | X | - | - | X | - | - | - | X | - | ||
DCMI |
DCMI_CaptureMode |
How to use the DCMI to interface with a camera module to continuously capture RGB565 images, crop them from size 320x240 to 240x240 then display the video stream on the LCD. | - | - | - | - | - | - | - | - | - | - | X | - | - | - | - | - | - | |
DCMI_Preview |
How to use the DCMI to interface with a camera module to continuously capture RGB565 images, crop them from size 320x240 to 240x240 then display the video stream on the LCD. | - | - | - | - | - | - | - | - | - | - | X | - | - | - | - | - | - | ||
DCMI_SnapshotMode |
How to use the DCMI to interface with a camera module to capture a single RGB565 image and crop it from size 320x240 to 240x240, and once a full frame camera image is captured, display it on a 240x240 LCD in RGB565 format. | - | - | - | - | - | - | - | - | - | - | X | - | - | - | - | - | - | ||
DFSDM |
DFSDM_AudioRecord |
How to use the DFSDM HAL API to perform stereo audio recording. This example uses two MP34DT01 digital microphones mounted on the board. | X | - | - | - | - | X | - | - | - | - | X | - | - | X | X | - | - | |
DFSDM_Thermometer |
How to use the DFSDM HAL API to perform temperature measurements. This example uses the PT100 (thermistor) and STPMS2 (sigma-delta modulator) mounted on the board. The STPMS2 allows voltage and current values to be obtained from the PT100. The temperature value is thus deduced. | X | - | - | - | - | - | - | - | - | - | - | - | - | - | - | - | - | ||
DMA |
DMAMUX_RequestGen |
How to use the DMA with the DMAMUX request generator to generate DMA transfer requests upon an External line 13 rising edge signal. | - | - | - | - | - | - | X | - | - | - | - | - | - | - | - | - | - | |
DMAMUX_SYNC |
How to use the DMA with the DMAMUX to synchronize a transfer with the LPTIM1 output signal. LPUART1 is used in DMA synchronized mode to send a countdown from 10 to 00, with a period of 2 seconds. | - | - | - | - | - | - | 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 | ||
DMA2D |
DMA2D_MemToMemWithBlending |
How to configure the DMA2D peripheral in Memory-to-memory with blending transfer mode. | - | - | - | - | - | - | - | - | - | - | X | - | - | - | - | - | - | |
DMA2D_MemToMemWithLCD |
How to configure DMA2D peripheral in Memory-to-memory transfer mode and display the result on the LCD. | - | - | - | - | - | - | - | - | - | - | X | - | - | - | - | - | - | ||
DMA2D_MemToMemWithPFC |
How to configure the DMA2D peripheral in Memory-to-memory transfer mode with pixel format conversion (PFC) mode. | - | - | - | - | - | - | - | - | - | - | X | - | - | - | - | - | - | ||
DMA2D_MemoryToMemory |
How to configure the DMA2D peripheral in Memory-to-memory transfer mode. | - | - | - | - | - | X | - | - | - | - | X | - | - | - | - | - | - | ||
DMA2D_RegToMemWithLCD |
How to configure DMA2D peripheral in Register-to-memory transfer mode and display the result on the LCD. | - | - | - | - | - | - | - | - | - | - | X | - | - | - | - | - | - | ||
DSI |
DSI_CmdMode_SingleBuffer |
How to use the embedded LCD DSI controller (using the LTDC and DSI Host IPs) to drive the round LCD mounted on-board. | - | - | - | - | - | X | - | - | - | - | - | - | - | X | - | - | - | |
DSI_ULPM_Data |
How to use the embedded LCD DSI controller (using the LTDC and DSI Host IPs) to drive the KoD LCD mounted on-board and manage entry and exit in DSI ULPM mode on the data lane only. In this mode, the DSI PHY state machine enters a low-power state on the data lane, allowing some power saving when the LCD does not need to display. When the display is needed again, the DSI ULPM on the data lane is exited, and the display operates as before. | - | - | - | - | - | X | - | - | - | - | - | - | - | X | - | - | - | ||
DSI_ULPM_DataClock |
How to use the embedded LCD DSI controller (using the LTDC and DSI Host IPs) to drive the KoD LCD mounted on-board and manage entry and exit in DSI ULPM mode on data and clock lanes. | - | - | - | - | - | X | - | - | - | - | - | - | - | X | - | - | - | ||
FIREWALL |
FIREWALL_VolatileData_Executable |
How to use the Firewall IP to protect a volatile data segment and to define it as executable. | - | - | - | - | - | - | - | - | X | - | - | X | - | - | - | - | - | |
| How to use the Firewall IP to protect a code segment as well as volatile and non-volatile data segments. | - | - | - | - | - | - | - | - | X | - | - | X | - | - | - | - | - | |||
FLASH |
FLASH_DualBoot |
Guide through the configuration steps to program internal Flash memory bank 1 and bank 2, and to swap between both of them by mean of the FLASH HAL API. | X | - | - | - | - | - | - | - | X | - | X | X | - | - | X | - | - | |
FLASH_EraseProgram |
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 | ||
FLASH_FastProgram |
How to configure and use the FLASH HAL API to erase and fast program the internal Flash memory. | X | - | - | - | - | X | X | - | X | - | X | X | - | X | X | X | - | ||
FLASH_WriteProtection |
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 | - | X | X | - | - | X | X | X | ||
FMC |
FMC_NOR |
How to configure the FMC controller to access the NOR memory. | X | - | - | - | - | X | - | - | - | - | - | - | - | - | - | - | - | |
FMC_SRAM |
How to configure the FMC controller to access the SRAM memory. | X | - | - | - | - | X | - | - | - | - | X | - | - | - | - | - | - | ||
GPIO |
GPIO_EXTI |
How to configure external interrupt lines. | 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 | ||
HAL |
HAL_RegisterCallbacks_TIM |
Register a callback function called every second based on TIM peripheral configuration to generate a timebase of one second with the corresponding interrupt request. | - | - | - | - | - | - | - | - | X | - | - | - | - | - | - | - | - | |
HAL_TimeBase_TIM |
How to customize HAL using a general-purpose timer as main source of time base instead of Systick. | 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 | - | - | - | - | - | |
HASH_HMAC_SHA224SHA1_DMA_Suspension |
How to suspend the HMAC digest computation when data are fed to the HASH unit with DMA. | - | - | - | - | - | - | X | - | - | - | - | - | - | - | - | - | - | ||
HASH_HMAC_SHA224SHA256_MultiBuffer_DMA |
How to handle text messages larger than the maximum DMA transfer length. The input data are split into several buffers with sizes within the DMA limit, then fed successively to the HASH peripheral. | - | - | - | - | - | - | X | - | - | - | - | X | - | - | - | - | - | ||
HASH_HMAC_SHA256MD5_IT_Suspension |
How to suspend the HMAC digest computation when data are fed in interrupt mode. | - | - | - | - | - | - | X | - | - | - | - | X | - | - | - | - | - | ||
HASH_SHA1MD5 |
How to use the HASH peripheral to hash data with SHA-1 and MD5 algorithms. | - | - | - | - | - | - | 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 | - | - | - | - | - | ||
HASH_SHA1SHA224_IT_Suspension |
How to suspend the HASH peripheral when data are fed in interrupt mode. | - | - | - | - | - | - | X | - | - | - | - | X | - | - | - | - | - | ||
HASH_SHA224SHA256_DMA |
How to use the HASH peripheral to hash data with SHA224 and SHA256 algorithms. | - | - | - | - | - | - | X | - | - | - | - | X | - | - | - | - | - | ||
HASH_SHA256MD5_DMA_Suspension |
How to suspend the HASH peripheral when data are fed to the HASH unit with DMA. | - | - | - | - | - | - | X | - | - | - | - | - | - | - | - | - | - | ||
I2C |
I2C_EEPROM |
How to handle I2C data buffer transmission/reception with DMA. In the example, the device communicates with an I2C EEPROM memory. | X | - | - | - | - | X | - | - | - | - | - | - | - | - | - | - | - | |
I2C_IOExpander |
How to handle I2C data communication with the I/O expander device mounted on the evaluation board. | X | - | - | - | - | - | - | - | - | - | - | - | - | - | - | - | - | ||
I2C_TwoBoards_AdvComIT |
How to handle I2C data buffer transmission/reception between two boards, using an interrupt. | 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 | - | ||
I2C_TwoBoards_ComIT |
How to handle I2C data buffer transmission/reception between two boards, using an interrupt. | 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 | - | ||
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 | - | - | - | 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 | - | ||
I2C_WakeUpFromStop |
How to handle I2C data buffer transmission/reception between two boards, using an interrupt when the device is in Stop mode. | X | - | - | - | X | - | - | - | X | - | - | X | - | - | - | - | - | ||
I2C_WakeUpFromStop2 |
How to handle I2C data buffer transmission/reception between two boards, using an interrupt when the device is in Stop 2 mode. | X | - | - | X | - | - | - | - | X | - | - | X | - | - | - | X | - | ||
IWDG |
IWDG_Reset |
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 | - | |
IWDG_WindowMode |
How to periodically update 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 | - | ||
LCD |
LCD_Blink_Frequency |
How to use the embedded LCD glass controller and how to set the LCD blink mode and blinking frequency. | X | - | - | - | - | - | - | - | - | - | - | - | - | - | - | - | - | |
LCD_SegmentsDrive |
How to use the embedded LCD glass controller to drive the on-board LCD glass by Pacific Display Devices. | X | - | - | - | - | - | - | - | - | - | - | - | - | - | - | - | - | ||
LPTIM |
LPTIM_PWMExternalClock |
How to configure and use, through the HAL LPTIM API, the LPTIM peripheral using an external counter clock, to generate a PWM signal at the lowest power consumption. | X | - | - | - | - | X | - | - | X | - | - | X | - | - | - | X | - | |
LPTIM_PWM_LSE |
How to configure and use, through the HAL LPTIM API, the LPTIM peripheral using LSE as counter clock, to generate a PWM signal, in a low-power mode. | X | - | - | - | - | X | - | - | - | - | - | - | - | - | - | X | - | ||
LPTIM_PulseCounter |
How to configure and use, through the LPTIM HAL API, the LPTIM peripheral to count pulses. | X | - | - | - | X | X | - | - | X | - | - | X | - | - | - | X | - | ||
LPTIM_RepetitionCounter |
How to configure and use LPTIM repetition counter to update the autoreload counter upon an update event. | - | - | - | X | - | - | - | - | - | - | - | - | - | - | - | - | - | ||
LPTIM_Timeout |
How to implement, through the HAL LPTIM API, a timeout with the LPTIMER peripheral, to wake up the system from a low-power mode. | X | - | - | X | X | X | - | - | - | - | - | X | - | X | - | X | - | ||
LPUART |
LPUART_TwoBoards_ComIT |
LPUART transmission (transmit/receive) in Interrupt mode between two boards. | - | - | - | - | - | - | - | - | - | - | - | X | - | - | - | - | - | |
LPUART_WakeUpFromStop |
Configuration of an LPUART to wake up the MCU from Stop mode when a given stimulus is received. | - | - | - | - | - | - | - | - | - | - | - | X | - | - | - | - | - | ||
LTDC |
LTDC_ColorKeying |
How to enable and use the LTDC color keying functionality. | - | - | - | - | - | X | - | - | - | - | - | - | - | - | - | - | - | |
LTDC_Display_1Layer |
How to configure the LTDC peripheral to display a 480x272 RGB565 (16 bits/pixel) 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 | - | - | - | - | - | - | - | - | - | - | - | ||
OPAMP |
OPAMP_PGA |
How to use the built-in PGA mode (OPAMP programmable gain). | X | - | - | - | X | X | - | - | X | - | - | X | - | - | - | - | - | |
OPAMP_STANDALONE |
How to configure the OPAMP peripheral in standalone mode. The gain in this mode can be set externally (external gain setting mode). | X | - | - | - | X | - | - | - | - | - | - | X | - | - | - | - | - | ||
OSPI |
OSPI_NOR_ExecuteInPlace |
How to execute code from OSPI memory after code loading. | - | - | - | - | - | X | - | - | - | - | - | - | - | - | - | - | - | |
OSPI_NOR_ExecuteInPlace_DTR |
How to execute code from OSPI memory after code loading. | - | - | - | - | - | X | - | - | - | - | - | - | - | - | - | - | - | ||
OSPI_NOR_MemoryMapped |
How to use a OSPI NOR memory in memory-mapped mode. | - | - | - | - | - | X | - | - | - | - | - | - | - | X | - | - | - | ||
OSPI_NOR_MemoryMapped_DTR |
How to use a OSPI NOR memory in memory-mapped mode. | - | - | - | - | - | X | - | - | - | - | - | - | - | X | - | - | - | ||
OSPI_NOR_ReadWrite_DMA |
How to use a OSPI NOR memory in DMA mode. | - | - | - | - | - | X | - | - | - | - | - | - | - | X | - | - | - | ||
OSPI_NOR_ReadWrite_DMA_DTR |
How to use a OSPI NOR memory in DMA mode. | - | - | - | - | - | X | - | - | - | - | - | - | - | X | - | - | - | ||
OSPI_RAM_ExecuteInPlace |
How to execute code from OSPI memory after code loading. | - | - | - | - | - | X | - | - | - | - | - | - | - | - | - | - | - | ||
OSPI_RAM_MemoryMapped |
How to use a OSPI HyperRAM memory in memory-mapped mode. | - | - | - | - | - | X | - | - | - | - | - | - | - | - | - | - | - | ||
OSPI_RAM_ReadWrite_DMA |
How to use a OSPI HyperRAM memory in DMA mode. | - | - | - | - | - | X | - | - | - | - | - | - | - | - | - | - | - | ||
PWR |
PWR_LPRUN |
How to enter and exit the Low-power run mode. | - | - | - | - | X | - | X | - | X | - | - | X | - | - | - | X | X | |
PWR_LPRUN_SRAM1 |
How to enter and exit the Low-power run mode. | - | - | - | - | X | - | X | - | X | - | - | X | - | - | - | X | - | ||
PWR_LPSLEEP |
How to enter the Low-power sleep mode and wake up from this mode by using an interrupt. | - | - | - | - | X | - | X | - | X | - | - | X | - | - | - | X | X | ||
PWR_ModesSelection |
How to configure the system to measure the current consumption in different low-power modes. | - | - | - | - | X | - | X | - | X | - | - | X | - | - | - | X | - | ||
PWR_RUN_SMPS |
How to use SMPS in Run mode and access the power consumption gain obtained when the SMPS feature is used. | - | X | X | X | - | - | - | X | - | X | - | - | - | - | - | - | - | ||
PWR_SHUTDOWN |
How to enter the Shutdown mode and wake up from this mode by using an external reset or the WKUP pin. | - | - | - | - | X | - | X | - | X | - | - | X | - | - | - | X | X | ||
PWR_SLEEP |
How to enter the Sleep mode and wake up from this mode by using an interrupt. | - | - | - | - | X | - | X | - | X | - | - | X | - | - | - | 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 | ||
PWR_STANDBY_RTC |
How to enter the Standby mode and wake-up from this mode by using an external reset or the RTC wakeup timer. | - | - | - | - | X | - | X | - | X | - | - | X | - | - | - | X | X | ||
PWR_STANDBY_SMPS |
How to enter SMPS Standby mode and wake up from this mode using the wake-up pin. | - | X | X | X | - | - | - | X | - | X | - | - | - | - | - | - | - | ||
PWR_STOP0_SMPS |
How to enter Stop 0 mode with or without SMPS enabled and to wake up from this mode using an interrupt. | - | X | X | X | - | - | - | X | - | X | - | - | - | - | - | - | - | ||
PWR_STOP1 |
How to enter the Stop 1 mode and wake up from this mode by using an interrupt. | - | - | - | - | X | - | X | - | X | - | - | X | - | - | - | X | X | ||
PWR_STOP1_RTC |
How to enter the Stop 1 mode and wake up from this mode by using an interrupt from RTC wakeup timer. | - | - | - | - | X | - | X | - | X | - | - | X | - | - | - | X | X | ||
PWR_STOP2 |
How to enter the Stop 2 mode and wake up from this mode by using external reset or wakeup interrupt. | - | - | - | - | X | - | X | - | X | - | - | X | - | - | - | X | X | ||
PWR_STOP2_RTC |
How to enter the Stop 2 mode and wake-up from this mode using an external reset or RTC wakeup timer. | - | - | - | - | X | - | X | - | X | - | - | X | - | - | - | X | X | ||
QSPI |
QSPI_ExecuteInPlace |
How to execute code from QSPI memory after code loading. | 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 | - | - | ||
QSPI_ReadWrite_DMA |
How to use a QSPI memory in DMA mode. | X | - | - | - | - | - | - | - | - | - | X | - | - | - | X | - | - | ||
QSPI_ReadWrite_IT |
How to use a QSPI memory in interrupt mode. | X | - | - | - | - | - | - | - | - | - | X | - | - | - | X | - | - | ||
RCC |
RCC_CRS_Synchronization_IT |
Configuration of the clock recovery service (CRS) in Interrupt mode, using the RCC HAL API. | - | - | - | - | X | - | - | - | - | - | - | X | - | - | - | X | X | |
RCC_CRS_Synchronization_Polling |
Configuration of the clock recovery service (CRS) in Polling mode, using the RCC HAL API. | - | - | - | - | X | - | - | - | - | - | - | X | - | - | - | X | X | ||
RCC_ClockConfig |
Configuration of the system clock (SYSCLK) and modification of the clock settings in Run mode, using the RCC HAL API. | X | - | - | X | - | X | X | - | X | - | - | X | - | X | X | X | - | ||
RCC_LSEConfig |
Enabling/disabling at run time the propagation of the low-speed external(LSE) RC oscillator (about 32 KHz) to peripherals other than RTC, using the RCC HAL API. | - | - | - | X | - | - | - | - | - | - | - | - | - | - | - | - | - | ||
RCC_LSIConfig |
Enabling/disabling of the low-speed internal (LSI) RC oscillator (about 32 KHz) at run time, using the RCC HAL API. | - | - | - | 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 | - | |
RNG_MultiRNG_IT |
Configuration of the RNG using the HAL API. This example uses RNG interrupts to generate 32-bit long random numbers. | X | - | - | X | X | X | X | - | - | - | - | X | - | - | - | X | - | ||
RTC |
RTC_Alarm |
Configuration and generation of an RTC alarm using the RTC HAL API. | X | - | - | X | X | X | X | - | X | - | X | - | - | - | - | X | - | |
RTC_Calendar |
Configuration of the calendar using the RTC HAL API. | X | - | - | X | - | X | - | - | - | - | - | - | - | - | - | X | - | ||
RTC_InternalTimeStamp |
Demonstration the internal timestamp feature using the RTC HAL API. | X | - | - | - | - | - | - | - | - | - | - | - | - | - | - | - | - | ||
RTC_LSI |
Use of the LSI clock source autocalibration to get a precise RTC clock. | X | - | - | X | X | X | X | - | X | - | - | X | - | - | - | X | - | ||
RTC_LowPower_STANDBY |
How to enter STANDBY mode and wake up from this mode using the RTC alarm event. | - | - | - | X | - | - | - | - | - | - | - | - | - | - | - | X | - | ||
RTC_Tamper |
Configuration of the RTC HAL API to write/read data to/from RTC Backup registers. | X | - | - | X | - | X | X | - | X | - | - | X | - | - | - | X | - | ||
RTC_TimeStamp |
Configuration of the RTC HAL API to demonstrate the timestamp feature. | X | - | - | X | - | X | X | - | X | - | - | X | - | X | - | X | - | ||
SAI |
SAI_AudioPlay |
Use of the SAI HAL API to play an audio file in DMA circular mode and handle the buffer update. | X | - | - | - | - | X | - | - | - | - | - | - | - | X | X | - | - | |
SMARTCARD |
SMARTCARD_T0 |
Firmware smartcard interface based on USART. The main purpose of this firmware example is to provide resources that ease the development of applications using the USART in Smartcard mode. | X | - | - | - | - | - | - | - | - | - | - | - | - | - | - | - | - | |
SPI |
SPI_FullDuplex_ComDMA |
Data buffer transmission/reception between two boards via SPI using DMA. | - | - | - | - | X | - | X | - | X | - | - | X | - | - | - | X | - | |
SPI_FullDuplex_ComIT |
Data buffer transmission/reception between two boards via SPI using Interrupt mode. | - | - | - | - | X | - | X | - | X | - | - | X | - | - | - | X | - | ||
SPI_FullDuplex_ComPolling |
Data buffer transmission/reception between two boards via SPI using Polling mode. | - | - | - | - | X | - | X | - | X | - | - | X | - | - | - | X | - | ||
SPI_HalfDuplex_ComPolling |
Data buffer half-duplex transmission/reception between two boards via SPI using Polling mode. | - | - | - | - | - | - | - | - | X | - | - | X | - | - | - | X | - | ||
SWPMI |
SWPMI_Session |
Configuration of the SWPMI peripheral to open a communication session with a SWP compliant card in no software buffer mode. | X | - | - | - | - | - | - | - | - | - | - | - | - | - | - | - | - | |
TIM |
TIM_DMA |
Use of the DMA with TIMER Update request to transfer data from memory to TIMER Capture Compare Register 3 (TIMx_CCR3). | X | - | - | - | X | - | - | - | X | - | - | X | - | - | - | X | - | |
TIM_DMABurst |
How to update the TIMER channel 1 period and duty cycle using the TIMER DMA burst feature. | X | - | - | - | X | - | - | - | X | - | - | X | - | - | - | X | - | ||
TIM_ExtTriggerSynchro |
Synchronization of TIM peripherals in Cascade mode with an external trigger. | X | - | - | - | - | - | - | - | X | - | - | X | - | - | - | X | - | ||
TIM_InputCapture |
How to use the TIM peripheral to measure an external signal frequency. | X | - | - | - | X | - | - | - | X | - | - | X | - | - | - | X | - | ||
TIM_OCActive |
Configuration of the TIM peripheral in Output Compare Active mode (when the counter matches the capture/compare register, the corresponding output pin is set to its active state). | X | - | - | - | X | - | - | - | X | - | - | X | - | - | - | X | - | ||
TIM_OCInactive |
Configuration of the TIM peripheral in Output Compare Inactive mode with the corresponding Interrupt requests for each channel. | X | - | - | - | X | - | - | - | X | - | - | X | - | - | - | X | - | ||
TIM_OCToggle |
Configuration of the TIM peripheral to generate four different signals at four different frequencies. | X | - | - | - | X | - | - | - | X | - | - | X | - | - | - | X | - | ||
TIM_OnePulse |
Use of the TIM peripheral to generate a single pulse when an external signal rising edge is received on the timer input pin. | X | - | - | - | X | - | - | - | X | - | - | X | - | - | - | X | - | ||
TIM_PWMInput |
How to use the TIM peripheral to measure the frequency and duty cycle of an external signal. | X | - | - | - | X | - | - | - | X | - | - | X | - | - | - | X | - | ||
TIM_PWMOutput |
Configuration of the TIM peripheral in PWM (pulse width modulation) mode. | X | - | - | - | X | X | - | - | X | - | - | X | - | - | - | X | - | ||
TIM_TimeBase |
Configuration of the TIM peripheral to generate a timebase of one second with the corresponding interrupt request. | X | - | - | - | X | - | - | - | X | - | - | X | - | - | - | X | - | ||
TSC |
TSC_BasicAcquisition_Interrupt |
Use of he TSC to perform continuous acquisitions of one channel in Interrupt mode. | X | - | - | - | - | - | - | - | - | - | - | - | - | - | - | - | - | |
UART |
LPUART_WakeUpFromStop |
Configuration of an LPUART to wake up the MCU from Stop mode when a given stimulus is received. | - | - | - | - | - | X | - | - | - | - | - | - | - | - | - | - | - | |
UART_HyperTerminal_DMA |
UART transmission (transmit/receive) in DMA mode between a board and an HyperTerminal PC application. | X | - | - | - | - | - | - | - | - | - | - | - | - | - | - | - | - | ||
UART_LowPower_HyperTerminal_DMA |
LPUART transmission (transmit/receive) in DMA mode between a board and an HyperTerminal PC application. | - | - | - | - | - | X | - | - | - | - | - | - | - | - | - | - | - | ||
UART_Printf |
Re-routing of the C library printf function to the UART. | X | - | - | - | - | X | - | - | - | - | - | - | - | - | - | - | - | ||
UART_TwoBoards_ComDMA |
UART transmission (transmit/receive) in DMA mode between two boards. | - | - | - | - | X | - | - | - | X | - | - | X | - | - | - | X | - | ||
UART_TwoBoards_ComIT |
UART transmission (transmit/receive) in Interrupt mode between two boards. | - | - | - | - | X | - | - | - | X | - | - | X | - | - | - | X | - | ||
UART_TwoBoards_ComPolling |
UART transmission (transmit/receive) in Polling mode between two boards. | - | - | - | - | X | - | - | - | X | - | - | X | - | - | - | X | - | ||
UART_WakeUpFromStop |
Configuration of an UART to wake up the MCU from Stop 1 mode when a given stimulus is received. | - | - | - | - | X | - | - | - | X | - | - | X | - | - | - | X | - | ||
WWDG |
WWDG_Example |
Configuration of the HAL API to periodically update the WWDG counter and simulate a software fault that generates an MCU WWDG reset when a predefined time period has elapsed. | X | - | - | X | - | X | - | - | X | - | - | X | - | - | - | X | - | |
| Total number of examples: 636 | 87 | 3 | 3 | 43 | 62 | 54 | 52 | 3 | 70 | 3 | 23 | 97 | 1 | 16 | 17 | 82 | 20 | |||
Examples_LL |
ADC |
ADC_AnalogWatchdog |
How to use an ADC peripheral with an ADC analog watchdog to monitor a channel and detect when the corresponding conversion data is outside the window thresholds. | - | - | - | - | - | - | - | - | X | - | - | X | - | - | - | - | - |
ADC_ContinuousConversion_TriggerSW |
How to use an ADC peripheral to perform continuous ADC conversions on a channel, from a software start. | - | - | - | - | - | - | - | - | X | - | - | X | - | - | - | - | - | ||
ADC_ContinuousConversion_TriggerSW_Init |
How to use an ADC peripheral to perform continuous ADC conversions on a channel, from a software start. | - | - | - | - | - | - | - | - | X | - | - | X | - | - | - | - | - | ||
ADC_ContinuousConversion_TriggerSW_LowPower |
How to use an ADC peripheral with ADC low-power features. | - | - | - | - | - | - | - | - | X | - | - | X | - | - | - | - | - | ||
ADC_GroupsRegularInjected |
How to use an ADC peripheral with both ADC groups (regular and injected) in their intended use cases. | - | - | - | - | - | - | - | - | X | - | - | X | - | - | - | - | - | ||
ADC_MultiChannelSingleConversion |
How to use an ADC peripheral to convert several channels. ADC conversions are performed successively in a scan sequence. | - | - | - | - | - | - | - | - | X | - | - | X | - | - | - | - | - | ||
ADC_MultimodeDualInterleaved |
How to use several ADC peripherals in multimode and interleaved mode. | - | - | - | - | - | - | - | - | X | - | - | X | - | - | - | - | - | ||
ADC_Oversampling |
How to use an ADC peripheral with ADC oversampling. | - | - | - | - | - | - | - | - | X | - | - | X | - | - | - | - | - | ||
ADC_SingleConversion_Stop2_LP |
How to use an ADC peripheral with a system configuration optimized for power consumption, to perform an acquisition at low frequency (between 1Hz and 1kHz). | - | - | - | - | - | - | - | - | - | - | - | - | - | - | - | - | X | ||
ADC_SingleConversion_TriggerSW |
How to use an ADC peripheral to perform a single ADC conversion on a channel at each software start. This example uses the polling programming model (for interrupt or DMA programming models, refer to other examples). This example is based on the STM32L4xx ADC LL API. The peripheral initialization is done using LL unitary service functions for optimization purpose (performance and size). | - | - | - | - | - | - | - | - | X | - | - | X | - | - | - | - | - | ||
ADC_SingleConversion_TriggerSW_DMA |
How to use an ADC peripheral to perform a single ADC conversion on a channel, at each software start. This example uses the DMA programming model (for polling or interrupt programming models, refer to other examples). This example is based on the STM32L4xx ADC LL API. The peripheral initialization is done using LL unitary service functions for optimization purpose (performance and size). | - | - | - | - | - | - | - | - | X | - | - | X | - | - | - | - | - | ||
ADC_SingleConversion_TriggerSW_IT |
How to use an ADC peripheral to perform a single ADC conversion on a channel, at each software start. This example uses the interrupt programming model (for polling or DMA programming models, refer to other examples). This example is based on the STM32L4xx ADC LL API. The peripheral initialization is done using LL unitary service functions for optimization purpose (performance and size). | - | - | - | - | - | - | - | - | X | - | - | X | - | - | - | - | - | ||
ADC_SingleConversion_TriggerTimer_DMA |
How to use an ADC peripheral to perform a single ADC conversion on a channel at each trigger event from a timer. Converted data are indefinitely transferred by DMA into a table (circular mode). This example is based on the STM32L4xx ADC LL API. The peripheral initialization is done using LL unitary service functions for optimization purpose (performance and size). | - | - | - | - | - | - | - | - | X | - | - | X | - | - | - | - | - | ||
ADC_SingleConversion_TriggerTimer_DMA_LP |
How to use an ADC peripheral with a system configuration optimized for power consumption, to perform an acquisition at medium frequency (between 10 Hz and 100 kHz). | - | - | - | - | - | - | - | - | - | - | - | - | - | - | - | - | X | ||
ADC_TemperatureSensor |
How to use an ADC peripheral to perform a single ADC conversion on the internal temperature sensor and calculate the temperature in degrees Celsius. | - | - | - | - | - | - | - | - | X | - | - | X | - | - | - | - | - | ||
COMP |
COMP_CompareGpioVsVrefInt_IT |
How to use a comparator peripheral to compare a voltage level applied on a GPIO pin to the internal voltage reference (VREFINT), in interrupt mode. This example is based on the STM32L4xx COMP LL API. The peripheral initialization is done using LL unitary service functions for optimization purpose (performance and size). | - | - | - | - | - | - | - | - | X | - | - | X | - | - | - | - | - | |
COMP_CompareGpioVsVrefInt_IT_Init |
How to use a comparator peripheral to compare a voltage level applied on a GPIO pin to the the internal voltage reference (VREFINT), in interrupt mode. This example is based on the STM32L4xx COMP LL API. The peripheral initialization is done using LL initialization function to demonstrate LL init usage. | - | - | - | - | - | - | - | - | X | - | - | X | - | - | - | - | - | ||
COMP_CompareGpioVsVrefInt_OutputGpio |
How to use a comparator peripheral to compare a voltage level applied on a GPIO pin to the internal voltage reference (VREFINT). | - | - | - | - | - | - | - | - | X | - | - | X | - | - | - | - | - | ||
COMP_CompareGpioVsVrefInt_Window_IT |
How to use a pair of comparator peripherals to compare a voltage level applied on a GPIO pin to two thresholds: the internal voltage reference (VREFINT) and a fraction of the internal voltage reference (VREFINT/2), in interrupt mode. This example is based on the STM32L4xx COMP LL API. The peripheral initialization is done using LL unitary service functions for optimization purpose (performance and size). | - | - | - | - | - | - | - | - | X | - | - | X | - | - | - | - | - | ||
CORTEX |
CORTEX_MPU |
Presentation of the MPU feature. This example configures a memory area as privileged read-only, and attempts to perform read and write operations in different modes. | - | - | - | X | - | - | - | - | X | - | - | X | - | - | - | - | - | |
CRC |
CRC_CalculateAndCheck |
How to configure the CRC calculation unit to compute a CRC code for a given data buffer, based on a fixed generator polynomial (default value 0x4C11DB7). The peripheral initialization is done using LL unitary service functions for optimization purposes (performance and size). | - | - | - | X | - | - | - | - | X | - | - | X | - | - | - | - | X | |
CRC_UserDefinedPolynomial |
How to configure and use the CRC calculation unit to compute an 8-bit CRC code for a given data buffer, based on a user-defined generating polynomial. The peripheral initialization is done using LL unitary service functions for optimization purposes (performance and size). | - | - | - | X | - | - | - | - | X | - | - | X | - | - | - | - | X | ||
CRS |
CRS_Synchronization_IT |
How to configure the clock recovery service in IT mode through the STM32L4xx CRS LL API. The peripheral initialization uses LL unitary service functions for optimization purposes (performance and size). | - | - | - | - | - | - | - | - | - | - | - | X | - | - | - | - | - | |
CRS_Synchronization_Polling |
How to configure the clock recovery service in polling mode through the STM32L4xx CRS LL API. The peripheral initialization uses LL unitary service functions for optimization purposes (performance and size). | - | - | - | - | - | - | - | - | - | - | - | X | - | - | - | - | - | ||
DAC |
DAC_GenerateConstantSignal_TriggerSW |
How to use the DAC peripheral to generate a constant voltage signal. This example is based on the STM32L4xx DAC LL API. | - | - | - | - | - | - | - | - | X | - | - | X | - | - | - | - | - | |
DAC_GenerateConstantSignal_TriggerSW_LP |
How to use the DAC peripheral to generate a constant voltage signal with the DAC low-power feature sample-and-hold. To be effective, a capacitor must be connected to the DAC channel output and the sample-and-hold timings must be tuned depending on the capacitor value. This example is based on the STM32L4xx DAC LL API. The peripheral initialization is done using LL unitary service functions for optimization purpose (performance and size). | - | - | - | - | - | - | - | - | X | - | - | X | - | - | - | - | - | ||
DAC_GenerateWaveform_TriggerHW |
How to use the DAC peripheral to generate a voltage waveform from a digital data stream transfered by DMA. This example is based on the STM32L4xx DAC LL API. The peripheral initialization is done using LL unitary service functions for optimization purpose (performance and size). | - | - | - | - | - | - | - | - | X | - | - | X | - | - | - | - | - | ||
DAC_GenerateWaveform_TriggerHW_Init |
How to use the DAC peripheral to generate a voltage waveform from a digital data stream transfered by DMA. This example is based on the STM32L4xx DAC LL API. The peripheral initialization is done using LL initialization function to demonstrate LL init usage. | - | - | - | - | - | - | - | - | X | - | - | X | - | - | - | - | - | ||
DMA |
DMA_CopyFromFlashToMemory |
How to use a DMA channel to transfer a word data buffer from Flash memory to embedded SRAM. The peripheral initialization uses LL unitary service functions for optimization purposes (performance and size).. | - | - | - | X | - | - | - | - | X | - | - | X | - | - | - | - | X | |
DMA_CopyFromFlashToMemory_Init |
How to use a DMA channel to transfer a word data buffer from Flash memory to embedded SRAM. The peripheral initialization uses LL initialization functions to demonstrate LL init usage. | - | - | - | - | - | - | - | - | X | - | - | X | - | - | - | - | - | ||
DMA2D |
DMA2D_MemoryToMemory |
How to configure the DMA2D peripheral in Memory-to-memory transfer mode. The example is based on the STM32L4xx DMA2D LL API. The peripheral initialization is done using LL unitary service functions for optimization purpose (performance and size). | - | - | - | - | - | - | - | - | - | - | X | - | - | - | - | - | - | |
EXTI |
EXTI_ToggleLedOnIT |
How to configure the $moduleName$ and use GPIOs to toggle the user LEDs available on the board when a user button is pressed. It is based on the STM32L4xx LL API. The peripheral initialization is done using LL unitary services functions for optimization purpose (performance and size). | - | - | - | - | - | - | - | - | X | - | - | X | - | - | - | - | - | |
EXTI_ToggleLedOnIT_Init |
How to configure the $moduleName$ and use GPIOs to toggle the user LEDs available on the board when a user button is pressed. This example is based on the STM32L4xx LL API. The peripheral initialization is done using LL initialization function to demonstrate LL init usage. | - | - | - | - | - | - | - | - | X | - | - | X | - | - | - | - | - | ||
GPIO |
GPIO_InfiniteLedToggling |
How to configure and use GPIOs to toggle the on-board user LEDs every 250 ms. This example is based on the STM32L4xx LL API. The peripheral initialization is done using LL unitary service functions for optimization purpose (performance and size). | - | - | - | - | - | - | - | - | X | - | - | X | - | - | - | - | X | |
GPIO_InfiniteLedToggling_Init |
How to configure and use GPIOs to toggle the on-board user LEDs every 250 ms. This example is based on the STM32L4xx LL API. The peripheral initialization is done using LL initialization function to demonstrate LL init usage. | - | - | - | - | - | - | - | - | X | - | - | X | - | - | - | - | X | ||
I2C |
I2C_OneBoard_AdvCommunication_DMAAndIT |
How to exchange data between an I2C master device in DMA mode and an I2C slave device in interrupt mode. The peripheral is initialized with LL unitary service functions to optimize for performance and size. | - | - | - | - | - | - | - | - | X | - | - | X | - | - | - | - | - | |
I2C_OneBoard_Communication_DMAAndIT |
How to transmit data bytes from an I2C master device using DMA mode to an I2C slave device using interrupt mode. The peripheral is initialized with LL unitary service functions to optimize for performance and size. | - | - | - | - | - | - | - | - | X | - | - | X | - | - | - | - | - | ||
I2C_OneBoard_Communication_IT |
How to handle the reception of one data byte from an I2C slave device by an I2C master device. Both devices operate in interrupt mode. The peripheral is initialized with LL unitary service functions to optimize for performance and size. | - | - | - | - | - | - | - | - | X | - | - | X | - | - | - | - | - | ||
I2C_OneBoard_Communication_IT_Init |
How to handle the reception of one data byte from an I2C slave device by an I2C master device. Both devices operate in interrupt mode. The peripheral is initialized with LL initialization function to demonstrate LL init usage. | - | - | - | - | - | - | - | - | X | - | - | X | - | - | - | - | - | ||
I2C_OneBoard_Communication_PollingAndIT |
How to transmit data bytes from an I2C master device using polling mode to an I2C slave device using interrupt mode. The peripheral is initialized with LL unitary service functions to optimize for performance and size. | - | - | - | - | - | - | - | - | X | - | - | X | - | - | - | - | - | ||
I2C_TwoBoards_MasterRx_SlaveTx_IT |
How to handle the reception of one data byte from an I2C slave device by an I2C master device. Both devices operate in interrupt mode. The peripheral is initialized with LL unitary service functions to optimize for performance and size. | - | - | - | - | - | - | - | - | X | - | - | X | - | - | - | - | - | ||
I2C_TwoBoards_MasterTx_SlaveRx |
How to transmit data bytes from an I2C master device using polling mode to an I2C slave device using interrupt mode. The peripheral is initialized with LL unitary service functions to optimize for performance and size. | - | - | - | - | - | - | - | - | X | - | - | X | - | - | - | - | - | ||
I2C_TwoBoards_MasterTx_SlaveRx_DMA |
How to transmit data bytes from an I2C master device using DMA mode to an I2C slave device using DMA mode. The peripheral is initialized with LL unitary service functions to optimize for performance and size. | - | - | - | - | - | - | - | - | X | - | - | X | - | - | - | - | - | ||
I2C_TwoBoards_WakeUpFromStop2_IT |
How to handle the reception of a data byte from an I2C slave device in Stop2 mode by an I2C master device, both using interrupt mode. The peripheral is initialized with LL unitary service functions to optimize for performance and size. | - | - | - | - | - | - | - | - | X | - | - | X | - | - | - | - | - | ||
IWDG |
IWDG_RefreshUntilUserEvent |
How to configure the IWDG peripheral to ensure periodical counter update and generate an MCU IWDG reset when a User push-button is pressed. The peripheral is initialized with LL unitary service functions to optimize for performance and size. | - | - | - | X | - | - | - | - | X | - | - | X | - | - | - | - | - | |
LPTIM |
LPTIM_PulseCounter |
How to use the LPTIM peripheral in counter mode to generate a PWM output signal and update its duty cycle. This example is based on the STM32L4xx LPTIM LL API. The peripheral initialization is done using LL unitary service functions for optimization purpose (performance and size). | - | - | - | - | - | - | - | - | X | - | - | X | - | - | - | - | - | |
LPTIM_PulseCounter_Init |
How to use the LPTIM peripheral in counter mode to generate a PWM output signal and update its duty cycle. This example is based on the STM32L4xx LPTIM LL API. The peripheral initialization is done using LL initialization function to demonstrate LL init usage. | - | - | - | - | - | - | - | - | X | - | - | X | - | - | - | - | - | ||
LPUART |
LPUART_WakeUpFromStop2 |
Configuration of GPIO and LPUART peripherals to allow characters received on LPUART_RX pin to wake up the MCU from low-power mode. This example is based on the LPUART LL API. The peripheral initialization uses LL unitary service functions for optimization purposes (performance and size). | - | - | - | - | - | - | - | - | X | - | - | X | - | - | - | - | - | |
LPUART_WakeUpFromStop2_Init |
Configuration of GPIO and LPUART peripherals to allow characters received on LPUART_RX pin to wake up the MCU from low-power mode. This example is based on the LPUART LL API. The peripheral initialization uses LL initialization function to demonstrate LL init usage. | - | - | - | - | - | - | - | - | X | - | - | X | - | - | - | - | - | ||
OPAMP |
OPAMP_PGA |
How to use the OPAMP peripheral in PGA mode (programmable gain amplifier). To test the OPAMP, a voltage waveform is generated by the DAC and feeds the OPAMP input. This example is based on the STM32L4xx OPAMP LL API. The peripheral initialization is done using LL unitary service functions for optimization purpose (performance and size). | - | - | - | - | - | - | - | - | X | - | - | X | - | - | - | - | - | |
OPAMP_PGA_Init |
How to use the OPAMP peripheral in PGA mode (programmable gain amplifier). To test the OPAMP, a voltage waveform is generated by the DAC and feeds the OPAMP input. This example is based on the STM32L4xx OPAMP LL API. The peripheral initialization is done using LL initialization function to demonstrate LL init usage. | - | - | - | - | - | - | - | - | X | - | - | X | - | - | - | - | - | ||
PWR |
PWR_EnterStandbyMode |
How to enter the Standby mode and wake up from this mode by using an external reset or a wakeup interrupt. | - | - | - | - | - | - | - | - | X | - | - | X | - | - | - | - | - | |
PWR_EnterStopMode |
How to enter Stop 2 mode. | - | - | - | - | - | - | - | - | X | - | - | X | - | - | - | - | - | ||
PWR_LPRunMode_SRAM1 |
How to execute code in Low-power run mode from SRAM1.. | - | - | - | - | - | - | - | - | X | - | - | X | - | - | - | - | - | ||
PWR_OptimizedRunMode |
How to increase/decrease frequency and VCORE and how to enter/exit the Low-power run mode. | - | - | - | - | - | - | - | - | X | - | - | X | - | - | - | - | - | ||
RCC |
RCC_HWAutoMSICalibration |
Use of the MSI clock source hardware autocalibration and LSE clock (PLL mode) to obtain a precise MSI clock. | - | - | - | X | - | - | - | - | X | - | - | X | - | - | - | - | - | |
RCC_OutputSystemClockOnMCO |
Configuration of MCO pin (PA8) to output the system clock. | - | - | - | X | - | - | - | - | X | - | - | X | - | - | - | - | - | ||
RCC_UseHSEasSystemClock |
Use of the RCC LL API to start the HSE and use it as system clock. | - | - | - | - | - | - | - | - | X | - | - | X | - | - | - | - | - | ||
RCC_UseHSI_PLLasSystemClock |
Modification of the PLL parameters in run time. | - | - | - | - | - | - | - | - | X | - | - | X | - | - | - | - | - | ||
RNG |
RNG_GenerateRandomNumbers |
Configuration of the RNG to generate 32-bit long random numbers. The peripheral initialization uses LL unitary service functions for optimization purposes (performance and size). | - | - | - | X | - | - | - | - | X | - | - | X | - | - | - | - | - | |
RNG_GenerateRandomNumbers_IT |
Configuration of the RNG to generate 32-bit long random numbers using interrupts. The peripheral initialization uses LL unitary service functions for optimization purposes (performance and size). | - | - | - | X | - | - | - | - | X | - | - | X | - | - | - | - | - | ||
RTC |
RTC_Alarm |
Configuration of the RTC LL API to configure and generate an alarm using the RTC peripheral. The peripheral initialization uses LL unitary service functions for optimization purposes (performance and size). | - | - | - | X | - | - | - | - | X | - | - | X | - | - | - | - | - | |
RTC_Alarm_Init |
Configuration of the RTC LL API to configure and generate an alarm using the RTC peripheral. The peripheral initialization uses the LL initialization function. | - | - | - | X | - | - | - | - | X | - | - | X | - | - | - | - | - | ||
RTC_Calendar |
Configuration of the LL API to set the RTC calendar. The peripheral initialization uses LL unitary service functions for optimization purposes (performance and size). | - | - | - | X | - | - | - | - | X | - | - | X | - | - | - | - | - | ||
RTC_ExitStandbyWithWakeUpTimer |
Configuration of the RTC to wake up from Standby mode using the RTC Wakeup timer. The peripheral initialization uses LL unitary service functions for optimization purposes (performance and size). | - | - | - | X | - | - | - | - | X | - | - | X | - | - | - | - | - | ||
RTC_ProgrammingTheWakeUpTimer |
Configuration of the RTC to use the WUT. The peripheral initialization uses LL unitary service functions for optimization purposes (performance and size). | - | - | - | - | - | - | - | - | - | - | - | X | - | - | - | - | - | ||
RTC_Tamper |
Configuration of the Tamper using the RTC LL API. The peripheral initialization uses LL unitary service functions for optimization purposes (performance and size). | - | - | - | X | - | - | - | - | X | - | - | X | - | - | - | - | - | ||
RTC_TimeStamp |
Configuration of the Timestamp using the RTC LL API. The peripheral initialization uses LL unitary service functions for optimization purposes (performance and size). | - | - | - | - | - | - | - | - | X | - | - | X | - | - | - | - | - | ||
SPI |
SPI_OneBoard_HalfDuplex_DMA |
Configuration of GPIO and SPI peripherals to transmit bytes from an SPI Master device to an SPI Slave device in DMA mode. This example is based on the STM32L4xx SPI LL API. The peripheral initialization uses LL unitary service functions for optimization purposes (performance and size). | - | - | - | - | - | - | - | - | X | - | - | X | - | - | - | - | - | |
SPI_OneBoard_HalfDuplex_DMA_Init |
Configuration of GPIO and SPI peripherals to transmit bytes from an SPI Master device to an SPI Slave device in DMA mode. This example is based on the STM32L4xx SPI LL API. The peripheral initialization uses the LL initialization function to demonstrate LL init usage. | - | - | - | - | - | - | - | - | X | - | - | X | - | - | - | - | - | ||
SPI_OneBoard_HalfDuplex_IT |
Configuration of GPIO and SPI peripherals to transmit bytes from an SPI Master device to an SPI Slave device in Interrupt mode. This example is based on the STM32L4xx SPI LL API. The peripheral initialization uses LL unitary service functions for optimization purposes (performance and size). | - | - | - | - | - | - | - | - | X | - | - | X | - | - | - | - | - | ||
SPI_TwoBoards_FullDuplex_DMA |
Data buffer transmission and reception via SPI using DMA mode. This example is based on the STM32L4xx SPI LL API. The peripheral initialization uses LL unitary service functions for optimization purposes (performance and size). | - | - | - | - | - | - | - | - | X | - | - | X | - | - | - | - | - | ||
SPI_TwoBoards_FullDuplex_IT |
Data buffer transmission and reception via SPI using Interrupt mode. This example is based on the STM32L4xx SPI LL API. The peripheral initialization uses LL unitary service functions for optimization purposes (performance and size). | - | - | - | - | - | - | - | - | X | - | - | X | - | - | - | - | - | ||
SWPMI |
SWPMI_Loopback_MultiSWBuffer |
Configuration of the SWPMI peripheral to start a communication using DMA multibuffers in Loopback mode. The peripheral initialization uses LL unitary service functions for optimization purposes (performance and size). | - | - | - | - | - | - | - | - | X | - | - | X | - | - | - | - | - | |
SWPMI_Loopback_MultiSWBuffer_Init |
Configuration of the SWPMI peripheral to start a communication using DMA multibuffers in Loopback mode. The peripheral initialization uses the LL initialization function to demonstrate LL init usage. | - | - | - | - | - | - | - | - | X | - | - | X | - | - | - | - | - | ||
SWPMI_Loopback_NoSWBuffer |
Configuration of the SWPMI peripheral to start a communication using No software buffer mode in Loopback mode. The peripheral initialization uses LL unitary service functions for optimization purposes (performance and size). | - | - | - | - | - | - | - | - | X | - | - | X | - | - | - | - | - | ||
TIM |
TIM_BreakAndDeadtime |
Configuration of the TIM peripheral to generate three center-aligned PWM and complementary PWM signals, insert a defined deadtime value, use the break feature, and lock the break and dead-time configuration. | - | - | - | - | - | - | - | - | X | - | - | X | - | - | - | - | - | |
TIM_DMA |
Use of the DMA with a timer update request to transfer data from memory to Timer Capture Compare Register 3 (TIMx_CCR3). This example is based on the STM32L4xx TIM LL API. The peripheral initialization uses LL unitary service functions for optimization purposes (performance and size). | - | - | - | - | - | - | - | - | X | - | - | X | - | - | - | - | - | ||
TIM_InputCapture |
Use of the TIM peripheral to measure a periodic signal frequency provided either by an external signal generator or by another timer instance. This example is based on the STM32L4xx TIM LL API. The peripheral initialization uses LL unitary service functions for optimization purposes (performance and size). | - | - | - | - | - | - | - | - | X | - | - | X | - | - | - | - | - | ||
TIM_OnePulse |
Configuration of 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 STM32L4xx TIM LL API. The peripheral initialization uses LL unitary service functions for optimization purposes (performance and size). | - | - | - | - | - | - | - | - | X | - | - | X | - | - | - | - | - | ||
TIM_OutputCompare |
Configuration of the TIM peripheral to generate an output waveform in different output compare modes. This example is based on the STM32L4xx TIM LL API. The peripheral initialization uses LL unitary service functions for optimization purposes (performance and size). | - | - | - | - | - | - | - | - | X | - | - | X | - | - | - | - | - | ||
TIM_PWMOutput |
Use of a timer peripheral to generate a PWM output signal and update the PWM duty cycle. This example is based on the STM32L4xx TIM LL API. The peripheral initialization uses LL unitary service functions for optimization purposes (performance and size). | - | - | - | - | - | - | - | - | X | - | - | X | - | - | - | - | - | ||
TIM_PWMOutput_Init |
Use of a timer peripheral to generate a PWM output signal and update the PWM duty cycle. This example is based on the STM32L4xx TIM LL API. The peripheral initialization uses LL initialization function to demonstrate LL init. | - | - | - | - | - | - | - | - | X | - | - | X | - | - | - | - | - | ||
TIM_TimeBase |
Configuration of the TIM peripheral to generate a timebase. This example is based on the STM32L4xx TIM LL API. The peripheral initialization uses LL unitary service functions for optimization purposes (performance and size). | - | - | - | - | - | - | - | - | X | - | - | X | - | - | - | - | - | ||
USART |
USART_Communication_Rx_IT |
Configuration of GPIO and USART peripherals to receive characters from an HyperTerminal (PC) in Asynchronous mode using an interrupt. The peripheral initialization uses LL unitary service functions for optimization purposes (performance and size). | - | - | - | - | - | - | - | - | X | - | - | X | - | - | - | - | - | |
USART_Communication_Rx_IT_Continuous |
Configuration of GPIO and USART peripherals to continuously receive characters from an HyperTerminal (PC) in Asynchronous mode using an interrupt. The peripheral initialization uses LL unitary service functions for optimization purposes (performance and size). | - | - | - | - | - | - | - | - | X | - | - | X | - | - | - | - | - | ||
USART_Communication_Rx_IT_Init |
Configuration of GPIO and USART peripherals to receive characters from an HyperTerminal (PC) in Asynchronous mode using an interrupt. The peripheral initialization uses the LL initialization function to demonstrate LL init. | - | - | - | - | - | - | - | - | X | - | - | X | - | - | - | - | - | ||
USART_Communication_Tx |
Configuration of GPIO and USART peripherals to send characters asynchronously to an HyperTerminal (PC) in Polling mode. If the transfer could not be complete within the allocated time, a timeout allows to exit from the sequence with timeout error. This example is based on STM32L4xx USART LL API. The peripheral initialization uses LL unitary service functions for optimization purpose (performance and size). | - | - | - | - | - | - | - | - | X | - | - | X | - | - | - | - | - | ||
USART_Communication_TxRx_DMA |
Configuration of GPIO and USART peripherals to send characters asynchronously to/from an HyperTerminal (PC) in DMA mode. | - | - | - | - | - | - | - | - | X | - | - | X | - | - | - | - | - | ||
USART_Communication_Tx_IT |
Configuration of GPIO and USART peripheral to send characters asynchronously to HyperTerminal (PC) in Interrupt mode. This example is based on the STM32L4xx USART LL API. The peripheral initialization uses LL unitary service functions for optimization purposes (performance and size). | - | - | - | - | - | - | - | - | X | - | - | X | - | - | - | - | - | ||
USART_HardwareFlowControl |
Configuration of GPIO and $COM_INSTANCE1_TYPE$ peripheral to receive characters asynchronously from an HyperTerminal (PC) in Interrupt mode with the Hardware Flow Control feature enabled. This example is based on STM32L4xx USART LL API. The peripheral initialization uses LL unitary service functions for optimization purposes (performance and size). | - | - | - | - | - | - | - | - | X | - | - | X | - | - | - | - | - | ||
USART_SyncCommunication_FullDuplex_DMA |
Configuration of GPIO, USART, DMA and SPI peripherals to transmit bytes between a USART and an SPI (in slave mode) in DMA mode. This example is based on the STM32L4xx USART LL API. The peripheral initialization uses LL unitary service functions for optimization purposes (performance and size). | - | - | - | - | - | - | - | - | X | - | - | X | - | - | - | - | - | ||
USART_SyncCommunication_FullDuplex_IT |
Configuration of GPIO, USART, DMA and SPI peripherals to transmit bytes between a USART and an SPI (in slave mode) in Interrupt mode. This example is based on the STM32L4xx USART LL API (the SPI uses the DMA to receive/transmit characters sent from/received by the USART). The peripheral initialization uses LL unitary service functions for optimization purposes (performance and size). | - | - | - | - | - | - | - | - | X | - | - | X | - | - | - | - | - | ||
USART_WakeUpFromStop1 |
Configuration of GPIO and STM32L4xx USART peripherals to receive characters on USART_RX pin and wake up the MCU from low-power mode. This example is based on the STM32L4xx USART LL API. The peripheral initialization uses LL unitary service functions for optimization purposes (performance and size). | - | - | - | - | - | - | - | - | X | - | - | X | - | - | - | - | - | ||
UTILS |
UTILS_ConfigureSystemClock |
How to use UTILS LL API to configure the system clock using PLL with HSI as source clock. | - | - | - | - | - | - | - | - | X | - | - | X | - | - | - | - | - | |
UTILS_ReadDeviceInfo |
How to read UID, Device ID and Revision ID and save them into a global information buffer. | - | - | - | - | - | - | - | - | X | - | - | X | - | - | - | - | - | ||
WWDG |
WWDG_RefreshUntilUserEvent |
Configuration of the WWDG to periodically update the counter and generate an MCU WWDG reset when a user button is pressed. The peripheral initialization uses the LL unitary service functions for optimization purposes (performance and size). | - | - | - | X | - | - | - | - | X | - | - | X | - | - | - | - | - | |
| Total number of examples_ll: 208 | 0 | 0 | 0 | 15 | 0 | 0 | 0 | 0 | 91 | 0 | 1 | 94 | 0 | 0 | 0 | 0 | 7 | |||
Examples_MIX |
ADC |
ADC_SingleConversion_TriggerSW_IT |
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 STM32L4xx ADC HAL and LL API (LL API usage for performance improvement). | - | - | - | - | - | - | - | - | X | - | - | - | - | - | - | - | - |
CRC |
CRC_PolynomialUpdate |
How to use the CRC peripheral through the STM32L4xx CRC HAL and LL API. | - | - | - | X | - | - | - | - | X | - | - | X | - | - | - | - | X | |
DMA |
DMA_FLASHToRAM |
How to use a DMA to transfer a word data buffer from Flash memory to embedded SRAM through the STM32L4xx DMA HAL and LL API. The LL API is used for performance improvement. | - | - | - | X | - | - | - | - | X | - | - | X | - | - | - | - | X | |
DMA2D |
DMA2D_MemToMemWithLCD |
How to configure the DMA2D peripheral in Memory-to-memory transfer mode and display the result on the LCD. The DMA2D LL APIs are used for performance improvement. | - | - | - | - | - | - | - | - | - | - | X | - | - | - | - | - | - | |
DMA2D_MemToMemWithRBSwap |
How to configure DMA2D peripheral in Memory-to-memory transfer mode with pixel format conversion and image blending, then display the result on LCD. The DMA2D LL APIs are used for performance improvement. | - | - | - | - | - | - | - | - | - | - | X | - | - | - | - | - | - | ||
I2C |
I2C_OneBoard_ComSlave7_10bits_IT |
How to perform I2C data buffer transmission/reception between one master and two slaves with different address sizes (7-bit or 10-bit). This example uses the STM32L4xx I2C HAL and LL API (LL API usage for performance improvement) and an interrupt. | - | - | - | - | - | - | - | - | X | - | - | X | - | - | - | - | - | |
OPAMP |
OPAMP_CALIBRATION |
How to calibrate and operate the OPAMP peripheral. This example is based on the STM32L4xx OPAMP HAL and LL API (LL API used for performance improvement). | - | - | - | - | - | - | - | - | X | - | - | - | - | - | - | - | - | |
PWR |
PWR_STANDBY_RTC |
How to enter Standby mode and wake up from this mode using an external reset or the RTC wakeup timer through the STM32L4xx RTC and RCC HAL and LL API. The LL API is used for performance improvement. | - | - | - | - | - | - | - | - | X | - | - | X | - | - | - | - | - | |
PWR_STOP1 |
How to enter the system in Stop 1 mode and wake up from this mode using external reset or wakeup interrupt (all the RCC functions calls use RCC LL API for footprint and performance improvements). | - | - | - | - | - | - | - | - | X | - | - | X | - | - | - | - | - | ||
SPI |
SPI_FullDuplex_ComPolling |
Data buffer transmission/reception between two boards via SPI using Polling mode. | - | - | - | - | - | - | - | - | X | - | - | X | - | - | - | - | - | |
SPI_HalfDuplex_ComPollingIT |
Data buffer transmission/reception between two boards via SPI using Polling (LL driver) and Interrupt modes (HAL driver). | - | - | - | - | - | - | - | - | X | - | - | X | - | - | - | - | - | ||
TIM |
TIM_6Steps |
Configuration of the TIM1 peripheral to generate six-step PWM signals. | - | - | - | - | - | - | - | - | X | - | - | X | - | - | - | - | - | |
UART |
UART_HyperTerminal_IT |
Use of a UART to transmit data (transmit/receive) between a board and an HyperTerminal PC application in Interrupt mode. This example describes how to use the USART peripheral through the STM32L4xx UART HAL and LL API, the LL API being used for performance improvement. | - | - | - | - | - | - | - | - | X | - | - | X | - | - | - | - | - | |
UART_HyperTerminal_TxPolling_RxIT |
Use of a UART to transmit data (transmit/receive) between a board and an HyperTerminal PC application both in Polling and Interrupt modes. This example describes how to use the USART peripheral through the STM32L4xx UART HAL and LL API, the LL API being used for performance improvement. | - | - | - | - | - | - | - | - | X | - | - | X | - | - | - | - | - | ||
| Total number of examples_mix: 28 | 0 | 0 | 0 | 2 | 0 | 0 | 0 | 0 | 12 | 0 | 2 | 10 | 0 | 0 | 0 | 0 | 2 | |||
Applications |
- |
Proximity |
This application shows how to use the VL53L0X sensor mounted on the B-L475E-IOT01A board to provide proximity information. | - | - | - | - | - | - | - | - | - | - | - | - | X | - | - | - | - |
BLE |
HeartRate |
This application shows how to use BLE component for HeartRate profile application. | - | - | - | - | - | - | - | - | - | - | - | - | X | - | - | - | - | |
P2P_LedButton |
This example aims at demonstrating point-to-point communications using the BLE component. | - | - | - | - | - | - | - | - | - | - | - | - | X | - | - | - | - | ||
FatFs |
FatFs_RAMDisk |
How to use STM32Cube firmware with FatFs middleware component as a generic FAT file system module. This example develops an application that exploits FatFs features to configure a RAM disk (SRAM) drive. | X | - | - | - | - | - | - | - | - | - | - | - | - | - | - | - | - | |
FatFs_USBDisk_Standalone |
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 both Full Speed (HS) mode. This example develops an application exploiting FatFs features, with USB disk drive configuration. | - | - | - | - | - | X | - | - | - | - | - | - | - | - | - | - | - | ||
FatFs_uSD_DMA_RTOS |
How to use STM32Cube firmware with FatFs middleware component as a generic FAT file system module. This example develops an application exploiting FatFs features, with a microSD drive in RTOS mode configuration. | X | - | - | - | - | X | - | - | - | - | X | - | - | - | - | - | - | ||
FatFs_uSD_DMA_Standalone |
How to use STM32Cube™ firmware with FatFs middleware component as a generic FAT file system module. This example develops an application making the most of FatFs features to configure a microSD drive. | - | - | - | - | - | X | - | - | - | - | - | - | - | - | - | - | - | ||
FatFs_uSD_Standalone |
How to use STM32Cube firmware with FatFs middleware component as a generic FAT file system module. This example develops an application that exploits FatFs features to configure a microSD drive. | 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 | - | X | - | |
FreeRTOS_LowPower_LPTIM |
How to enter and exit low-power mode with CMSIS RTOS API with LPTIM used as clock source for both RTOS and HAL ticks. | - | - | - | - | - | - | - | - | - | - | - | - | X | - | - | - | - | ||
FreeRTOS_MPU |
How to use the MPU feature of FreeRTOS. | - | - | - | - | - | X | - | - | X | - | - | - | - | - | - | - | - | ||
FreeRTOS_Mail |
How to use mail queues with CMSIS RTOS API. | X | - | - | X | - | - | - | - | - | - | - | X | - | - | - | X | - | ||
FreeRTOS_Mutexes |
How to use mutexes with CMSIS RTOS API. | X | - | - | X | - | - | - | - | - | - | - | X | - | - | - | X | - | ||
FreeRTOS_Queues |
How to use message queues with CMSIS RTOS API. | X | - | - | X | - | - | - | - | - | - | - | X | - | - | - | X | - | ||
FreeRTOS_Semaphore |
How to use semaphores with CMSIS RTOS API. | X | - | - | X | - | - | - | - | - | - | - | X | - | - | - | X | - | ||
FreeRTOS_SemaphoreFromISR |
How to use semaphore from ISR with CMSIS RTOS API. | X | - | - | X | - | - | - | - | - | - | - | X | - | - | - | X | - | ||
FreeRTOS_Signal |
How to perform thread signaling using CMSIS RTOS API. | X | - | - | X | - | - | - | - | - | - | - | X | - | - | - | X | - | ||
FreeRTOS_SignalFromISR |
How to perform thread signaling from an interrupt using CMSIS RTOS API. | X | - | - | X | - | - | - | - | - | - | - | X | - | - | - | X | - | ||
FreeRTOS_ThreadCreation |
How to implement thread creation using CMSIS RTOS API. | X | - | - | X | X | X | - | - | X | - | - | X | - | - | X | X | X | ||
FreeRTOS_Timers |
How to use timers of CMSIS RTOS API. | X | - | - | X | - | - | - | - | - | - | - | X | - | - | - | X | - | ||
IAP |
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 | - | - | - | - | - | - | - | - | - | - | - | - | - | - | - | - | |
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 | - | - | - | - | - | - | - | - | - | - | - | - | - | - | - | - | ||
NFC |
WrAARtoRunBLEapp |
This application aims at showing how to write an AAR NDEF message to an M24SR type 4 NFC tag so that the BLE STM32 Profiles application is launched on the smartphone when it comes near the NFC antenna . | - | - | - | - | - | - | - | - | - | - | - | - | X | - | - | - | - | |
WriteTag |
This application aims at showing how to write NDEF messages to an M24SR type 4 NFC tag so that the associated application is launched on the smartphone when it comes near the NFC antenna. | - | - | - | - | - | - | - | - | - | - | - | - | X | - | - | - | - | ||
STemWin |
HelloWorld |
Simple "Hello World" example based on STemWin. | - | - | - | - | - | - | - | - | - | - | - | - | - | X | - | - | - | |
STemWin_HelloWorld |
Simple "Hello World" example based on STemWin. | X | - | - | - | - | - | - | - | - | - | X | - | - | - | - | - | - | ||
STemWin_SampleDemo |
How to implement a sample demonstration example allowing to show some of the STemWin Library capabilities. | X | - | - | - | - | - | - | - | - | - | X | - | - | - | - | - | - | ||
SubGhz |
P2P |
This application aims at demonstrating point-to-point communication between two B-L475E-IOT01A boards with SubGhz module using Spirit1 driver and STM32Cube firmware. | - | - | - | - | - | - | - | - | - | - | - | - | X | - | - | - | - | |
TouchSensing |
TouchSensing_1touchkey |
Use of the STMTouch driver with 1 touchkey sensor. | X | - | - | - | - | X | - | - | - | - | - | - | - | - | - | - | - | |
USB_Device |
CDC_Standalone |
Use of the USB device application based on the Device Communication Class (CDC) and following the PSTN subprotocol. This application uses the USB Device and UART peripherals. | X | - | - | X | - | - | - | - | - | - | X | - | - | - | - | X | - | |
CustomHID_Standalone |
Use of the USB device application based on the Custom HID Class. | X | - | - | - | - | - | - | - | - | - | - | - | - | - | - | - | - | ||
DFU_Standalone |
Compliant implementation of the Device Firmware Upgrade (DFU) capability to program the embedded Flash memory through the USB peripheral. | X | - | - | X | X | X | X | - | - | - | X | - | - | X | X | X | - | ||
HID_Standalone |
Use of the USB device application based on the Human Interface (HID). | X | - | - | X | X | X | X | - | - | - | X | - | X | X | X | X | - | ||
HID_Standalone_BCD |
Use of the USB device application based on the Human Interface (HID) with Battery Charger Detection (BCD). | X | - | - | X | X | - | - | - | - | - | X | - | - | - | X | X | - | ||
HID_Standalone_LPM |
Use of the USB device application based on the Human Interface (HID) with Link Power Management Protocol (LPM). | X | - | - | - | X | - | - | - | - | - | X | - | - | - | X | X | - | ||
MSC_Standalone |
Use of the USB device application based on the Mass Storage Class (MSC). | X | - | - | - | - | X | - | - | - | - | - | - | - | - | - | - | - | ||
USB_Host |
CDC_Standalone |
Use of the USB host application based on the CDC class. | X | - | - | - | - | - | - | - | - | - | - | - | - | - | - | - | - | |
HID_Standalone |
Use of the USB host application based on the HID class. | X | - | - | - | - | - | X | - | - | - | X | - | - | - | - | - | - | ||
MSC_Standalone |
Use of the USB host application based on the Mass Storage Class (MSC). | X | - | - | - | - | X | X | - | - | - | X | - | X | X | - | - | - | ||
WiFi |
WiFi_Client_Server |
This application shows how to use the Es-WiFi module to perform a TCP client mode using STM32Cube HAL. It demonstrates how to set up a client program and 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 STM32Cube HAL. | - | - | - | - | - | - | - | - | - | - | - | - | X | - | - | - | - | ||
| Total number of applications: 125 | 28 | 0 | 0 | 14 | 5 | 12 | 5 | 0 | 2 | 0 | 11 | 10 | 11 | 6 | 5 | 15 | 1 | |||
Demonstrations |
- |
Adafruit_LCD_1_8_SD_Joystick |
Demonstration firmware based on STM32Cube. This example helps you to discover STM32 Cortex-M devices that are plugged onto your STM32 Nucleo board. | - | - | - | X | - | - | X | - | X | - | - | X | - | - | - | X | - |
Demo |
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 modular architecture. | - | - | - | - | - | - | - | - | - | - | X | - | - | - | X | - | - | ||
Gravitech_4digits |
Demonstration of firmware based on STM32Cube. This example provides firmware to to help you to discover STM32 Cortex-M devices that are plugged onto an your STM32NUCLEO_32 board. | - | - | - | - | X | - | - | - | - | - | - | - | - | - | - | - | X | ||
MB1144 |
The STM32Cube demonstration platform comes on top of the STM32Cube as a firmware package that offers a full set of software components based on a modular architecture. All modules can be reused separately in standalone applications. All these modules are managed by the STM32Cube demonstration kernel that allows to dynamically add new modules and access common resources (storage, graphical components and widgets, memory management, real-time operating system). The STM32Cube demonstration platform is built around the powerful graphical STemWin library and the FreeRTOS realtime operating system. It uses almost all STM32 features and offers a large scope of use cases based on the STM32Cube HAL BSP and several middleware components. | X | - | - | - | - | - | - | - | - | - | - | - | - | - | - | - | - | ||
MenuLauncher |
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 modular architecture. | - | - | - | - | - | - | - | - | - | - | - | - | - | X | - | - | - | ||
MenuLauncher |
MB1314 |
The STM32Cube demonstration platform comes on top of the STM32Cube(TM) as a firmware package that offers a full set of software components based on a modular architecture. | - | - | - | - | - | X | - | - | - | - | - | - | - | - | - | - | - | |
MB1315 |
The STM32Cube demonstration platform comes on top of the STM32Cube(TM) as a firmware package that offers a full set of software components based on a modular architecture. | - | - | - | - | - | X | - | - | - | - | - | - | - | - | - | - | - | ||
| Total number of demonstrations: 13 | 1 | 0 | 0 | 1 | 1 | 2 | 1 | 0 | 1 | 0 | 1 | 1 | 0 | 1 | 1 | 1 | 1 | |||
| Total number of projects: 1044 | 118 | 5 | 5 | 77 | 70 | 70 | 60 | 5 | 178 | 5 | 40 | 214 | 14 | 25 | 25 | 100 | 33 |


🍵
I'm a multidisciplinary product designer and illustrator, skilled at ux design and ux research.
Previously at Comcast/Xfinity and DogSpot.


Get Involved
The Money, Politics and Transparency Project is intended to provide an opportunity for advocates, researchers, party officials, regulators, journalists and others to collaborate and network on issues related to political finance transparency. To receive updates and join in discussions please:
- Join the Money, Politics and Transparency Google Group.
- Follow @MPTransparency
- Contact us about contribution to the creation of political finance transparency norms.
Related Organizations
Events
{% with event = upcoming_events[0] %}
{% if upcoming_count > 1 %}
{% endif %}
- Date
- {{ event.start.strftime('%B %-d, %Y') }}
- {{ event.title }}
- {% if event.url %} {{ event.title }} {% else %} {{ event.title }} {% endif %}
- Location
- {{ event.location }} {% if event.url %}
- Full event details
- Event details {% endif %}
More events
-
{% for event in upcoming_events[3:] %}
-
- Date
- {{ event.start.strftime('%B %-d, %Y') }}
- {{ event.title }}
- {% if event.url %} {{ event.title }} {% else %} {{ event.title }} {% endif %} {#
- Venue
- @Hartford Public Library #}
- Location
- {{ event.location }} {#
- Hosted by
- Connecticut Data Collaborative #} {% if event.url %}
- Full event details
- Event details {% endif %}
{% endfor %}


HOME › Analyst Briefings › Analyst Briefing presentation on the “Oil & Gas Automation & Instrumentation Market (SCADA, DCS, PLC & MES), Instrumentation, Analyzers, Flow Computers, Leakage Detection, Operation & Geography – Analysis & Forecast (2013 - 2020)”
Analyst Briefing presentation on the “Oil & Gas Automation & Instrumentation Market (SCADA, DCS, PLC & MES), Instrumentation, Analyzers, Flow Computers, Leakage Detection, Operation & Geography – Analysis & Forecast (2013 - 2020)”
The E&SC practice at MarketsandMarkets is pleased to announce its Analyst Briefing presentation on the “Oil & Gas Automation & instrumentation Market (SCADA, DCS, PLC & MES), Instrumentation, Analyzers, Flow Computers, Leakage Detection, Operation & Geography – Analysis & Forecast (2013 - 2020)”, to be held on 11 December, 2013.
Process automation & instrumentation market in the oil & gas industry are segmented into five technologies; namely process automation, process instrumentation, process analyzer, flow computer, and leakage detection system. The other segmentation is done on the basis of the operational activities, namely the upstream operation, midstream operation, and downstream operation.
Process automation & instrumentation market in the oil & gas industry is expected to reach $31.24 billion by 2020, at an estimated CAGR of 8.23% from 2013 to 2020.
The overall process automation & instrumentation market in the oil & gas industry is segmented into three major segments, namely technology, operation, and geography. All the major segments are further segmented into sub segments. All the segments and sub segments are separately described in the report. Geography-wise segmentation is also done for the oil & gas automation & instrumentation market. The market by geography is segmented on the basis of the six major regions, namely the Americas, the Middle East, Europe, APAC, Africa, and Rest of the World (ROW).
The main drivers for the process automation and instrumentation market in oil and gas industry include:- exploration and extraction of shale gas, rising demand of oil and gas, upgrading old oil and gas platform, exploration and extraction from aging oil and gas wells, and the increasing emphasis on safety and security. Development of oil and gas in the emerging economies is expected to be a major growth opportunity with regards to the process automation and instrumentation market in the oil and gas industry. Moreover, major restraints for the market include matured and saturated developed economies, and issues of integration of the data generated by installed automation products.
Some of the major companies dominating the process automation & instrumentation market in the oil & gas industry are ABB (Switzerland), Emerson Process Management (U.S.), Siemens (Germany), Honeywell (U.S.), Rockwell Automation (U.S.), and Yokogawa (Japan).
The figure below shows the estimated continuous growth of process automation & instrumentation market in the oil & gas industry in the coming seven years till 2020.
Source: MarketsandMarkets Analysis
The agenda for the briefing includes discussion on the key high growth markets, thereby marking the growth trend in the process automation & instrumentation market in the oil & gas industry. Furthermore, a briefing will be conducted on the competitive scenario and geographic trends and opportunities in the macro and micro-markets with respect to Americas, Middle East, Europe, Africa, Asia-Pacific, and ROW
About MarketsandMarkets
MarketsandMarkets is a global market research and consulting company based in the U.S. We publish strategically analyzed market research reports and serve as a business intelligence partner to Fortune 500 companies across the world.
MarketsandMarkets also provides multi-client reports, company profiles, databases, and custom research services. They cover thirteen industry verticals, including advanced materials, automotives and transportation, banking and financial services, biotechnology, chemicals, consumer goods, energy and power, food and beverages, industrial automation, medical devices, pharmaceuticals, semiconductor and electronics, and telecommunications and IT.
We at MarketsandMarkets are inspired to help our clients grow by providing apt business insight with our huge market intelligence repository.
Note: An email containing the Login Details and Time of the Analyst Briefing will be sent to you soon after your registration.


Student Organization - Check Request Form
Request for payment to
Amount to be paid
Reason for request
Individual requesting check
Organization to be charged
Indicate what date this check is needed
2nd signature for approval
Today's Date
Comments
Request Approved By
Date
Check #
Date Issued
Date mailed/picked up


nips nips2000 nips2000-47 nips2000-47-reference knowledge-graph by maker-knowledge-mining
Source: pdf
Author: Renato Vicente, David Saad, Yoshiyuki Kabashima
Abstract: We analyze Gallager codes by employing a simple mean-field approximation that distorts the model geometry and preserves important interactions between sites. The method naturally recovers the probability propagation decoding algorithm as an extremization of a proper free-energy. We find a thermodynamic phase transition that coincides with information theoretical upper-bounds and explain the practical code performance in terms of the free-energy landscape.
[1] Plefka, T., (1982) Convergence condition of the TAP equation for the infinite-ranged Ising spin glass model. Journal of Physics A 15, 1971-1978.
[2] Tanaka, T., Information geometry of mean field approximation. to appear in Neural Computation
[3] Saul, L.K. & , M.L Jordan (1996) Exploiting tractable substructures in intractable. In Touretzky, D. S. , M. C. Mozer and M. E. Hasselmo (eds.), Advances in Neural Information Processing Systems 8, pp. 486-492. Cambridge, MA: MIT Press.
[4] Frey, B.J. & D.J.C. MacKay (1998) A revolution: belief propagation in graphs with cycles. In Jordan, M.L, M. J. Kearns and S.A. Solla (eds.), Advances in Neural Information Processing Systems 10, pp. 479-485 . Cambridge, MA: MIT Press.
[5] Berrou, C. & A. Glavieux (1996) Near optimum error correcting coding and decoding: Turbocodes, IEEE Transactions on Communications 44,1261-1271.
[6] Gallager, R.G. (1963) Low-density parity-check codes, MIT Press, Cambridge, MA.
[7] MacKay, D.J.C. (1999) Good error-correcting codes based on very sparse matrices, IEEE Transactions on Information Theory 45, 399-431.
[8] Kanter, 1. & D. Saad (2000) Finite-size effects and error-free communication in Gaussian channels, Journal of Physics A 33, 1675-1681.
[9] Sourlas, N. (1989) Spin-glass models as error-correcting codes, Nature 339, 693-695.
[10] Derrida, B. (1981) Random-energy model: an exactly solvable model of disordered systems, Physical Review B 24(5),2613-2626.
[11] Vicente, R., D. Saad & Y. Kabashima (1999) Finite-connectivity systems as error-correcting codes, Physical Review E 60(5), 5352-5366.
[12] Kabashima, Y., T. Murayama & D.Saad (2000) Typical performance of Gallager-type errorcorrecting codes, Physical Review Letters 84 (6), 1355-1358.
[13] Montanari, A. & N. Sourlas (2000) The statistical mechanics of turbo codes, European Physical Journal B 18,107-119.
[14] Sherrington, D. & K.Y.M. Wong (1987) Graph bipartitioning and the Bethe spin glass, Journal of Physics A 20, L 785-L791.
[15] Kabashima, Y. & D. Saad (1998) Belief propagation vs. TAP for decoding corrupted messages, Europhysics Letters 44 (5), 668-674.
[16] Kschischang, F.R. & B.J. Frey, (1998) Iterative decoding of compound codes by probability probagation in graphical models, IEEE Journal on Selected Areas in Comm. 16 (2), 153-159.
[17] Gujrati, P.D. (1995) Bethe or Bethe-like lattice calculations are more reliable than conventional mean-field calculations , Physical Review Letters 74 (5) , 809-812.
[18] Rieger, H. & T.R. Kirkpatrick (1992) Disordered p-spin interaction models on Husirni trees, Physical Review B 45 (17), 9772-9777.


| 1 | /** | |
| 2 | * Copyright 2013 Mozilla Foundation | |
| 3 | * | |
| 4 | * Licensed to the Apache Software Foundation (ASF) under one | |
| 5 | * or more contributor license agreements. See the NOTICE file | |
| 6 | * distributed with this work for additional information | |
| 7 | * regarding copyright ownership. The ASF licenses this file | |
| 8 | * to you under the Apache License, Version 2.0 (the | |
| 9 | * "License"); you may not use this file except in compliance | |
| 10 | * with the License. You may obtain a copy of the License at | |
| 11 | * | |
| 12 | * http://www.apache.org/licenses/LICENSE-2.0 | |
| 13 | * | |
| 14 | * Unless required by applicable law or agreed to in writing, software | |
| 15 | * distributed under the License is distributed on an "AS IS" BASIS, | |
| 16 | * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. | |
| 17 | * See the License for the specific language governing permissions and | |
| 18 | * limitations under the License. | |
| 19 | */ | |
| 20 | package com.mozilla.pig.eval.json; | |
| 21 | ||
| 22 | import java.util.HashMap; | |
| 23 | import java.util.List; | |
| 24 | import java.util.Map; | |
| 25 | ||
| 26 | import org.apache.pig.data.Tuple; | |
| 27 | ||
| 28 | public class JsonTupleMap extends JsonMap { | |
| 29 | | |
| 30 | /** | |
| 31 | * Converts List objects to Tuple to keep Pig happy | |
| 32 | * | |
| 33 | * @param l | |
| 34 | * @return | |
| 35 | */ | |
| 36 | @SuppressWarnings("unchecked") | |
| 37 | private Tuple convertListToTuple(List<Object> l) { | |
| 38 | Tuple t = tupleFactory.newTuple(); | |
| 39 | for (Object o : l) { | |
| 40 |
1
1. convertListToTuple : negated conditional → KILLED |
if (o instanceof List) { |
| 41 |
1
1. convertListToTuple : removed call to org/apache/pig/data/Tuple::append → KILLED |
t.append(convertListToTuple((List<Object>) o)); |
| 42 | } else { | |
| 43 |
1
1. convertListToTuple : removed call to org/apache/pig/data/Tuple::append → KILLED |
t.append(o); |
| 44 | } | |
| 45 | } | |
| 46 | ||
| 47 |
1
1. convertListToTuple : mutated return of Object value for com/mozilla/pig/eval/json/JsonTupleMap::convertListToTuple to ( if (x != null) null else throw new RuntimeException ) → KILLED |
return t; |
| 48 | } | |
| 49 | ||
| 50 | /** | |
| 51 | * Convert map and its values to types that Pig can handle | |
| 52 | * | |
| 53 | * @param m | |
| 54 | * @return | |
| 55 | */ | |
| 56 | @Override | |
| 57 | @SuppressWarnings("unchecked") | |
| 58 | protected Map<String, Object> makeSafe(Map<String, Object> m) { | |
| 59 | Map<String, Object> safeValues = new HashMap<String, Object>(); | |
| 60 | for (Map.Entry<String, Object> entry : m.entrySet()) { | |
| 61 | Object v = entry.getValue(); | |
| 62 |
2
1. makeSafe : negated conditional → KILLED 2. makeSafe : negated conditional → KILLED |
if (v != null && v instanceof List) { |
| 63 | // This is the main diff from the parent class | |
| 64 | // in that it converts lists to | |
| 65 | Tuple t = convertListToTuple((List<Object>) v); | |
| 66 | safeValues.put(entry.getKey(), t); | |
| 67 |
2
1. makeSafe : negated conditional → SURVIVED 2. makeSafe : negated conditional → SURVIVED |
} else if (v != null && v instanceof Map) { |
| 68 | safeValues.put(entry.getKey(), makeSafe((Map<String, Object>) v)); | |
| 69 | } else { | |
| 70 | safeValues.put(entry.getKey(), v); | |
| 71 | } | |
| 72 | } | |
| 73 | ||
| 74 |
1
1. makeSafe : mutated return of Object value for com/mozilla/pig/eval/json/JsonTupleMap::makeSafe to ( if (x != null) null else throw new RuntimeException ) → KILLED |
return safeValues; |
| 75 | } | |
| 76 | } | |
Mutations | ||
| 40 |
1.1 |
|
| 41 |
1.1 |
|
| 43 |
1.1 |
|
| 47 |
1.1 |
|
| 62 |
1.1 2.2 |
|
| 67 |
1.1 2.2 |
|
| 74 |
1.1 |


Swell Configuration
Collect data for this session?
Yes
No
Allow Direct Manipulation?
Yes
No
Continue


Property pro lite is being developed by NZAKIZWANIMANA Theoneste as project to join Andela Fellowiship program. This is one of the project that all Andelans must do when they are entering in the fellowship. As the title say we are future software developers, Andela builds high-performing, distributed engineering teams with Africa’s most talented software developers. We believe the future of software development is open, inclusive, and everywhere. And I believe that and that is why I am interested in joining Andela


This is an example how to customize Nginx by Chef.
Nginx is the reverse proxy server, that I usually use as load balancer in my solutions. Now I have requirement how to simplify the configuration of the Nginx and to support it by some remote service.
The first step is to manage web sites by Chef. We will create DataBag that will contains all information about sites and where to redirect requests from Nginx.
1. Data Bag Creation
Assume that we have Nginx installed in our network and some machines with internal IP addresses that serves requests. We want to support simple list of the servers and addresses where to redirect HTTP requests.
Let’s create simple data bag fronta.json
{
"id": "fronta",
"forwards": [
{
"site": "site1",
"hostnames": "site1-example.com www.site1-example.com www2.site1-example.com",
"url": "http://<IP_ADDRESS>:8080/",
"enabled": "true"
},
{
"site": "site2",
"hostnames": "site2-example.com www.site2-example.com",
"url": "http://<IP_ADDRESS>:8080/",
"enabled": "true"
}
],
"ssl_forwards": [
{
"alias": "ssl-site1",
"url": "http://192.168.123:8443/ssl-site1/"
},
{
"alias": "ssl-site2",
"url": "http://192.168.122:8443/ssl-site2/"
}
]
}
In this Data Bag we are having two sections: forwards and ssl_forwards. The first one is used for simple HTTP forwards for internal machines, the second one for SSL.
When HTTP request comes to port 80 with server name “site1-example.com” then Nginx forwards request to http://<IP_ADDRESS>:8080/ in our internal network.
When HTTPS request comes to port 443 like https://out-nginx-machine.com/ssl-site1/ then Nginx forwards it to http://192.168.123:8443/ssl-site1/
We need to upload data bag to Chef Server by command:
knife data bag from file fronta fronta.json
You will see message:
Updated data_bag_item[fronta::fronta]
2. Role Creation
Crete the role fronta.rb and upload this role to Chef Server:
knife role from file fronta.rb
You will see message:
Updated Role fronta!
Assign role to the node:
knife node run_list add front_node "role[fronta]"
3. Cookbook modification
In the previous article we successfully installed Nginx by Chef.
And now we are going to modify cookbook nginx to add nginx::fronta recipe.
Create the recipe nginx/recipes/fronta.rb
Uncomment this block in order to automate ssl.key installation, place your ssl.key file to the “nginx/files/default/ssl/ssl.key” in the cookbook.
In other case, place manually ssl.key to /etc/nginx/ssl.key on the front_node.
#cookbook_file "#{node['nginx']['dir']}/ssl.key" do
# source "ssl/ssl.key"
# owner "root"
# group "root"
# mode "0600"
#end
Place you ssl.crt file to the “nginx/files/default/ssl/ssl.crt”, this file could be chained if you have intermediate certificate.
Create template file nginx/templates/default/forward-site.erb
Create SSL template file nginx/templates/default/ssl-site.erb
Upload cookbook to the Chef Server
knife cookbook upload nginx
4. Operations
Now each time when you have new site in nginx, you need only to modify fronta.json file and to upload data bag
knife data bag from file fronta fronta.json
You could manage data bags from Chef Server and through API.
Chef-client automatically refreshed settings from Chef Server, if you want to speed up this process then go to the front_node and run:
sudo -i
chef-client
Done.


In this project we present software design patterns in JavaScript.
Images were generated by StarUML from the .mdj file in the staruml-design-patterns project. Classes are implemented with js.class.
Everyone is welcome to improve on this and provide implementation in various programming languages.
Target audience
Tehnical developers in the making. Previous Javascript and design pattern knowledge is recommended.
- External resources:
- GoF's Design Paterns
- Addy Osmani's Learning JavaScript Design Patterns