Skip to main content

Arm Mbed Enabled Categories and Technical Requirements

For a product to be validated as an official Arm® Mbed Enabled™ product, it must fall under one of the following categories, and must meet the compliance criteria and technical requirements defined for that category.

Product Categories

Mbed Enabled for Mbed OS 2 ("Classic")

  • Board:  A development platform including a suitable microcontroller target, programming and debugging interfaces, and optional peripherals containing a MCU
  • Component: Sensors, radios, modules and other components external to the target MCU that have a library targeting the Mbed SDK
  • End Product: Final products and devices that utilize Mbed Classic SDK

Mbed Enabled for Mbed OS 5

  • Interface: hardware circuit and accompanying firmware that is used for development, debug and testing software that runs on Arm based microcontrollers. It provides access to the Arm CPU debug access port.
  • Board: development or evaluation boards that include a target and an Interface.
  • End Product: a product that utilizes Arm Mbed technology in its creation (i.e. not a developer product).

Technical Requirements

To apply for a product to be accredited as an official Arm Mbed Enabled product, a product must fall under one of the following categories, and must meet the criteria defined for that category.

  • Mbed Enabled for Mbed OS 2

    Mbed Enabled for Mbed OS 2

    The technical requirements below align with Mbed OS 2 ("Classic").

    Board Requirements

    A hardware platform contains an on-board interface circuit used for programming and debugging the target MCU.

    1. The target MCU is supported in the Mbed SDK (http://github.com/mbedmicro/mbed)
    2. On-board interface circuit for programming and debugging
      • MUST Implement the following firmware behaviors as a USB Composite Device and be compatible with all actively supported versions of Windows, Mac and Linux operating systems.
        • USB MSC - Mass Storage Device Class
          • Program binary or hex record file formats
          • Contain a read-only file named mbed.htm that directs a browser to the appropriate platform page on http://developer.mbed.org/platforms
        • USB CDC - Communication Device Class
          • Operate at all standard baudrate(s) 2400 thru 115200
          • Support ‘SendBreak’ resulting in target MCU reset on all OSs
        • USB HID - Human Interface Device
          • Channel used for CMSIS-DAP or similar debug protocol
    3. Hardware platform testing
    4. Developer Documentation
      • Has an official platform page that contains pinout, schematics and platform information Platform example(s) to help get started with the product
      • Designated F/AE on http://developer.mbed.org to monitor community questions/feedback regarding the product and supporting software
    5. Available for purchase
      • The platform must be in production and available for purchase or sample

    Component Requirements

    Components are sensors, radios, modules or software that connects to and runs on a Mbed Enabled MCU or platform and library uses the Mbed SDK peripheral and timing APIs.

    1. Hardware component delivered with the component library providing a fully functional library and example(s)
      • Component library should work on a minimum of 10 Hardware Platforms
    2. Developer Documentation
      • Has an official component page that contains pinout, schematics and component information
      • Has an official component library support written against the Mbed SDK
      • Component library implements established C++ technology APIs and/or Mbed common coding practices
      • Component example(s) to help get started with the product.
      • Component unit and functional tests
    3. Designated F/AE on http://developer.mbed.org to monitor community questions/feedback regarding the product and support software

    End product requirements

    Final products and devices that utilize Mbed technology.

    1. Includes Hardware Platform, target MCU and/or Component
  • Mbed Enabled for mbed OS 5

    Mbed Enabled for Mbed OS 5

    The compliance criteria and technical requirements below aligns with Mbed OS 5.1 (16.07) release.

    Compliance Criteria

    All Mbed Enabled products must meet all MUST compliance criteria and are encouraged to meet all SHOULD compliance criteria.

    Interface

    A hardware circuit and accompanying firmware that is used for development, debug and testing software that runs on Arm based microcontrollers. It provides access to the Arm CPU debug access port.

    • MUST support a Mbed htrun plug-in. For compatibility requirements see htrun porting guide
    • MUST be identifiable by Mbed-ls. For compatibility requirements see Mbed-ls porting guide
    • MUST implement the following firmware behaviors as a USB Composite Device
      • USB MSC -- Mass Storage Device Class
        • MUST support programming hex files
        • MUST contain a read-only HTML-5 compliant htm file
        • SHOULD be named mbed.htm
        • MUST have a method for reading the contents of target flash
        • MUST have a details file containing board ID and circuit ID
        • MUST indicate failure status of programming operation
        • SHOULD support programming binary files
        • SHOULD redirect to the mbed.com product specific page
      • USB CDC -- Communication Device Class
        • MUST support at all standard baudrates 9600 thru 115200
        • MUST Support ACM ‘SendBreak’ resulting in target reset sequence
        • SHOULD support all standard baudrates 2400 thru 921600
      • USB HID -- Human Interface Device or similar
        • MUST support a channel used for debugging
        • SHOULD be CMSIS-DAP
    • MUST have technical support documents available for download from Mbed.com
    • MUST have EDA consumable files available for download from Mbed.com
    • MUST have a public issue tracker and feedback mechanism
    • MUST have an Mbed Partner Agreement

    Board

    Development or evaluation boards that include a Target and an Interface.

    • MUST implement CMSIS-CORE, Mbed HAL and Mbed drivers in the current Mbed OS major release

    • MUST implement Mbed RTOS APIs (based on CMSIS-RTOS standard)
    • MUST support all major compilers for Arm architecture – GCC Arm, Arm Compiler 5 and IAR
    • SHOULD implement entropy source support, if provided by the SoC, module or board
    • MUST pass all Mbed OS validation tests for the current major release
    • MUST have an Mbed Enabled Interface circuit and firmware available (see compliance criteria for Interface)
    • MUST have a pinout diagram based on the Mbed pinout template
    • MUST provide product photo, description, features and other marketing collateral
    • MUST have technical documents available for download from the Mbed Developer website
    • MUST have EDA consumable files available for download from the Mbed Developer website
    • MUST provide a comprehensive example using all onboard Components in a meaningful way
    • SHOULD use supported Components
    • MUST have a public issue tracker and feedback mechanism
    • MUST have a support engineer on the Mbed Developer website to monitor community questions/feedback regarding the product and supporting software
    • MUST provide 10x units mounted on a PCB with for validation and regression testing
    • MUST have a license identifiable using SPDX
    • MUST have an Mbed Partner Agreement

    End Product

    A product that utilize Arm mbed technology in its creation (i.e. not a developer product).

    • MUST be based on Arm Mbed technology
    • MUST complete a questionnaire about the end product to be reviewed by the Mbed Enabled review committee
    • SHOULD complete a technical review of end products implementation (NDA available if required)

    Technical Requirements

    All Mbed Enabled products must pass the test defined by these technical requirements.

    Interface 

    Hardware circuit and accompanying firmware that is used for development, debug and testing software that runs on Arm based microcontrollers. It provides access to the Arm CPU debug access port.

    • Compatible with and supported by Mbed host test (https://github.com/armmbed/htrun)
    • Compatible with and supported by Mbed-ls (https://github.com/armmbed/mbed-ls)
    • Have product specification document publicly available (i.e. Have product specification document publicly available (i.e. http://mbed.com/daplink)
    • Have a schematic publicly available (i.e. https://developer.mbed.org/teams/mbed/code/mbed-HDK)
    • Have a public issue tracker and feedback mechanism (i.e. https://github.com/armmbed/DAPLink/issues)
    • Implement the following firmware behaviors as a USB Composite Device and be compatible with all actively supported versions of Windows, Mac and Linux operating systems.
      • USB Filesystem -- A disk drive with product information. Drag-and-drop action programs the target MCU memory.
      • USB Serial Port -- A virtual comport that has exposes connections for UART transmit and receive pin. The 'Send Break' command results in a reset sequence.
      • USB Debug -- A connection that allows programming and debugging from the host PC.

    Board 

    Development or evaluation boards that include both a Target and an Interface.

    • Target port merged mainline in https://github.com/mbedmicro/mbed according to Mbed OS 5.0 porting and contributor guidelines (https://github.com/mbedmicro/mbed/blob/master/docs/COMMITTERS.md)
    • Passing tests suite and all test plans for (> Mbed test -t <arm, iar, gcc_arm> -m <target name>)
      • u-test framework
      • CMSIS-CORE
      • Mbed HAL
      • Mbed RTOS
    • Mbed HAL requirements:
      • Timing resource capable of 1us interval
      • Low power timing resource capable of 1ms interval
      • Dynamic GPIO configuration
      • Sleep able to enter WFI
    • Mbed RTOS requirements:
      • RTOS must be enabled and capable of 1 thread minimum (i.e. main thread)

    End Product

    A product that utilize Arm Mbed technology in its creation (i.e. not a developer product).

    • Completed questionnaire and technical review with end product review team

Apply

Ready to apply? Before applying review the technical requirements and ensure your product meets all requirements before submitting your application. 

Trademark Guidelines

Arm Mbed Trademark Guidelines (220.5 KB)

Important information

This site uses cookies to store information on your computer. By continuing to use our site, you consent to our cookies.

Arm websites use two types of cookie: (1) those that enable the site to function and perform as required; and (2) analytical cookies which anonymously track visitors only while using the site. If you are not happy with this use of these cookies please review our Privacy Policy to learn how they can be disabled. By disabling cookies some features of the site will not work.