(Translated by https://www.hiragana.jp/)
About - Apache Mynewt

An OS to build, deploy and securely manage billions of devices

Latest News:

Apache Mynewt 1.12.0, Apache NimBLE 1.7.0 released (April 4, 2024)

Features

  • Real-time operating system kernel (Mynewt OS)
  • Bluetooth Low Energy stack (BLE 5) - choose HOST only or CONTROLLER only or FULL stack.
  • Bluetooth Low Energy Mesh
  • Command line package management and build system (Newt Tool)
  • Hardware Abstraction Layer unifying common MCU features, see discussion thread
  • Board Support Infrastructure
  • System level logs and statistics
  • Secure bootloader, signed images and remote firmware upgrade
  • Flash circular buffers, Newtron Flash File System (nffs), or hook up any other file system
  • Serial upgrade of bootloader, see discussion thread
  • WiFi support via socket interface, join discussion here
  • Sensor API, see discussion thread
  • Support for MIPS architecture (PIC32 boards)
  • Support for RISCV architecture (HiFive1 boards)
  • Basic IP support
  • Full IP support for selected boards (currently STM32F7/F4 and PIC32MZ)
  • Low power support with ability for drivers to switch low power settings automatically (Nordic and Dialog boards)
  • USB support

For features in each release, see Release Notes

Roadmap

Some upcoming features:

  • Extended low power support
  • Extended full IP support
  • Support for additional boards

Feature Request

The issues list on GitHub NimBLE Repo features all the new ideas for Bluetooth Low Energy (BLE) stack awaiting discussion and review. For other requests not related to BLE, please visit GitHub Mynewt Repo. Once the community decides to go ahead with a request, it is scheduled into a release. Generally, effort is made to schedule a requested feature into a particular version no later than 6 weeks prior to the planned release date.

If you have suggestions for a new feature, use case, or implementation improvements, create a new issue in appropriate repository and assign it a label enhancement. Introduce it in the dev@ mailing list with a link to the GitHub Issue.

FAQ

Questions? Click here