Industry-Standard Benchmarks for Embedded Systems
EEMBC, an industry alliance, develops benchmarks to help system designers select the optimal processors and understand the performance and energy characteristics of their systems. EEMBC has benchmark suites targeting cloud and big data, mobile devices (for phones and tablets), networking, ultra-low power microcontrollers, the Internet of Things (IoT), digital media, automotive, and other application areas. EEMBC also has benchmarks for general-purpose performance analysis including CoreMark, MultiBench (multicore), and FPMark (floating-point).

ULPMARK


An EEMBC Benchmark 

Targeting the Ultra-Low Power Domain

Whether the targets are IoT devices or other type of battery-powered application, the implications of ultra-low power (ULP) varies. The lowest active current is required when the power source is severely limited (e.g., energy harvesting). The lowest sleep current is required when the system spends most of its time in standby mode, waking up infrequently (periodically or asynchronously) to process a task. ULP can also imply great energy efficiency, whereby the most work is performed in a limited time period. Overall, the application requires tradeoffs on all of the above. To ensure ULP operation over periods of months, years, and decades, developers face numerous optimization challenges. An increasing number of microcontrollers ‘claim’ ULP capabilities, but developers cannot rely on datasheet parameters alone. The EEMBC® ULPMark™ standardizes datasheet parameters and provides a methodology to reliably and equitably measure MCU energy efficiency.


Two Versions of ULPMark™
  • ULPMark-Core Profile (version 1.0) focuses on the MCU’s core. This benchmark utilizes a common set of workloads that are portable across 8-, 16-, and 32-bit microcontrollers. The Core Profile runs on a one-second duty cycle combining these workloads with an extended period of inactivity to enable the use of microcontroller low-power modes.

    Click on image to zoom
  • ULPMark-Peripheral Profile (version 2.0) (UNDER DEVELOPMENT) focuses on the MCU’s commonly used peripherals, including pulse-width modulation (PWM), analog-to-digital conversion (ADC), serial peripheral interface (SPI), and real-time clock (RTC). ULPMark 2.0 defines ten 1-second activity slots each with variable usage of ADC, SPI, PWM, RTC, allowing the MCU and peripherals to sleep after their activities have completed.

    Click on image to zoom

 

ULPMark Measurement Methodology

Both versions of ULPMark utilize the EEMBC IoTConnect™ Framework, portable to any vendor’s microcontroller
Provides external stimuli for the MCU’s peripherals and coordinates the timing of the energy measurements
Compatible with EEMBC IoTMark™-BLE and EEMBC SecureMark™ benchmarks


Click on image to zoom

 
Working Group Status
  • MCU vendors and others are submitting results for ULPMark-Core Profile
  • ULPMark-Peripheral Profile development is nearing completion. Finalizing result calculation, fine-tuning peripheral behavior, and release-candidate testing.
  • Join the EEMBC ULPMark working group to help ensure a meaningful and fair representation for your company’s products. Email EEMBC for more information.

Chairperson

  • Monica Redon, Analog Devices

Members

  • Ambiq Micro, Analog Devices, Andes Technology, ARM, Cypress, Dialog Semiconductor, Flex, Intel, Microchip, NXP, Nordic Semiconductor, ON Semiconductor, Renesas, Silicon Labs, STMicro, Texas Instruments.

IoTConnect Framework Interface


Click to Zoom

What Does it Mean to be ULPMark Ready?

  • It’s an MCU board that allows easy connection of the EEMBC EnergyMonitor to the microcontroller.
  • The MCU vendor has provided a detailed description of how to setup a board to run ULPMark.
  • The MCU board can only be modified simply (e.g. jumper settings) with no hardware modifications
  • Vendor has provided documentation of tools needed, platform and project files, etc.

ULPMark Ready

Beyond the Data Sheets of Ultra-Low-Power MCUs: What Does Energy Efficiency Really Mean? (Elektroniknet.de)

ULPMark Goes Peripheral

ULPBench Debunked

Representing ULPMark Results in Device Datasheets