Copyright 2016 STMicroelectronics
The STM32CubeL0 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_STM32CubeL0_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 STM32CubeL0 Firmware package.
| Level | Module Name | Project Name | Description | STM32L073Z_EVAL | STM32L011K4-Nucleo | STM32L031K6-Nucleo | STM32L073RZ-Nucleo | STM32L053R8-Nucleo | STM32L053C8-Discovery |
Templates_LL |
- |
Starter project |
This projects provides a reference template through the LL API that can be used to build any firmware application. | X | X | X | X | X | X |
| Total number of templates_ll: 6 | 1 | 1 | 1 | 1 | 1 | 1 | |||
Templates |
- |
Starter project |
This projects provides a reference template that can be used to build any firmware application. | X | X | X | X | X | X |
| Total number of templates: 6 | 1 | 1 | 1 | 1 | 1 | 1 | |||
Examples |
- |
BSP |
This example provides a description of how to use the different BSP drivers. | X | - | - | - | X | - |
ADC |
ADC_AnalogWatchdog |
This example provides a short description of how to use the ADC peripheral to perform conversions with analog watchdog and interruptions. | X | - | - | X | - | - | |
ADC_DMA_Transfer |
This example describes 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_LowPower |
This example provides a short description of how to use the ADC peripheral to perform conversions with ADC low power modes: auto-wait and auto-power off. | X | X | X | X | X | X | ||
ADC_OverSampler |
This example describes how to configure and use ADC to convert an external analog input (PA0) combined with oversampling feature to increase resolution, through the STM32L0xx HAL API. | - | - | X | - | X | X | ||
ADC_RegularConversion_Interrupt |
This example describes how to use the ADC1 and Interrupt to convert continuously data from ADC1 channel0., through the STM32L0xx HAL API. | X | - | X | X | X | X | ||
ADC_RegularConversion_Polling |
This example describes how to use the ADC1 and the Polling mode to convert data from ADC1 channel0. | X | - | X | X | X | - | ||
ADC_Sequencer |
This example provides a short description of how to use the ADC peripheral with sequencer to convert several channels. | - | - | - | - | X | - | ||
AES |
AES_DMA |
This example provides a short description of how to use the AES peripheral to encrypt and decrypt data using AES Algorithm with ECB chaining mode. | - | - | - | - | X | - | |
AES_Modes |
This example provides a short description of how to configure the AES hardware accelerator to encrypt then to decrypt text with the different modes ECB, CBC et CTR. | - | - | - | - | X | - | ||
COMP |
COMP_AnalogWatchdog |
This example shows how to make an analog watchdog using the COMP peripherals in window mode. | X | - | - | X | X | X | |
COMP_Interrupt |
This example shows how to configure the COMP peripheral to compare the external voltage applied on PA1 with the Internal Voltage Reference. | - | - | - | - | X | - | ||
COMP_PWMSignalControl |
This example shows how to configure COMP2 peripheral to automatically hold TIM21 PWM output on safe state (low level) as soon as comparator output is set at high level. | X | - | X | X | X | X | ||
COMP_PulseWidthMeasurement |
This example shows how to configure the COMP1 peripheral to measure pulse width. | X | - | - | X | X | X | ||
CRC |
CRC_Data_Reversing_16bit_CRC |
This example guides you through the different configuration steps by means of the HAL API. The CRC (Cyclic Redundancy Check) calculation unit computes a 16-bit long CRC code derived from a buffer of 8-bit data (bytes). | - | - | - | X | - | - | |
CRC_Example |
This example guides you through the different configuration steps by mean of HAL API to ensure the use of the CRC (Cyclic Redundancy Check) calculation unit to get a CRC code of a given buffer of data words (32-bit long), based on a fixed generator polynomial (0x4C11DB7). | X | X | X | X | X | X | ||
CRC_bytes_stream_7bit_CRC |
This example guides you through the different configuration steps by means of the HAL API. The CRC (Cyclic Redundancy Check) calculation unit computes 7-bit long CRC codes derived from buffers of 8-bit data (bytes). | - | - | - | X | - | - | ||
CRYP |
CRYP_AESModes |
This example provides a short description of how to use the CRYP peripheral to encrypt and decrypt data using AES in chaining modes (ECB, CBC, CTR). | - | X | X | X | - | - | |
CRYP_DMA |
This example provides a short description of how to use the CRYP peripheral to encrypt and decrypt data using AES 128 Algorithm with ECB chaining mode in DMA mode. | - | X | X | X | - | - | ||
Cortex |
CORTEXM_MPU |
This example presents the MPU feature. The example purpose is to configure a memory region as privileged read only region and tries to perform read and write operation in different mode. | X | - | - | X | X | X | |
CORTEXM_ModePrivilege |
This example shows how to modify CortexM0+ Thread mode privilege access and stack. | - | - | - | - | X | X | ||
CORTEXM_SysTick |
This example shows how to use the default SysTick configuration with a 1 ms timebase to toggle LEDs. | X | - | - | X | X | X | ||
DAC |
DAC_SignalsGeneration |
This example provides a description of how to use the DAC peripheral to generate several signals using DMA controller. | X | - | - | X | X | X | |
DAC_SimpleConversion |
This example provides a short description of how to use the DAC peripheral to do a simple conversion in 8 bits right alignment of 0xFF value, the result of conversion can be seen by connecting PA4(DAC channel1) to an oscilloscope. | X | - | - | X | X | X | ||
DMA |
DMA_FLASHToRAM |
This example provides a description of how to use a DMA to transfer a word data buffer from Flash memory to embedded SRAM through the HAL API. | X | X | X | X | X | X | |
DMA_RAMToDAC |
This example provides a description of how to use a DMA channel to transfer data buffer from RAM memory to DAC. | - | - | - | X | X | X | ||
FIREWALL |
FIREWALL_VolatileData_Executable |
This example shows how to use the Firewall IP to protect a volatile data segment located in SRAM and to define it as executable. | X | - | - | - | - | - | |
| This example shows how to use the Firewall IP to protect a code segment as well as volatile and non-volatile data segments. | X | - | - | - | - | - | |||
FLASH |
FLASH_DualBoot |
This example guides you through the different configuration steps by mean of HAL API on how to program bank1 and bank2 of the STM32L0xx internal Flash memory mounted on STM32L073Z-EVAL and swap between both of them. | X | - | - | - | - | - | |
FLASH_DualBoot_Workaround |
This example guides you through the different configuration steps by mean of HAL API on how to program bank1 and bank2 of the STM32L0xx internal Flash memory mounted on STM32L073Z-EVAL and possibly boot on one of them. | X | - | - | - | - | - | ||
FLASH_EraseProgram |
This example guides you through the different configuration steps by mean of HAL API how to erase and program the STM32L0xx internal Flash memory mounted on STM32L073Z-EVAL. | X | X | X | X | X | X | ||
FLASH_WriteProtection |
This example describes how to configure and use the FLASH HAL API to enable and disable the write protection of the internal Flash memory. | X | X | X | X | X | X | ||
GPIO |
GPIO_EXTI |
This example shows how to configure external interrupt lines. | X | - | - | X | X | X | |
GPIO_IOToggle |
This example describes how to configure and use GPIOs through the STM32L0xx HAL API. | X | X | X | X | X | - | ||
GPIO_IOToggle_MaxFrequency |
This example describes how to configure and use GPIOs through the STM32L0xx HAL API. | X | X | X | X | X | X | ||
GPIO_IOToggle_VariableFreq |
This example describes how to make toggle LED3 at different frequencies. It configures and uses GPIOs for LED and vitual button through the STM32L0xx HAL API. | - | - | X | - | - | - | ||
HAL |
HAL_TimeBase |
This example describes how to customize the HAL time base using a general purpose timer(TIM6) instead of Systick as main source of time base. | - | - | - | - | X | X | |
I2C |
I2C_TwoBoards_AdvComIT |
This example describes how to perform I2C data buffer transmission/reception between two boards, using an interrupt. | X | X | X | X | X | X | |
I2C_TwoBoards_ComDMA |
This example describes how to perform I2C data buffer transmission/reception between two boards, via DMA. | X | X | X | X | X | X | ||
I2C_TwoBoards_ComIT |
This example describes how to perform I2C data buffer transmission/reception between two boards using an interrupt. | - | X | X | - | X | X | ||
I2C_TwoBoards_ComPolling |
This example describes how to perform I2C data buffer transmission/reception between two boards in Polling mode. | - | X | X | - | X | - | ||
I2C_TwoBoards_RestartAdvComIT |
This example describes how to perform a multiple I2C data buffer transmission/reception between two boards in Interrupt mode and with a restart condition. | - | - | - | X | - | - | ||
I2C_TwoBoards_RestartComIT |
This example describes how to perform a single I2C data buffer transmission/reception between two boards in Interrupt mode and with a restart condition. | - | - | - | X | - | - | ||
I2C_WakeUpFromStop |
This example describes how to perform I2C data buffer transmission/reception between two boards using an interrupt when the device is in STOP mode. | X | X | X | X | - | - | ||
IWDG |
IWDG_Reset |
This example describes how to ensure IWDG reload counter and simulate a software fault that generates an MCU IWDG reset when a programmed time period has elapsed. | X | X | X | X | X | X | |
IWDG_WindowMode |
This example shows how to periodically update the IWDG reload counter and simulate a reload outside the window that generates an MCU IWDG reset. | X | - | - | X | X | X | ||
LCD |
LCD_Blink_Frequency |
This example provides a description of how to use the STM32L0xx embedded LCD GLASS controller and how to configures the LCD Blink mode and Blink frequency. | X | - | - | - | X | - | |
LCD_SegmentsDrive |
This example provides a description of how to use the STM32L0xx embedded LCD controller to drive the Pacific Display LCD glass mounted on STM32L152C-Disovery board. | - | - | - | - | X | - | ||
LPTIM |
LPTIM_PWMExternalClock |
This example describes how to configure and use LPTIM to generate a PWM at the lowest power consumption, using an external counter clock, through the HAL LPTIM API. | X | - | - | - | X | X | |
LPTIM_PWM_LSE |
This example describes how to configure and use LPTIM to generate a PWM in low power mode using the LSE as a counter clock, through the HAL LPTIM API. | X | - | - | - | X | X | ||
LPTIM_PulseCounter |
This example describes how to configure and use LPTIM to count pulses through the LPTIM HAL API. | X | X | X | X | X | X | ||
LPTIM_Timeout |
This example describes how to implement a low power timeout to wake-up the system using the LPTIMER, through the HAL LPTIM API. | X | - | X | X | X | X | ||
PWR |
PWR_LPRUN |
This example shows how to enters the system to Low Power Run mode and exit from this mode using Wkup/Tamper push-button. | X | X | X | X | X | X | |
PWR_LPSLEEP |
This example shows how to enters the system to Low Power Sleep mode and wake-up from this mode using Wkup/Tamper push-button EXTI lines 4 to 15. | X | X | X | X | X | X | ||
PWR_PVD |
This example shows how to configure the programmable voltage detector using an external interrupt line. External DC supply has to be used to power Vdd. | X | X | X | X | X | X | ||
PWR_SLEEP |
This example shows how to enters the system to Sleep mode and wake-up from this mode using Wkup/Tamper push-button EXTI lines 4 to 15. | X | X | X | X | X | X | ||
PWR_STANDBY |
This example shows how to enters the system to STANDBY mode and wake-up from this mode using: external RESET or WKUP pin. | X | X | X | X | X | X | ||
PWR_STANDBY_RTC |
This example shows how to enter the system to STANDBY mode and wake-up from this mode using RTC Wakeup Timer Event connected to EXTI Line 20. | X | X | X | X | X | X | ||
PWR_STOP |
This example shows how to enters the system to STOP mode and wake-up from this mode using Key push button EXTI_Line4-15. | X | X | X | X | X | X | ||
PWR_STOP_RTC |
This example shows how to enter the system to STOP mode and wake-up from this mode using RTC Wakeup Timer Event connected to EXTI_Line17. | X | X | X | X | X | X | ||
RCC |
RCC_CRS_Synchronization_IT |
This example describes how to use the RCC HAL API to configure Clock Recovery Service in IT mode. | X | - | - | - | - | - | |
RCC_CRS_Synchronization_Polling |
This example describes how to use the RCC HAL API to configure Clock Recovery Service in using polling mode. | X | - | - | - | - | - | ||
RCC_ClockConfig |
This example describes how to use the RCC HAL API to configure the system clock (SYSCLK) and modify the clock settings on run time. | X | - | - | - | X | - | ||
RCC_LSIConfig |
This example describes how to use the RCC HAL API to enable or disable the low-speed internal (LSI) RC oscillator (about 40 KHz) at run time. | X | X | X | X | - | - | ||
RNG |
RNG_MultiRNG |
This example guides you through the HAL API different configuration steps to ensure 32-bit long random numbers generation by RNG peripheral. | X | - | - | X | X | X | |
RTC |
RTC_Alarm |
This example guides you through the different configuration steps by means of the RTC HAL API to configure and generate an RTC alarm. | X | X | X | X | X | X | |
RTC_Calendar |
This example guides you through the different configuration steps by mean of HAL API to ensure Calendar configuration using the RTC peripheral. | X | X | X | - | - | X | ||
RTC_LSI |
This example demonstrates and explains how to use the LSI clock source auto calibration to get a precise RTC clock. | X | X | X | X | X | X | ||
RTC_LowPower_STANDBY |
This example shows how to enter the system to STANDBY mode and wake-up from this mode using RTC Alarm Event. | X | - | - | - | - | - | ||
RTC_Tamper |
This example guides you through the different configuration steps by means of the RTC HAL API to write/read data to/from RTC Backup registers and demonstrate the tamper detection feature. | X | X | X | X | X | X | ||
RTC_TimeStamp |
This example guides you through the different configuration steps by means of the RTC HAL API to demonstrate the timestamp feature. | X | X | X | X | X | X | ||
SMBUS |
SMBUS_TSENSOR |
This example guides you through the different configuration steps by mean of HAL API to ensure SMBUS Data buffer transmission and reception with IT. | X | - | - | - | - | - | |
SPI |
SPI_FullDuplex_AdvCom |
This example guides you through the different configuration steps by mean of HAL API to transmit/receive SPI data buffer in Polling mode and in an advanced communication mode: the master board always sends the command to the slave before any transmission is performed. | - | - | - | - | X | - | |
SPI_FullDuplex_ComDMA |
This example shows how to perform SPI data buffer transmission/reception between two boards via DMA. | X | X | X | X | X | X | ||
SPI_FullDuplex_ComIT |
This example shows how to ensure SPI data buffer transmission/reception between two boards by using an interrupt. | X | X | X | X | X | X | ||
SPI_FullDuplex_ComPolling |
This example shows how to ensure SPI data buffer transmission/reception in Polling mode between two boards. | X | X | X | X | X | - | ||
TIM |
TIM_DMA |
This example provides a description of how to use DMA with TIMER Update request to transfer Data from memory to TIMER Capture Compare Register 3 (CCR3). | X | X | X | X | X | X | |
TIM_DMABurst |
This example shows how to update the TIMER channel1 period and the duty cycle using the TIMER DMA burst feature. | X | X | X | X | X | X | ||
TIM_ExtTriggerSynchro |
This example shows how to synchronize TIM peripherals in cascade mode with an external trigger. | - | - | - | - | X | - | ||
TIM_InputCapture |
This example shows how to use the TIM peripheral to measure the frequency of an external signal. | X | X | X | X | X | X | ||
TIM_OCActive |
This example shows how to configure the TIM peripheral in Output Compare Active mode (when the counter matches the capture/compare register, the concerned output pin is set to its active state). | X | X | X | X | X | X | ||
TIM_OCInactive |
This example shows how to configure the TIM peripheral in Output Compare Inactive mode with the corresponding Interrupt requests for each channel. | X | X | X | X | X | - | ||
TIM_OCToggle |
This example shows how to configure the TIM peripheral to generate four different signals with four different frequencies. | X | X | X | X | X | X | ||
TIM_OnePulse |
This example shows how to use the TIM peripheral to generate a One pulse Mode after a Rising edge of an external signal is received in Timer Input pin. | X | X | X | X | X | - | ||
TIM_PWMInput |
This example shows how to use the TIM peripheral to measure the frequency and duty cycle of an external signal. | - | - | - | X | X | - | ||
TIM_PWMOutput |
This example shows how to configure the TIM peripheral in PWM (Pulse Width Modulation) mode. | X | X | X | X | X | X | ||
TIM_TimeBase |
This example shows how to configure the TIM peripheral to generate a time base of one second with the corresponding Interrupt request. | X | X | X | X | X | X | ||
TSC |
TSC_BasicAcquisition_Interrupt |
This example describes how to use the TSC to perform continuous acquisitions of two channels in interrupt mode. | X | - | - | - | - | - | |
TSC_BasicAcquisition_Polling |
This example describes how to use the TSC to perform continuous acquisitions of one channel in polling mode. | X | - | - | - | - | - | ||
UART |
LPUART_TwoBoards_ComIT |
This Example shows a LPUART transmission (transmit/receive) between 2 STM32L0538-DISCO boards in interrupt mode, the two LPUART are clocked with LSI. | - | - | - | - | - | X | |
LPUART_WakeUpFromStop |
This example shows how to configure the LPUART to wake up the MCU from STOP mode when the proper stimulus is received. | - | - | - | - | - | X | ||
UART_HyperTerminal_DMA |
This example shows how to ensure UART Data buffer transmission and reception with DMA. The communication is done with the Hyperterminal PC application. | X | X | X | - | - | - | ||
UART_LowPower_HyperTerminal_DMA |
This example guides you through the different configuration steps by mean of HAL API to ensure UART Data buffer transmission and reception with DMA. | X | - | - | - | - | - | ||
UART_Printf |
This example shows how to retarget the C library printf function to the UART. | X | X | X | - | - | - | ||
UART_TwoBoards_ComDMA |
This example describes an UART transmission (transmit/receive) in DMA mode between two STM32L073Z-EVAL boards. | X | X | X | X | X | X | ||
UART_TwoBoards_ComIT |
This example describes an UART transmission (transmit/receive) in interrupt mode between two STM32L073Z-EVAL boards. | X | X | X | X | X | X | ||
UART_TwoBoards_ComPolling |
This example describes an UART transmission (transmit/receive) in polling mode between two STM32L073Z-EVAL boards. | X | X | X | X | X | - | ||
UART_WakeUpFromStop |
This example shows how to configure an UART to wake up the MCU from STOP mode when the proper stimulus is received. | X | X | X | - | - | - | ||
WWDG |
WWDG_Example |
This example guides you through the different configuration steps by means of the HAL API to perform periodic WWDG counter update and simulate a software fault that generates an MCU WWDG reset when a predefined time period has elapsed. | X | X | X | X | X | X | |
| Total number of examples: 375 | 76 | 50 | 56 | 64 | 72 | 57 | |||
Examples_LL |
ADC |
ADC_AnalogWatchdog |
This example describes how to use a ADC peripheral with ADC analog watchdog to monitor a channel and detect when the corresponding conversion data is out of window thresholds; This example is based on the STM32L0xx ADC LL API; peripheral initialization done using LL unitary services functions for optimization purpose (performance and size). | - | - | - | X | - | - |
ADC_ContinuousConversion_TriggerSW |
This example describes how to use a ADC peripheral to perform continuous ADC conversions of a channel, from a SW start; This example is based on the STM32L0xx ADC LL API; peripheral initialization done using LL unitary services functions for optimization purpose (performance and size). | - | - | - | X | - | - | ||
ADC_ContinuousConversion_TriggerSW_Init |
This example describes how to use a ADC peripheral to perform continuous ADC conversions of a channel, from a SW start; This example is based on the STM32L0xx ADC LL API; peripheral initialization done using LL unitary services functions for optimization purpose (performance and size). | - | - | - | X | - | - | ||
ADC_ContinuousConversion_TriggerSW_LowPower |
This example describes how to use a ADC peripheral with ADC low power features; This example is based on the STM32L0xx ADC LL API; peripheral initialization done using LL unitary services functions for optimization purpose (performance and size). | - | - | - | X | - | - | ||
ADC_MultiChannelSingleConversion |
This example describes how to use a ADC peripheral to convert several channels, ADC conversions are performed successively in a scan sequence; This example is based on the STM32L0xx ADC LL API; peripheral initialization done using LL unitary services functions for optimization purpose (performance and size). | - | - | - | X | - | - | ||
ADC_Oversampling |
This example describes how to use a ADC peripheral with ADC oversampling; This example is based on the STM32L0xx ADC LL API; peripheral initialization done using LL unitary services functions for optimization purpose (performance and size). | - | - | - | X | - | - | ||
ADC_SingleConversion_TriggerSW |
This example describes how to use a ADC peripheral to perform a single ADC conversion of a channel, at each software start; Example using programming model: polling (for programming models interrupt or DMA transfer, refer to other examples); This example is based on the STM32L0xx ADC LL API; peripheral initialization done using LL unitary services functions for optimization purpose (performance and size). | - | - | - | X | - | - | ||
ADC_SingleConversion_TriggerSW_DMA |
This example describes how to use a ADC peripheral to perform a single ADC conversion of a channel, at each software start; Example using programming model: DMA transfer (for programming models polling or interrupt, refer to other examples); This example is based on the STM32L0xx ADC LL API; peripheral initialization done using LL unitary services functions for optimization purpose (performance and size). | - | - | - | X | - | - | ||
ADC_SingleConversion_TriggerSW_IT |
This example describes how to use a ADC peripheral to perform a single ADC conversion of a channel, at each software start; Example using programming model: interrupt (for programming models polling or DMA transfer, refer to other examples); This example is based on the STM32L0xx ADC LL API; peripheral initialization done using LL unitary services functions for optimization purpose (performance and size). | - | - | - | X | - | - | ||
ADC_SingleConversion_TriggerTimer_DMA |
This example describes how to use a ADC peripheral to perform a single ADC conversion of a channel, at each trigger event from timer; Conversion data are transferred by DMA into a table, indefinitely (circular mode); This example is based on the STM32L0xx ADC LL API; peripheral initialization done using LL unitary services functions for optimization purpose (performance and size). | - | - | - | X | - | - | ||
ADC_TemperatureSensor |
This example describes how to use a ADC peripheral to perform a single ADC conversion of the internal temperature sensor and to calculate the temperature in Celsius degrees; Example using programming model: polling (for programming models interrupt or DMA transfer, refer to other examples); This example is based on the STM32L0xx ADC LL API; peripheral initialization done using LL unitary services functions for optimization purpose (performance and size). | - | - | - | X | - | - | ||
COMP |
COMP_CompareWithInternalReference_IT |
This example shows how to use a comparator peripheral to compare a voltage level applied on a GPIO pin versus the internal voltage reference (VrefInt), in interrupt mode; This example is based on the STM32L0xx COMP LL API; peripheral initialization done using LL unitary services functions for optimization purpose (performance and size). | - | - | - | X | - | - | |
COMP_CompareWithInternalReference_IT_Init |
This example shows how to use a comparator peripheral to compare a voltage level applied on a GPIO pin versus the internal voltage reference (VrefInt), in interrupt mode; This example is based on the STM32L0xx COMP LL API; peripheral initialization done using LL initialization function to demonstrate LL init usage. | - | - | - | X | - | - | ||
CORTEX |
CORTEX_MPU |
This example presents the MPU feature. Its purpose is to configure a memory area as privileged read-only area and attempt to perform read and write operations in different modes. | - | - | - | X | - | - | |
CRC |
CRC_CalculateAndCheck |
This example shows how to configure CRC calculation unit to get a CRC code of a given data buffer, based on a fixed generator polynomial (default value 0x4C11DB7). Peripheral initialization done using LL unitary services functions for optimization purpose (performance and size). | - | - | - | X | - | - | |
CRC_UserDefinedPolynomial |
This example shows how to configure and use CRC calculation unit to get a 8-bit long CRC of a given data buffer, based on a user-defined generating polynomial. Peripheral initialization done using LL unitary services functions for optimization purpose (performance and size). | - | - | - | X | - | - | ||
CRS |
CRS_Synchronization_IT |
This example describes how to configure Clock Recovery Service in IT mode through the STM32L0xx CRS LL API. Peripheral initialization done using LL unitary services functions for optimization purpose (performance and size). | - | - | - | X | - | - | |
CRS_Synchronization_Polling |
This example describes how to configure Clock Recovery Service in polling mode through the STM32L0xx CRS LL API. Peripheral initialization done using LL unitary services functions for optimization purpose (performance and size). | - | - | - | X | - | - | ||
DAC |
DAC_GenerateConstantSignal_TriggerSW |
This example describes how to use the DAC peripheral to generate a constant voltage signal; This example is based on the STM32L0xx DAC LL API; peripheral initialization done using LL unitary services functions for optimization purpose (performance and size). | - | - | - | X | - | - | |
DAC_GenerateWaveform_TriggerHW |
This example describes how to use the DAC peripheral to generate a waveform voltage from digital data stream transfered by DMA; This example is based on the STM32L0xx DAC LL API; peripheral initialization done using LL unitary services functions for optimization purpose (performance and size). | - | - | - | X | - | - | ||
DAC_GenerateWaveform_TriggerHW_Init |
This example describes how to use the DAC peripheral to generate a waveform voltage from digital data stream transfered by DMA; This example is based on the STM32L0xx DAC LL API; peripheral initialization done using LL initialization function to demonstrate LL init usage. | - | - | - | X | - | - | ||
DMA |
DMA_CopyFromFlashToMemory |
This example describes how to use a DMA channel to transfer a word data buffer from Flash memory to embedded SRAM. Peripheral initialization done using LL unitary services functions for optimization purpose (performance and size). | - | - | - | X | - | - | |
DMA_CopyFromFlashToMemory_Init |
This example describes how to use a DMA channel to transfer a word data buffer from Flash memory to embedded SRAM. Peripheral initialization done using LL initialization function to demonstrate LL init usage. | - | - | - | X | - | - | ||
EXTI |
EXTI_ToggleLedOnIT |
This example describes how to configure the EXTI and use GPIOs using the STM32L0xx LL API to toggles the available users LEDs on the board when User button is pressed. Peripheral initialization done using LL unitary services functions for optimization purpose (performance and size). | - | - | - | X | - | - | |
EXTI_ToggleLedOnIT_Init |
This example describes how to configure the EXTI and use GPIOs using the STM32L0xx LL API to toggles the available users LEDs on the board when User button is pressed. Peripheral initialization done using LL initialization function to demonstrate LL init usage. | - | - | - | X | - | - | ||
GPIO |
GPIO_InfiniteLedToggling |
This example describes how to configure and use GPIOs through the LL API to toggles the available users LEDs on the board each 250 ms. Peripheral initialization done using LL unitary services functions for optimization purpose (performance and size). | - | - | - | X | - | - | |
GPIO_InfiniteLedToggling_Init |
This example describes how to configure and use GPIOs through the LL API to toggles the available users LEDs on the board each 250 ms. Peripheral initialization done using LL initialization function to demonstrate LL init usage. | - | - | - | X | - | - | ||
I2C |
I2C_OneBoard_AdvCommunication_DMAAndIT |
This example describes how to exchange some datas between an I2C Master device using DMA mode and an I2C Slave device using IT mode. Peripheral initialization done using LL unitary services functions for optimization purpose (performance and size). | - | - | - | X | - | - | |
I2C_OneBoard_Communication_DMAAndIT |
This example describes how to transmit some data bytes from an I2C Master device using DMA mode to an I2C Slave device using IT mode. Peripheral initialization done using LL unitary services functions for optimization purpose (performance and size). | - | - | - | X | - | - | ||
I2C_OneBoard_Communication_IT |
This example describes how to receive data byte from an I2C Slave device using IT mode to an I2C Master device using IT mode. Peripheral initialization done using LL unitary services functions for optimization purpose (performance and size). | - | - | - | X | - | - | ||
I2C_OneBoard_Communication_IT_Init |
This example describes how to receive data byte from an I2C Slave device using IT mode to an I2C Master device using IT mode. Peripheral initialization done using LL initialization function to demonstrate LL init usage. | - | - | - | X | - | - | ||
I2C_OneBoard_Communication_PollingAndIT |
This example describes how to transmit data bytes from an I2C Master device using Polling mode to an I2C Slave device using IT mode. Peripheral initialization done using LL unitary services functions for optimization purpose (performance and size). | - | - | - | X | - | - | ||
I2C_TwoBoards_MasterRx_SlaveTx_IT |
This example describes how to receive data byte from an I2C Slave device using IT mode to an I2C Master device using IT mode. Peripheral initialization done using LL unitary services functions for optimization purpose (performance and size). | - | - | - | X | - | - | ||
I2C_TwoBoards_MasterTx_SlaveRx |
This example describes how to transmit some data bytes from an I2C Master device using Polling mode to an I2C Slave device using IT mode. Peripheral initialization done using LL unitary services functions for optimization purpose (performance and size). | - | - | - | X | - | - | ||
I2C_TwoBoards_MasterTx_SlaveRx_DMA |
This example describes how to transmit some data bytes from an I2C Master device using DMA mode to an I2C Slave device using DMA mode. Peripheral initialization done using LL unitary services functions for optimization purpose (performance and size). | - | - | - | X | - | - | ||
I2C_TwoBoards_WakeUpFromStop_IT |
This example describes how to receive data byte from an I2C Slave device in Stop mode using IT mode to an I2C Master device using IT mode. Peripheral initialization done using LL unitary services functions for optimization purpose (performance and size). | - | - | - | X | - | - | ||
IWDG |
IWDG_RefreshUntilUserEvent |
This example describes how to configure the IWDG and insure counter update at regular period and generating an MCU IWDG reset at User Button pressed. Peripheral initialization done using LL unitary services functions for optimization purpose (performance and size). | - | - | - | X | - | - | |
LPTIM |
LPTIM_PulseCounter |
This example describes how to use the LPTIM in counter mode to generate a PWM output signal and update PWM duty cycle, based on a trigger provided by an external function generator. This example is based on the STM32L0xx LPTIM LL API; peripheral initialization is done using LL unitary services functions for optimization purpose (performance and size). | - | - | - | X | - | - | |
LPTIM_PulseCounter_Init |
This example describes how to use the LPTIM in counter mode to generate a PWM output signal and update PWM duty cycle, based on a trigger provided by an external function generator. This example is based on the STM32L0xx LPTIM LL API; peripheral initialization is done using LL initialization function to demonstrate LL init usage. | - | - | - | X | - | - | ||
LPUART |
LPUART_WakeUpFromStop |
This example shows how to configure GPIO and LPUART peripherals to allow characters received on LPUART RX pin, to wake up MCU from low power mode; This example is based on STM32L0xx LPUART LL API; Peripheral initialization is done using LL unitary services functions for optimization purpose (performance and size). | - | - | - | X | - | - | |
LPUART_WakeUpFromStop_Init |
This example shows how to configure 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 STM32L0xx LPUART LL API; Peripheral initialization is done using LL initialization function to demonstrate LL init usage. | - | - | - | X | - | - | ||
PWR |
PWR_EnterStandbyMode |
This example shows how to enter the system in STANDBY mode and wake-up from this mode using external RESET or wake-up interrupt. | - | - | - | X | - | - | |
PWR_EnterStopMode |
This example shows how to enter the system in STOP mode. | - | - | - | X | - | - | ||
PWR_LPRunMode_SRAM1 |
This example shows how to execute code (LowPowerRun Mode) from SRAM1. | - | - | - | X | - | - | ||
PWR_OptimizedRunMode |
This example shows how to increase/decrease Frequency and Vcore and how to enter/exit LowPowerRun Mode. | - | - | - | X | - | - | ||
RCC |
RCC_OutputSystemClockOnMCO |
This example describes how to configure MCO pin (PA8) to output the system clock. | - | - | - | X | - | - | |
RCC_UseHSEasSystemClock |
This example describes how to use the RCC LL API how to start the HSE and use it as system clock. | - | - | - | X | - | - | ||
RCC_UseHSI_PLLasSystemClock |
This example shows how to modify the PLL parameters in run time. | - | - | - | X | - | - | ||
RNG |
RNG_GenerateRandomNumbers |
This example shows how to configure RNG peripheral to allow generation of 32-bit long Random Numbers. Peripheral initialization done using LL unitary services functions for optimization purpose (performance and size). | - | - | - | X | - | - | |
RNG_GenerateRandomNumbers_IT |
This example shows how to configure RNG peripheral to allow generation of 32-bit long Random Numbers, using interrupts. Peripheral initialization done using LL unitary services functions for optimization purpose (performance and size). | - | - | - | X | - | - | ||
RTC |
RTC_Alarm |
This example guides you through the different configuration steps by mean of LL API to ensure Alarm configuration and generation using the RTC peripheral. Peripheral initialization done using LL unitary services functions for optimization purpose (performance and size). | - | - | - | X | - | - | |
RTC_Alarm_Init |
This example guides you through the different configuration steps by mean of LL API to ensure Alarm configuration and generation using the RTC peripheral. Peripheral initialization done using LL initialization function to demonstrate LL init usage. | - | - | - | X | - | - | ||
RTC_Calendar |
This example guides you through the different configuration steps by mean of HAL API to configure the RTC calendar. Peripheral initialization done using LL unitary services functions for optimization purpose (performance and size). | - | - | - | X | - | - | ||
RTC_ExitStandbyWithWakeUpTimer |
This example shows how to configure the RTC in order to wakeup system from standby mode using RTC Wakeup Timer. Peripheral initialization is done using LL unitary services functions for optimization purpose (performance and size). | - | - | - | X | - | - | ||
RTC_ProgrammingTheWakeUpTimer |
This example shows how to configure the RTC in order to work with the WUT. Peripheral initialization done using LL unitary services functions for optimization purpose (performance and size). | - | - | - | X | - | - | ||
RTC_Tamper |
This example guides you through the different configuration steps by mean of LL API to ensure Tamper configuration using the RTC peripheral. Peripheral initialization done using LL unitary services functions for optimization purpose (performance and size). | - | - | - | X | - | - | ||
RTC_TimeStamp |
This example guides you through the different configuration steps by mean of LL API to ensure Time Stamp configuration using the RTC peripheral. Peripheral initialization done using LL unitary services functions for optimization purpose (performance and size). | - | - | - | X | - | - | ||
SPI |
SPI_OneBoard_HalfDuplex_DMA |
This example shows how to configure GPIO and SPI peripherals for transmitting bytes from an SPI Master device to an SPI Slave device by using DMA mode through the STM32L0xx SPI LL API. Peripheral initialization done using LL unitary services functions for optimization purpose (performance and size). | - | - | - | X | - | - | |
SPI_OneBoard_HalfDuplex_DMA_Init |
This example shows how to configure GPIO and SPI peripherals for transmitting bytes from an SPI Master device to an SPI Slave device by using DMA mode through the STM32L0xx SPI LL API. Peripheral initialization done using LL initialization function to demonstrate LL init usage. | - | - | - | X | - | - | ||
SPI_OneBoard_HalfDuplex_IT |
This example shows how to configure GPIO and SPI peripherals for transmitting bytes from an SPI Master device to an SPI Slave device by using IT mode through the STM32L0xx SPI LL API. Peripheral initialization done using LL unitary services functions for optimization purpose (performance and size). | - | - | - | X | - | - | ||
SPI_TwoBoards_FullDuplex_DMA |
This example shows how to ensure SPI Data buffer transmission and reception using DMA mode through the STM32L0xx SPI LL API. Peripheral initialization done using LL unitary services functions for optimization purpose (performance and size). | - | - | - | X | - | - | ||
SPI_TwoBoards_FullDuplex_IT |
This example shows how to ensure SPI Data buffer transmission and reception using Interrupt mode through the STM32L0xx SPI LL API. Peripheral initialization done using LL unitary services functions for optimization purpose (performance and size). | - | - | - | X | - | - | ||
TIM |
TIM_DMA |
This example provides a description of how to use DMA with TIMER update request to transfer Data from memory to TIMER Capture Compare Register 3 (TIMx_CCR3); Example using the STM32L0xx TIM LL API, peripheral initialization done using LL unitary services functions for optimization purpose (performance and size). | - | - | - | X | - | - | |
TIM_InputCapture |
This example shows how to use the TIM peripheral to measure the frequency of a periodic signal provided either by an external signal generator or by another timer instance; Example using the STM32L0xx TIM LL API, peripheral initialization done using LL unitary services functions for optimization purpose (performance and size). | - | - | - | X | - | - | ||
TIM_OnePulse |
This example shows how to configure a timer to generate a positive pulse in Output Compare mode with a length of tPULSE and after a delay of tDELAY; This example is based on the STM32L0xx TIM LL API; peripheral initialization is done using LL unitary services functions for optimization purpose (performance and size). | - | - | - | X | - | - | ||
TIM_OutputCompare |
This example shows how to configure the TIM peripheral to generate an output waveform in different output compare modes; Example using the STM32L0xx TIM LL API, peripheral initialization done using LL unitary services functions for optimization purpose (performance and size). | - | - | - | X | - | - | ||
TIM_PWMOutput |
This example describes how to use a timer peripheral to generate a PWM output signal and update PWM duty cycle; Example using the STM32L0xx TIM LL API, peripheral initialization done using LL unitary services functions for optimization purpose (performance and size). | - | - | - | X | - | - | ||
TIM_PWMOutput_Init |
This example describes how to use a timer peripheral to generate a PWM output signal and update PWM duty cycle; Example using the STM32L0xx TIM LL API, peripheral initialization done using LL initialization function to demonstrate LL init usage. | - | - | - | X | - | - | ||
TIM_TimeBase |
This example shows how to configure the TIM peripheral to generate a time base; Example using the STM32L0xx TIM LL API, peripheral initialization done using LL unitary services functions for optimization purpose (performance and size). | - | - | - | X | - | - | ||
USART |
USART_Communication_Rx_IT |
This example shows how to configure GPIO and USART peripheral for receiving characters from HyperTerminal (PC) in Asynchronous mode using IT. Peripheral initialization done using LL unitary services functions for optimization purpose (performance and size). | - | - | - | X | - | - | |
USART_Communication_Rx_IT_Continuous |
This example shows how to configure GPIO and USART peripheral for continuously receiving characters from HyperTerminal (PC) in Asynchronous mode using IT. Peripheral initialization done using LL unitary services functions for optimization purpose (performance and size). | - | - | - | X | - | - | ||
USART_Communication_Rx_IT_Init |
This example shows how to configure GPIO and USART peripheral for receiving characters from HyperTerminal (PC) in Asynchronous mode using IT. Peripheral initialization done using LL initialization function to demonstrate LL init usage. | - | - | - | X | - | - | ||
USART_Communication_Tx |
This example shows how to configure GPIO and USART peripherals to send characters asynchronously to an HyperTerminal (PC) in Polling mode. If the transfer could not be completed within the allocated time, a timeout allows to exit from the sequence with a Timeout error code; This example is based on STM32L0xx USART LL API; Peripheral initialization done using LL unitary services functions for optimization purpose (performance and size). | - | - | - | X | - | - | ||
USART_Communication_TxRx_DMA |
This example shows how to configure GPIO and USART peripheral to send characters asynchronously to/from an HyperTerminal (PC) in DMA mode; This example is based on STM32L0xx USART LL API; Peripheral initialization done using LL unitary services functions for optimization purpose (performance and size). | - | - | - | X | - | - | ||
USART_Communication_Tx_IT |
This example shows how to configure GPIO and USART peripheral to send characters asynchronously to HyperTerminal (PC) in Interrupt mode; This example is based on STM32L0xx USART LL API; Peripheral initialization done using LL unitary services functions for optimization purpose (performance and size). | - | - | - | X | - | - | ||
USART_HardwareFlowControl |
This example shows how to configure GPIO and USART peripheral to receive characters asynchronously from HyperTerminal (PC) in Interrupt mode with Hardware Flow Control feature enabled; This example is based on STM32L0xx USART LL API; Peripheral initialization done using LL unitary services functions for optimization purpose (performance and size). | - | - | - | X | - | - | ||
USART_SyncCommunication_FullDuplex_DMA |
This example shows how to configure GPIO, USART, DMA and SPI peripherals for transmitting bytes from/to an USART peripheral to/from an SPI peripheral (in slave mode) by using DMA mode through the STM32L0xx USART LL API. Peripheral initialization done using LL unitary services functions for optimization purpose (performance and size). | - | - | - | X | - | - | ||
USART_SyncCommunication_FullDuplex_IT |
This example shows how to configure GPIO, USART, DMA and SPI peripherals for transmitting bytes from/to an USART peripheral to/from an SPI peripheral (in slave mode) by using IT mode through the STM32L0xx USART LL API (SPI is using DMA for receving/transmitting characters sent from/received by USART). Peripheral initialization done using LL unitary services functions for optimization purpose (performance and size). | - | - | - | X | - | - | ||
USART_WakeUpFromStop |
This example shows how to configure GPIO and USART peripherals for allowing characters received on USART RX pin, to wake Up MCU from low power mode, using STM32L0xx USART LL API. Peripheral initialization done using LL unitary services functions for optimization purpose (performance and size). | - | - | - | X | - | - | ||
UTILS |
UTILS_ConfigureSystemClock |
This example describes how to use UTILS LL API to configure the system clock using PLL with HSI as source clock. The user application just needs to calculate PLL parameters using STM32CubeMX and call the UTILS LL API. | - | - | - | X | - | - | |
UTILS_ReadDeviceInfo |
This example describes how to Read UID, Device ID and Revision ID and save them into a global information buffer. | - | - | - | X | - | - | ||
WWDG |
WWDG_RefreshUntilUserEvent |
This example describes how to configure WWDG and update counter at regular period and generating an MCU WWDG reset at User Button pressed. Peripheral initialization done using LL unitary services functions for optimization purpose (performance and size). | - | - | - | X | - | - | |
| Total number of examples_ll: 82 | 0 | 0 | 0 | 82 | 0 | 0 | |||
Examples_MIX |
ADC |
ADC_SingleConversion_TriggerSW_IT |
This example describes how to use a ADC peripheral to perform a single ADC conversion of a channel, at each software start; Example using programming model: interrupt (for programming models polling or DMA transfer, refer to other examples); This example is based on the STM32L0xx ADC HAL & LL API (LL API used for performance improvement). | - | - | - | X | - | - |
CRC |
CRC_PolynomialUpdate |
This example provides a description of how to use CRC peripheral through the STM32L0xx CRC HAL & LL API (LL API used for performance improvement). | - | - | - | X | - | - | |
DMA |
DMA_FLASHToRAM |
This example provides a description of how to use a DMA to transfer a word data buffer from Flash memory to embedded SRAM through the STM32L0xx DMA HAL & LL API (LL API used for performance improvement). | - | - | - | X | - | - | |
I2C |
I2C_OneBoard_ComSlave7_10bits_IT |
This example describes how to perform I2C data buffer transmission/reception between master and 2 slaves with different Address size (7-bit or 10-bit) through the STM32L0xx HAL & LL API (LL API used for performance improvement), using an interrupt. | - | - | - | X | - | - | |
PWR |
PWR_STANDBY_RTC |
This example shows how to enter the system in STANDBY mode and wake-up from this mode using external RESET or RTC Wake-up Timer through the STM32L0xx RTC & RCC HAL & LL API (LL API used for performance improvement). | - | - | - | X | - | - | |
PWR_STOP |
This example shows how to enter the system in STOP with Low power regulator mode and wake-up from this mode using external RESET or wake-up interrupt (all the RCC functions calls use RCC LL API for footprint and performance improvements). | - | - | - | X | - | - | ||
SPI |
SPI_FullDuplex_ComPolling |
This example shows how to ensure SPI data buffer transmission/reception in Polling mode between two boards. | - | - | - | X | - | - | |
SPI_HalfDuplex_ComPollingIT |
This example shows how to ensure SPI data buffer transmission/reception between two boards by using Polling (LL Driver) an interrupt mode (HAL Driver). | - | - | - | X | - | - | ||
TIM |
TIM_PWMInput |
This example shows how to use the TIM peripheral to measure the frequency and duty cycle of an external signal. | - | - | - | X | - | - | |
UART |
UART_HyperTerminal_IT |
This example describes how to use an UART to transmit data (transmit/receive) between a board and an HyperTerminal PC application in Interrupt mode; This example provides a description of how to use USART peripheral through the STM32L0xx UART HAL & LL API (LL API used for performance improvement). | - | - | - | X | - | - | |
UART_HyperTerminal_TxPolling_RxIT |
This example describes how to use an UART to transmit data (transmit/receive) between a board and an HyperTerminal PC application both in Polling and Interrupt modes; This example provides a description of how to use USART peripheral through the STM32L0xx UART HAL & LL API (LL API used for performance improvement). | - | - | - | X | - | - | ||
| Total number of examples_mix: 11 | 0 | 0 | 0 | 11 | 0 | 0 | |||
Applications |
FatFs |
FatFs_uSD |
This example provides a description on how to use STM32Cube firmware with FatFs middleware component as a generic FAT file system module, in order to develop an application exploiting FatFs offered features with microSD drive configuration. | X | - | - | - | X | - |
FatFs_uSD_RTOS |
This example provides a description on how to use STM32Cube firmware with FatFs middleware component as a generic FAT file system module, in order to develop an application exploiting FatFs offered features with microSD drive in RTOS mode configuration using the SD card available on the Adafruit 1.8" TFT shield and mounted on top of the STM32 Nucleo board. | - | - | - | - | X | - | ||
FreeRTOS |
FreeRTOS_LowPower |
This application shows how to enter and exit low power mode with CMSIS RTOS API. | X | - | X | X | X | X | |
FreeRTOS_LowPower_LPTIM |
This application aims to enter MCU in the STOP mode when all RTOS tasks are suspended. | - | - | - | - | X | - | ||
FreeRTOS_Mail |
This application shows how to use mail queues with CMSIS RTOS API. | X | - | X | X | X | X | ||
FreeRTOS_Mutexes |
This application shows how to use mutexes with CMSIS RTOS API. | X | - | X | X | X | X | ||
FreeRTOS_Queues |
This application shows how to use message queues with CMSIS RTOS API. | X | - | X | X | X | X | ||
FreeRTOS_Semaphore |
This application shows how to use semaphores with CMSIS RTOS API . | X | - | X | X | X | X | ||
FreeRTOS_SemaphoreFromISR |
This application shows how to use semaphore from ISR with CMSIS RTOS API . | X | - | X | X | X | X | ||
FreeRTOS_Signal |
This application shows how to use thread signalling using CMSIS RTOS API. | X | - | X | X | X | X | ||
FreeRTOS_SignalFromISR |
This application shows how to use thread signalling from an interrupt using CMSIS RTOS API. | X | - | X | X | X | X | ||
FreeRTOS_ThreadCreation |
This application shows how to implement a thread creation using CMSIS RTOS API. | X | - | X | X | X | X | ||
FreeRTOS_Timers |
This application shows how to use timers of CMSIS RTOS API. | X | - | 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) using the 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 | - | - | - | - | - | ||
LCD |
LCD_Display_Text |
This example provides a description of how to use the STM32L0xx embedded LCD GLASS controller and how to configures the LCD to display a simple text and activate the different icons. | X | - | - | - | - | - | |
TouchSensing |
TouchSensing_Linear |
This firmware is a basic example on how to use the STMTouch driver with 1 linear sensor. The ECS and DTO are also used. | X | - | - | - | - | X | |
USB_Device |
CDC_Standalone |
This example is a part of the USB Device Library package using STM32Cube firmware. It describes how to use USB device application based on the Device Communication Class (CDC) following the PSTN sub-protocol in the STM32L0xx devices using the USB Device and UART peripherals. | X | - | - | - | - | - | |
DFU_Standalone |
This example is a part of the USB Device Library package using STM32Cube firmware. It describes how to use USB device application based on the Device Firmware Upgrade (DFU) on the STM32L0xx devices. | X | - | - | - | X | X | ||
HID_Standalone |
This example is a part of the USB Device Library package using STM32Cube firmware. This application shows how to use the USB device application based on the Human Interface (HID). | X | - | - | - | X | - | ||
HID_Standalone_BCD |
This example is a part of the USB Device Library package using STM32Cube firmware. This example describes how to use the BCD feature based on the USB HID device application. | X | - | - | - | X | X | ||
HID_Standalone_LPM |
This example describes how to use USB device application based on the Human Interface (HID) with Link Power Management Protocol (LPM) on the STM32L073xx USB FS devices. | X | - | - | - | X | - | ||
HID_TSL_Standalone |
This example is a part of the USB Device Library package using STM32Cube firmware. This example describes how to use USB device application based on the Human Interface (HID). | - | - | - | - | - | X | ||
HID_TSL_Standalone_LPM |
This example describes how to use USB device application based on the Human Interface (HID) with Link Power Management Protocol (LPM) on the STM32L053xx USB FS devices. | - | - | - | - | - | X | ||
MSC_Standalone |
This example is a part of the USB Device Library package using STM32Cube firmware. It describes how to use USB device application based on the Mass Storage Class (MSC) on the STM32L0xx devices. | X | - | - | - | - | - | ||
| Total number of applications: 73 | 21 | 0 | 10 | 10 | 17 | 15 | |||
Demonstrations |
- |
Adafruit_LCD_1_8_SD_Joystick |
The provided demonstration firmware based on STM32Cube helps you to discover STM32 Cortex-M devices that can be plugged on a STM32NUCLEO board. | - | - | - | X | - | - |
Demo |
The provided demonstration firmware based on STM32Cube helps you to discover STM32 Cortex-M devices that can be plugged on a STM32L073Z_EVAL board. | X | - | - | - | X | X | ||
Gravitech_4digits |
The provided demonstration firmware based on STM32Cube helps you to discover STM32 Cortex-M devices that can be plugged on a STM32NUCLEO_32 board. | - | X | X | - | - | - | ||
| Total number of demonstrations: 6 | 1 | 1 | 1 | 1 | 1 | 1 | |||
| Total number of projects: 559 | 100 | 53 | 69 | 170 | 92 | 75 |


You stuttered {{total_number_of_hesitations}} times out of {{total_number_of_words}} words. This gives you an accuracy of {{accuracy}}%.


Supported Interfaces in Xalan-Java
Public interfaces
A public interface of Xalan-Java 2 is an API that a typical client developer should code against. Such interfaces are usually based upon World-Wide Web Consortium (W3C) recommendations, such as XSLT 1.0 and XPath 1.0, or Java Specification Requests (JSR's) with a status of "Final Release", such as JAXP.
The Xalan-Java 2 team will support use of public interfaces, and will attempt to fix severe bugs in such interfaces.
A particular version of a public interface will be supported for all the maintenance drops of a particular version and release of Xalan-Java 2 (that is, for a release that changes just the third digit of the version number). At the point a new version of Xalan-Java 2 is made available, (that is, a release that changes the first or second digit of the version number) such interfaces could change to reflect the latest standard specifications.
The public interfaces of Xalan-Java 2 are:
-
JAXP 1.3
interfaces found in the
javax.xml.parsers
,javax.xml.transform
,org.xml.sax
,org.w3c.dom
andjavax.xml.xpath
packages. - The Xalan-Java 2 specific XPath API, defined by the classes
- API's for using, configuring or defining a serializer, from the
org.apache.xml.serializer
package: - Properties files for configuring a serializer. (See
Setting output
properties in your stylesheets for more information.)
-
org/apache/xml/serializer/output_xml.properties
-
org/apache/xml/serializer/output_html.properties
-
org/apache/xml/serializer/output_text.properties
-
- Command-line interfaces for performing transformations:
Experimental interfaces
Interfaces and classes that are designated experimental reflect recent World-Wide Web Consortium (W3C) draft recommendations or draft Java Specification Requests (JSR's). Such an API is based upon a specification that is subject to change, and so is itself subject to change as the relevant standards body makes changes to the specification.
If and when the specification upon which the API is based reaches its final published form, the API could become a Public interface in a subsequent release of Xalan-Java 2, although the Xalan-Java 2 team could decide to simply withdraw the API, if it decided that making the API a public interface would not be appropriate.
As the name suggests, experimental interfaces are provided in order to give users the opportunity to experiment with new features so that they can provide feed-back on those features. They should not be used in production-level code. The Xalan-Java 2 team may fix severe bugs in experimental interfaces.
The experimental interfaces of Xalan-Java 2 are:
- The
DOM Level 3 XPath API found in the
org.apache.xpath.domapi
package.
Internal interfaces
All other classes are considered to be part of the internal interface of
Xalan-Java 2. Some such classes or members of such classes may themselves
be designated as public
using the Java keyword, but that is
a consequence of the internal organization of Xalan-Java 2.
Users who have complex and specific needs, such as the need to build their own XSLT or XPath processors, might use these internal interfaces, but their use is not supported. In addition these interfaces are subject to change without notice.


Here are the activities offered in our resort
Beach play
whale watching
Sea cave exploration
Kayaking
Cooking classes(culinary classes)
Surfing
Back to our home page
Home


Angelina Jolie still bitter over Brad Pitt
- Advertisement -
Oscar-winner Angelina Jolie is reportedly bitter over her ex, Ad Astra star Brad Pitt.
An insider for USWeekly said Angelina still has a lot of resentment toward Brad.
Angelina feels bitter towards Brad because he turned the lives of their six children – Maddox, 18, Pax, 15, Zahara, 14, Shiloh, 13, and 11-year-old twins Knox and Vivienne – upside down. And she wants him to be accountable for that.
It was reported that she told Harper’s Bazaar she has to stay in LA because of Brad.
- Advertisement -
In September 2016, the couple called it quits, but she still did not want to be friends with Brad.
The daughter of Jon Voight did not want to marry the 55-year-old Oklahoma native in the first place and she said she is never going to get married anymore.
An insider told UsWeekly that Angelina is not letting go.
According to reports as saying, the 44-year-old actress is currently shooting a Marvel in Spain and she loves to live abroad but has to live where Brad is for the sake of their kids.
It is reported that Angelina is lashing out at Brad, depicting him as calling all the shots and deciding the beauty’s fate even though she has her own life and career.
An insider shared that the family used to lead a nomadic existence before the divorce because of Angelina’s restlessness.
The insider added that Brad wanted stability for the kids while Angelina wanted to give them an idyllic childhood by showing them different countries, languages and experiences.
The couple has not been photographed together since September 2016 after they broke up due to irreconcilable differences.
Their divorce has is not finalised but they share physical and legal custody of their children.
In 2014, Brad pressured Angelina to get married at their home in France. It is reported that Angelina doesn’t want to get married again.
The Maleficent star has not been dating ever since leaving Brad while Brad has been dating jewellery designer and holistic healer Sat Hari Khalsa, 50.
- Advertisement -


Reports an HTML element without a closing tag. Some coding styles require that HTML elements have closing tags even where this is optional.


Run all of these if you haven't already in order to get the courses and be able to read them offline. Clicking on them anytime after the first time will just update them
Important! After clicking wait for about 10-50 seconds until the courses have been downloaded.
A notification is going to popup once everything is done.
You need internet connection for that.
After that, wait while the database is being updated.
If you skip this page everything is going to work apart from offline functionality.


Terminals for netbeans
This module provides terminal services inside netbeans.
It does so at several levels:
-
Actions to start a terminal running a shell or a command of users choice
in a default terminal TopComponent.
The actions are tentatively placed under the Run menu.
-
API for creating a Terminal and running a Program under it.
See the class comment for {@link org.netbeans.modules.terminal.api.Terminal} for an example.
-
API for constructing custom TopComponents for harboring Terminals.
See the class comment for {@link org.netbeans.modules.terminal.api.TerminalContainer} for an example
of how to do this.
-
An alternative implementation of NetBeans's standard {@link org.openide.windows.IOProvider} API.
See the class comment for {@link org.netbeans.modules.terminal.ioprovider.TerminalIOProvider} for an example
of how to aquire such a service.
See the class comment for {@link org.netbeans.modules.terminal.ioprovider.TerminalInputOutput} for a
discussion of how to take extra advantage of the underlying
{@link org.netbeans.lib.terminalemulator.Term}.


| Category | Recipe | Description | Key Parameters | Sample devops pipelines |
|---|---|---|---|---|
| Continuous Integration | Publish a batch inference pipeline | Publishes a batch inference pipeline to the workspace & optionally runs it |
|
|
| Register Pretrained Model | Register a pretrained model stored in the repo (supports git lfs i.e. large file system) |
Accept & gracefully handle null values on additional params: model framework, framework version, sample input & output dataset |
||
| Register Model from run metadata file | Register a model from a metadata file from a training run in Azure ML |
It also outputs the model-metadata (output of model registration) into the devops pipeline. This can be used by downstream tasks like deploy. |
||
| Run functional tests on service endpoint | Run functional tests using newman (postman's cli version) and publishes the test results to Devops pipeline |
|
||
| Run training in the cloud | Run the training in the specified cluster and publish the run metadata for optional downstream consumption in devops pipeline |
|
||
| Continuous Deloyment | Deploy to ACI from Registered Model | Given model name and version, this recipe deploys a registered model to Azure Container Instance |
|
|
| Deploy to ACI from Metadata | Deploy a registered model from model metadata file (output of model registration) to ACI |
|
||
| Deploy to AKS from Registered Model | Given aks cluster, model name and version, this recipe deploys a registered model to Azure Kubernetes Service |
|
||
| Deploy to AKS from Metadata | Deploy a registered model from model metadata file (output of model registration) to AKS |
|
||
| Run pipeline | Runs a specified published pipeline |
|
Batch Inference recipe uses this under the hood. Refer to it. | |
| IaC (Infrastructure as Code) | Provision ML workspace | Provisions a new ML workspace along with a Azure ML compute cluster and AKS cluster. Also provisions Storage account, ACR, KeyVault & App insights | It sources the parameters through recipes/common/Variables.yml and recipes/IaC/arm/IaCAzureResourceManager.json | |
| Tear down a resource group | Tear down a resource group along with all its resources (workspace, clusters etc) |
It sources the parameters through recipes/common/Variables.yml. It primarily needs service connection name, resource group name and location. |
||
| Provision AKS Cluster | Provisions a AKS cluster from Azure ML workspace |
Note: Recipe is being updated to add more parameters |
||
| Provision Azure ML Compute | Provisions Azure ML compute |
|


This page documents version 2.0-dev of bingwa, which is currently considered experimental.
Introduction. bingwa is a command-line tool used to carry out meta-analysis of genome-wide association studies. It is particularly suited for use with the program SNPTEST, but can also be used with other association testing programs such as MMM. Features of bingwa include:
- Direct support for SNPTEST output files.
- Support for fixed-effect frequentist and a flexible bayesian meta-analysis method.
- Support for both univariate and multivariate meta-analysis (including support for meta-analysing tests performed using SNPTEST's multinomial test).
Disclaimer. This page documents version 2.0-dev of bingwa which is currently considered experimental. This means we expect some features not to work, or not to work well, or to work wrongly, or to destroy your computer or sanity.
References. If you make use of bingwa, please cite the following paper, which describes the key methodology underlying the program:
- "Imputation-Based Meta-Analysis of Severe Malaria in Three African Populations", Band et al, PLOS Genetics (2013)
Similar methodology was also developed in these papers:
- "Genome-wide association study identifies a variant in HDAC9 associated with large vessel ischemic stroke", International Stroke Genetics Consortium (ISGC) and Wellcome Trust Case Control Consortium 2 (WTCCC2), Nat. Genetics (2012)
- "Reappraisal of known malaria resistance loci in a large multi-centre study", Rockett et al, Nat. Genetics (2014).
Acknowledgements. Bingwa was developed at the Wellcome Trust Centre for Human Genetics, Oxford, UK. A full list of people who contributed to the methodology will appear here.
The general process followed by bingwa is shown on the right. In brief, bingwa proceeds by
- Loading association test data from a set of cohorts (e.g. SNPTEST files).
- Matching variants between cohorts.
- Computing frequentist meta-analysis and one or more Bayes factors.
- Writing results.
We'll update this page with more details on the method soon. In the meantime the tutorial has usage examples.
Running bingwa
-flat-file
to write a flat file instead.
Flat files are space, tab or comma-delimited according to the filename extension.
sd=0.2,0.2/cor=1,1,1:bf
.
fixed:bf
and independent:bf
columns.
Here, the independent model assumes that true effects are uncorrelated between the cohorts - i.e.
they have diagonal variance-covariance matrix.
In addition to the two model-specific bayes factors, bingwa will compute a model-averaged bayes factor
over all the models specified, named mean_bf
.
-prior-weights
option to reweight them. Weights are renormalised to sum to one in the mean bayes factor computation - i.e.
the mean Bayes factor is computed as
$$\text{BF}_{\text{avg}} = \frac{\sum_i \text{weight}_i \cdot \text{BF}_i}{\sum_i \text{weight}_i}$$
where $\text{weight}_i$ and $\text{BF}_i$ are the specified weight and Bayes factor for model $i$.
If -prior-weights
is specified, any model not specified in the argument is given weight zero in the mean Bayes factor.
-priors
option can be used to tell bingwa to load priors
from a file instead of the command-line. Prior files additionally allow for comments and use of
whitespace. See file formats page for the
format of this file. For example, the above priors could be specified
-extra-variables
option tells bingwa to output a given set of columns
in the output.
Understanding bingwa sqlite output files
Below we've given some examples of using the shell or various programming languages to extract data from a bingwa
sqlite file.
We assume the file is named bingwa.sqlite
and the meta-analysis results were stored
in the MetaAnalysis
table.
Note: The sqlite3
program is installed by default on most UNIX-like systems.
It's quite flexible, and can be used in interactive mode, or to run queries directly from the command-line.
We'll use both methods below.
See the sqlite3 command shell documentation for a full list of options.
Inspecting the contents of the results file
sqlite files can be inspected using the sqlite3 command shell. Open the file by typing:
$ sqlite3 -column -header bingwa.sqlite
You should see the sqlite prompt (sqlite3>
). Let's see what tables are stored in this file:
sqlite3> .tables Analysis Entity MetaAnalysis AnalysisProperty EntityData MetaAnalysisView AnalysisPropertyView EntityDataView Variant AnalysisStatus EntityRelationship VariantIdentifier AnalysisStatusView EntityRelationshipView VariantView
Here, the main results are stored in the MetaAnalysis
table,
and bingwa has also created the MetaAnalysisView
view which provides a nicer view of the results.
(The -table-name
option can be used to change the name of the main results table.
By default it is a name of the form Analysis<n>
, where n is an integer.)
The Analysis*
and Entity*
tables are used to store
metadata about the analyses you have run. Let's see what's stored in this file:
sqlite> SELECT * FROM Analysis ; id name chunk ---------- --------------- ---------- 1 bingwa analysis NA sqlite> SELECT COUNT(*) AS count FROM MetaAnalysisView count ------- 200
So this file stores meta-analysis results for 200 variants from a single analysis called "bingwa analysis".
In a large, real analysis, it's often useful to use the -analysis-name
and -analysis-chunk
options to give the analysis a
more descriptive name and explain what part of the data it corresponds to. It's possible to store several analyses in the same sqlite file
(or even in the same table, provided analysis columns are compatible), so this information becomes important to understand the results.
Let's have a look at what the results actually look like. Because there are lots of columns we'll switch sqlite3 to line-based output:
sqlite3> .mode line sqlite3> SELECT * FROM MetaAnalysisView LIMIT 1 ; rsid = KGP1 alleleA = A alleleB = G analysis = bingwa analysis analysis_id = 1 variant_id = 1 chromosome = NA position = 1000 cohort 1:A = 0.0 cohort 1:B = 0.0 cohort 1:AA =<PHONE_NUMBER>89648 cohort 1:AB =<PHONE_NUMBER>93164 cohort 1:BB = 87.870002746582 cohort 1:NULL = 0.0 cohort 1:B_allele_frequency = 0.418490950302478 cohort 1:maf = 0.418489992618561 cohort 1:ml_beta_1 = 0.100000001490116 cohort 1:ml_se_1 = 0.0199999995529652 cohort 1:pvalue = 0.100000001490116 cohort 1:info = 0.374507993459702 cohort 2:A = 0.0 cohort 2:B = 0.0 cohort 2:AA =<PHONE_NUMBER>51758 cohort 2:AB =<PHONE_NUMBER>27539 cohort 2:BB = 71.2190017700195 cohort 2:NULL = 0.0 cohort 2:B_allele_frequency = 0.394207201652197 cohort 2:maf = 0.394199997186661 cohort 2:ml_beta_1 = 0.0799999982118607 cohort 2:ml_se_1 = 0.0199999995529652 cohort 2:pvalue = 0.94200998544693 cohort 2:info = 0.97086101770401 FixedEffectMetaAnalysis:beta_1 = 0.0899999998509884 FixedEffectMetaAnalysis:se_1 = 0.0141421353076296 FixedEffectMetaAnalysis:wald_pvalue_1 = 1.96615875463349e-10 FixedEffectMetaAnalysis:pvalue = 1.96615875463348e-10
This analysis contains the results of a fixed-effect frequentist analysis of two cohorts, by default called "cohort 1" and "cohort 2". The results file contains columns reflecting genotype counts and model fits in each cohort, and columns containing meta-analysed effect size estimate, standard error, and a two-tailed fixed-effect meta-analysis P-value.
Note: the -cohort-names
option can be used to name the cohorts in a more useful way.
Processing bingwa sqlite output files
Below are some example commands that process bingwa output in the command-line or in R. See above for a full description of bingwa's sqlite output.
01
, 02
, etc.
> library( RSQLite )
> db = dbConnect( dbDriver( "SQLite" ), "bingwa.sqlite" )
> D = dbGetQuery( db, "SELECT * FROM MetaAnalysisView" )
Input file formats
.txt
, .csv
or .tsv
).
Output file formats
Bingwa can either output to a flat file or to a table in a sqlite database. Both have pros and cons.
Flat files are simple and easy to use. However, they can become difficult to read from for very large analyses (such as genome-wide analyses of datasets imputed into recent reference panels) which may require writing special file-handling code.
Flat files are written when the -flat-file
option is specified.
Sqlite files are easy to use via the sqlite3 command shell, which is installed on most UNIX-like systems. They can also be read directly from programming languages, e.g. by using the RSQLite package in R or the sqlite3 module in python. An attractive feature is that they are indexed, so that data for specific regions of the genome or specific variants can be easily found. See the examples page for code snippets for processing bingwa-produced sqlite files.
Sqlite is the default output format for bingwa.
Specifying priors
The file format used for the -priors
option follows the following rules.
- Blank lines and lines starting with # (comment lines) are ignored.
- Every other line is part of a prior specification.
- Each prior may optionally start with a name specification of the form
<name>:
. (Unnamed priors are given computed names, but it's usually best to name them.) - Two forms of prior specification are permissible, full and shorthand prior specification.
-
A full prior specification is of the form
sd=<a,b,c,...>/cor=1,x,y,...
. Herea,b,c,...
are real numbers. The number of sds specified must bed
, the number of parameters in all cohorts put together; the number of correlations specified must be equal tod×(d+1)/2
. The values ofsd
specify a diagonal matrix σ with standard deviations on its diagonal, while the values ofcor
specify the upper triangle of a correlation matrix Ρ. The resulting prior is σ×Ρ×σ -
A shorthand prior specification is of the form
tau=<a>/sd=<b,c,d,...>/cor=1,...
. Herea,b,c,...
are real numbers. The number of sds specified must bed
, the number of parameters in each cohort; the number of correlations specified must be equal tod×(d+1)/2
.
Prior may be of the form
[name:]sd=<value2>[,<value2<>,...]/cor=1[,x,y,z...]
Bingwa is available either as binaries or as source code.
Binaries
Pre-compiled binaries are available for the following platforms. (See here for other builds.)
| Version | Platform | File |
|---|---|---|
| v2-dev† | Ubuntu 12.04 x86-64 | bingwa_v2.0-dev-linux-x86_64.tgz |
| v2-dev† | CentOS6.5 x86-64 | bingwa_v2.0-dev-CentOS6.5-x86_64.tgz |
| v2-dev† | Mac OS X | bingwa_v2.0-dev-osx.tgz |
†This version of bingwa is considered experimental.
To run bingwa, download the relevant file and extract it as follows.
$ tar -xzf bingwa_v2.0-dev-[machine].tgz $ cd bingwa_v2.0-dev-[machine] $ ./bingwa_v2.0-dev -help
Source
The source code to bingwa is built as part of the qctool package on bitbucket. See the qctool wiki page for more details.


{% extends "generic.html" %} {% block content %} {% if validlink %}
Please enter (and confirm) your new password
{% else %}The reset link was invalid, likely because it has already been used. please request a new password reset
{% endif %} {% endblock %}


D.4.1.4 StructureDefinition: Example Extension - Mappings
Mappings for the StructureDefinition-template-forecastStatusReason Profile.
Mappings for RIM Mapping (http://hl7.org/v3)
| Example Extension |
| Extension (forecastStatusReason) | |
| id | n/a |
| extension | n/a |
| url | N/A |
| valueCode | N/A |


About: Syncs calendar events to your wearable at the press of a button, using the Wearable DataApi to transmit data such as event time, description, and background image. The DataItems can be deleted individually via an action on the event notifications, or all at once via a button on the companion. When deleted using the notification action, a ConfirmationActivity is used to indicate success or failure.
How to run: Install the Application APK on the companion, and the Wearable APK on the wearable. Start the sample by running the AgendaData application on the companion.
Wearable APIs used: DataApi, NodeApi, WearableListenerService, ConfirmationActivity
Screenshots:


This subpart prescribes policies and procedures with respect to—
(a) Patent and copyright infringement liability;
(b) Royalties;
(c) Security requirements for patent applications containing classified subject matter; and
(d) Patented technology under trade agreements.
(a) Pursuant to 28 U.S.C. 1498, the exclusive remedy for patent or copyright infringement by or on behalf of the Government is a suit for monetary damages against the Government in the Court of Federal Claims. There is no injunctive relief available, and there is no direct cause of action against a contractor that is infringing a patent or copyright with the authorization or consent of the Government (e.g., while performing a contract).
(b) The Government may expressly authorize and consent to a contractor’s use or manufacture of inventions covered by U.S. patents by inserting the clause at 52.227-1, Authorization and Consent.
(c) Because of the exclusive remedies granted in 28 U.S.C. 1498, the Government requires notice and assistance from its contractors regarding any claims for patent or copyright infringement by inserting the clause at 52.227-2, Notice and Assistance, Regarding Patent and Copyright Infringement.
(d) The Government may require a contractor to reimburse it for liability for patent infringement arising out of a contract for commercial items by inserting the clause at FAR 52.227-3, Patent Indemnity.
(a)(1) Insert the clause at 52.227-1, Authorization and Consent, in solicitations and contracts except that use of the clause is—
(i) Optional when using simplified acquisition procedures; and
(ii) Prohibited when both complete performance and delivery are outside the United States.
(2) Use the clause with its Alternate I in all R&D solicitations and contracts for which the primary purpose is R&D work, except that this alternate shall not be used in construction and architect-engineer contracts unless the contract calls exclusively for R&D work.
(3) Use the clause with its Alternate II in solicitations and contracts for communication services with a common carrier and the services are unregulated and not priced by a tariff schedule set by a regulatory body.
(b) Insert the clause at 52.227-2, Notice and Assistance Regarding Patent and Copyright Infringement, in all solicitations and contracts that include the clause at 52.227-1, Authorization and Consent.
(c)(1) Insert the clause at 52.227-3, Patent Indemnity, in solicitations and contracts that may result in the delivery of commercial items, unless—
(i) Part 12 procedures are used;
(ii) The simplified acquisition procedures of Part 13 are used;
(iii) Both complete performance and delivery are outside the United States; or
(iv) The contracting officer determines after consultation with legal counsel that omission of the clause would be consistent with commercial practice.
(2) Use the clause with either its Alternate I (identification of excluded items) or II (identification of included items) if—
(i) The contract also requires delivery of items that are not commercial items; or
(ii) The contracting officer determines after consultation with legal counsel that limitation of applicability of the clause would be consistent with commercial practice.
(3) Use the clause with its Alternate III if the solicitation or contract is for communication services and facilities where performance is by a common carrier, and the services are unregulated and are not priced by a tariff schedule set by a regulatory body.
(d)(1) Insert the clause at 52.227-4, Patent Indemnity—Construction Contracts, in solicitations and contracts for construction or that are fixed-price for dismantling, demolition, or removal of improvements. Do not insert the clause in contracts solely for architect-engineer services.
(2) If the contracting officer determines that the construction will necessarily involve the use of structures, products, materials, equipment, processes, or methods that are nonstandard, noncommercial, or special, the contracting officer may expressly exclude them from the patent indemnification by using the clause with its Alternate I. Note that this exclusion is for items, as distinguished from identified patents (see paragraph (e) of this subsection).
(e) It may be in the Government’s interest to exempt specific U.S. patents from the patent indemnity clause. Exclusion from indemnity of identified patents, as distinguished from items, is the prerogative of the agency head. Upon written approval of the agency head, the contracting officer may insert the clause at 52.227-5, Waiver of Indemnity, in solicitations and contracts in addition to the appropriate patent indemnity clause.
(f) If a patent indemnity clause is not prescribed, the contracting officer may include one in the solicitation and contract if it is in the Government’s interest to do so.
(g) The contracting officer shall not include in any solicitation or contract any clause whereby the Government agrees to indemnify a contractor for patent infringement.
(a) To determine whether royalties anticipated or actually paid under Government contracts are excessive, improper, or inconsistent with Government patent rights the solicitation provision at 52.227-6 requires prospective contractors to furnish royalty information. The contracting officer shall take appropriate action to reduce or eliminate excessive or improper royalties.
(b) If the response to a solicitation includes a charge for royalties, the contracting officer shall, before award of the contract, forward the information to the office having cognizance of patent matters for the contracting activity. The cognizant office shall promptly advise the contracting officer of appropriate action.
(c) The contracting officer, when considering the approval of a subcontract, shall require royalty information if it is required under the prime contract. The contracting officer shall forward the information to the office having cognizance of patent matters. However, the contracting officer need not delay consent while awaiting advice from the cognizant office.
(d) The contracting officer shall forward any royalty reports to the office having cognizance of patent matters for the contracting activity.
(a) When the Government is obligated to pay a royalty on a patent because of an existing license agreement and the contracting officer believes that the licensed patent will be applicable to a prospective contract, the Government should furnish the prospective offerors with—
(1) Notice of the license;
(2) The number of the patent; and
(3) The royalty rate cited in the license.
(b) When the Government is obligated to pay such a royalty, the solicitation should also require offerors to furnish information indicating whether or not each offeror is the patent owner or a licensee under the patent. This information is necessary so that the Government may either—
(1) Evaluate an offeror’s price by adding an amount equal to the royalty; or
(2) Negotiate a price reduction with an offeror when the offeror is licensed under the same patent at a lower royalty rate.
(a) If at any time the contracting officer believes that any royalties paid, or to be paid, under a contract or subcontract are inconsistent with Government rights, excessive, or otherwise improper, the contracting officer shall promptly report the facts to the office having cognizance of patent matters for the contracting activity concerned.
(b) In coordination with the cognizant office, the contracting officer shall promptly act to protect the Government against payment of royalties—
(1) With respect to which the Government has a royalty-free license;
(2) At a rate in excess of the rate at which the Government is licensed; or
(3) When the royalties in whole or in part otherwise constitute an improper charge.
(c) In appropriate cases, the contracting officer in coordination with the cognizant office shall demand a refund pursuant to any refund of royalties clause in the contract (see 27.202-4) or negotiate for a reduction of royalties.
(d) For guidance in evaluating information furnished pursuant to 27.202-1, see 31.205-37. See also 31.109 regarding advance understandings on particular cost items, including royalties.
The clause at 52.227-9, Refund of Royalties, establishes procedures to pay the contractor royalties under the contract and recover royalties not paid by the contractor when the royalties were included in the contractor’s fixed price.
(a)(1) Insert a solicitation provision substantially the same as the provision at 52.227-6, Royalty Information, in—
(i) Any solicitation that may result in a negotiated contract for which royalty information is desired and for which certified cost or pricing data are obtained under 15.403; or
(ii) Sealed bid solicitations only if the need for such information is approved at a level above the contracting officer as being necessary for proper protection of the Government’s interests.
(2) If the solicitation is for communication services and facilities by a common carrier, use the provision with its Alternate I.
(b) If the Government is obligated to pay a royalty on a patent involved in the prospective contract, insert in the solicitation a provision substantially the same as the provision at 52.227-7, Patents—Notice of Government Licensee. If the clause at 52.227-6 is not included in the solicitation, the contracting officer may require offerors to provide information sufficient to provide this notice to the other offerors.
(c) Insert the clause at 52.227-9, Refund of Royalties, in negotiated fixed-price solicitations and contracts when royalties may be paid under the contract. If a fixed-price incentive contract is contemplated, change “price” to “target cost and target profit” wherever it appears in the clause. The clause may be used in cost-reimbursement contracts where agency approval of royalties is necessary to protect the Government’s interests.
(a) Unauthorized disclosure of classified subject matter, whether in patent applications or resulting from the issuance of a patent, may be a violation of 18 U.S.C. 792, et seq. (Chapter 37—Espionage and Censorship), and related statutes, and may be contrary to the interests of national security.
(b) Upon receipt of a patent application under paragraph (a) or (b) of the clause at 52.227-10, Filing of Patent Applications—Classified Subject Matter, the contracting officer shall ascertain the proper security classification of the patent application. If the application contains classified subject matter, the contracting officer shall inform the contractor how to transmit the application to the United States Patent Office in accordance with procedures provided by legal counsel. If the material is classified “Secret” or higher, the contracting officer shall make every effort to notify the contractor within 30 days of the Government’s determination, pursuant to paragraph (a) of the clause.
(c) Upon receipt of information furnished by the contractor under paragraph (d) of the clause at 52.227-10, the contracting officer shall promptly submit that information to legal counsel in order that the steps necessary to ensure the security of the application will be taken.
(d) The contracting officer shall act promptly on requests for approval of foreign filing under paragraph (c) of the clause at 52.227-10 in order to avoid the loss of valuable patent rights of the Government or the contractor.
Insert the clause at 52.227-10, Filing of Patent Applications—Classified Subject Matter, in all classified solicitations and contracts and in all solicitations and contracts where the nature of the work reasonably might result in a patent application containing classified subject matter.
(a) The requirements of this section apply to the use of technology covered by a valid patent when the patent holder is from a country that is a party to the North American Free Trade Agreement (NAFTA).
(b) Article 1709(10) of NAFTA generally requires a user of technology covered by a valid patent to make a reasonable effort to obtain authorization prior to use of the patented technology. However, NAFTA provides that this requirement for authorization may be waived in situations of national emergency or other circumstances of extreme urgency, or for public noncommercial use.
(c) Section 6 of Executive Order 12889, “Implementation of the North American Free Trade Act,” of December 27, 1993, waives the requirement to obtain advance authorization for an invention used or manufactured by or for the Federal Government. However, the patent owner shall be notified in advance whenever the agency or its contractor knows or has reasonable grounds to know, without making a patent search, that an invention described in and covered by a valid U.S. patent is or will be used or manufactured without a license. In cases of national emergency or other circumstances of extreme urgency, this notification need not be made in advance, but shall be made as soon as reasonably practicable.
(d) The contracting officer, in consultation with the office having cognizance of patent matters, shall ensure compliance with the notice requirements of NAFTA Article 1709(10) and Executive Order 12889. A contract award should not be suspended pending notification to the patent owner.
(e) Section 6(c) of Executive Order 12889 provides that the notice to the patent owner does not constitute an admission of infringement of a valid privately-owned patent.
(f) When addressing issues regarding compensation for the use of patented technology, Government personnel should be advised that NAFTA uses the term “adequate remuneration.” Executive Order 12889 equates “remuneration” to “reasonable and entire compensation” as used in 28 U.S.C. 1498, the statute that gives jurisdiction to the U.S. Court of Federal Claims to hear patent and copyright cases involving infringement by the Government.
(g) When questions arise regarding the notice requirements or other matters relating to this section, the contracting officer should consult with legal counsel.
Article 31 of Annex 1C, Agreement on Trade-Related Aspects of Intellectual Property Rights, to GATT (Uruguay Round) addresses situations where the law of a member country allows for use of a patent without authorization, including use by the Government.


Planning a sensible city trip is often not easy. You quickly fall into tourist traps and never get to see the really beautiful corners. With Wanderlust you can compare the tours of many different guides and read the testimonials of former participants. This makes it possible to find the tour that best suits you!
As a travel guide it is often not easy to advertise your tours. Often you don't find the right audience and therefore can't give a satisfaction guarantee. With wanderlust this has an end! Advertise your tour here, share the experiences of your former customers and win new customers who want exactly what you offer!


Scarlett Johansson says she romanticised marriage during relationship with Ryan Reynolds
by Judy PhilanderCape Town - Scarlett Johansson has spoken candidly about her marriage to Ryan Reynolds.
In an interview with Vanity Fair, the Avengers actress opened up about her first marriage to Ryan and the lessons she learnt from the experience.
"The first time I got married I was 23 years old," she said.
"I didn’t really have an understanding of marriage. Maybe I kind of romanticised it, I think, in a way."
The 35-year-old was married to the Canadian actor from 2008 to 2011, after they began dating in 2007, ELLE reports.
"It’s a different part of my life now," she said of that time period.
 I’m able to make more active choices. I’m more present, I think, than I’ve been before."
In 2014 Scarlett found love again with French journalist Romain Dauriac but the pair divorced in 2017 and share a five-year-old daughter named Rose Dorothy, Cosmopolitan reports.
The actress recently announced her engagement to Saturday Night Live actor Colin Jost – even flaunting her new engagement ring on the red carpet.
Speaking about her thoughts on marriage now, she said: "The idea of building a family, making a family, and having that work, I like that idea."
"I think that would be wonderful. I’ve always wanted that. I wanted that also in my marriage to my daughter’s father as well. It just wasn’t the right person. But I like that idea."
(Sources: Vanity Fair , ELLE , Cosmopolitan)


?A
1
THE
NEW
YORK
BOTANICAL
GARDEN
EXPLORATION
of
CUBA
Palm
barren,
City
of
Santa
Clara
noML/.]...
'
J
New
York
Botanical
Garden
ibsites
N.
L.
Britton
E.
G.
Britton
Peroy
Wilson
COLLEOTOR8
March
29-31,
1910
1659625
Legend -
Level of confidence that token is an accurately-transcribed word
extremely low
very low
low
undetermined
medium
high
very high


| 004:047 Khan | : |
O you who have been given the Scripture (Jews and Christians)!   And the command of Allah is ever executed. |
| 004:047 Pickthal | : |
O ye unto whom the Scripture hath been given! Believe in what We have revealed confirming that which ye possess, before We destroy countenances so as to confound them, or curse them as We cursed the Sabbath-breakers (of old time). The commandment of Allah is always executed. |
| 004:047 Rashad | : |
O you who received the scripture, you shall believe in what we reveal herein, confirming what you have, before we banish certain faces to exile, or condemn them as we condemned those who desecrated the Sabbath. GOD's command is done. |
| 004:047 Sarwar | : |
People of the Book, have faith in the Quran that We have revealed to confirm your Book, before certain faces are changed and turned back. We shall condemn them as We did the people of the Sabbath about whom God's decree had decisively been ordained. |
| 004:047 Shakir | : |
O you who have been given the Book! believe that which We have revealed, verifying what you have, before We alter faces then turn them on their backs, or curse them as We cursed the violaters of the Sabbath, and the command of Allah shall be executed. |
| 004:047 Sherali | : |
O ye people of the Book ! believe in what WE have now sent down, fulfilling that which is with you, before WE destroy some of your leaders and turn them on their backs or curse them as WE cursed the people of the Sabbath. And the decree of ALLAH is bound to be fulfilled. |
| 004:047 Yusufali | : |
O ye People of the Book! believe in what We have (now) revealed, confirming what was (already) with you, before We change the face and fame of some (of you) beyond all recognition, and turn them hindwards, or curse them as We cursed the Sabbath-breakers, for the decision of Allah Must be carried out. |
Concepts/Themes Covered: أركان الإسلام > التوحيد > توحيد الله تعالي > إنذار من لا يعترف بتوحيد الله تعالي بالانتقام Pillars of Islam> Islamic> Oneness of Allah>A Warning to all who do not Acknowledge his Glory Oneness that He'll take Retribution from them القرآن الكريم > وصفه ووجوب الإيمان به The Holy Quran> The Description and the Necessity to Believe it الديانات > بنو إسرائيل > أصحاب السبت Religions>Children of Israel>Al-Sabt(Saturday) People الديانات > بنو إسرائيل > حالاتهم Religions>Children of Israel>Their Status القصص والتاريخ > موسى > قوم موسى The Stories and the History>Moses>People of Moses
This tool uses eight English parallel translations for the Holy Quran imported from Mr. Clay Smith. You can also visit Qurany Concepts for browsing the Quran themes or topics. If you want to search the Holy Quran for keywords, please visit Qurany Keywords.


Career Consult offer a number of services, which you can pick and choose to suit your needs. Please sign up to and recieive a free 15min consultation and let us help you launch your career.
During your appointment you are encouraged to ask anything! No question is too silly.


Which of the following STD's has the patient had?
Which of the following the patient has been diagnosed with earlier?


Overview
Problem
Novice backpackers have a hard time finding multi-day backpacks with the right features, capacity and fit. A single mistake during the purchase might end up affecting the health and even safety of the backpacker during an extended trip in wilderness.
Solution
We redesigned REI's website to provide more detailed guidance and support for novice backpackers to find the backpack of the right size, capacity, and features without having to travel to an REI store.
My Role
UX Researcher, UX Designer
Timeline
Sept. 2017 - Dec. 2017
Team Members
Tony Jin, Xinyi Chen, Lindsay Kelly, Brianna Pritchett, Xue Zhao
Tools
Qualtrics, Sketch, InVision
Our Approach
My Contribution
During the research phase, I contacted local REI stores for interview permissions. After the first store declined our request, my perseverance helped us discover alternative choices and more opportunities for interviews. I visited different REI stores for observations and interviews, and conducted a task analysis based on the data collected. I also took the lead to design and distribute a detailed online survey that yielded hundreds of responses with rich qualitative data. I then analyzed the survey data and helped create affinity diagrams. With the help of my teammate Lindsay, I created a customer journey map based on the data we gathered.
Generated in the ideation phase, my ideas of providing guidance through an interactive survey and community-based expert support were both refined and incorporated into our final design.
In addition, I created two versions of interactive prototypes in InVision for two rounds of user testing. I synthesized users' feedback from both rounds, developed design implications, and created the final User Interface using Sketch. I also moderated several cognitive walkthrough and usability testing sessions.