Movatterモバイル変換


[0]ホーム

URL:


Skip to content

Navigation Menu

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up

modm: a C++23 library generator for AVR and ARM Cortex-M devices

License

NotificationsYou must be signed in to change notification settings

modm-io/modm

Repository files navigation

modm (pronounced like dial-up "modem") is a toolbox forbuilding custom C++23 libraries tailored to your embedded device.modm generates startup code, HALs and their implementations, communicationprotocols, drivers for external devices, and BSPs in a modular, customizableprocess that you can fine-tune to your needs.

This project also has aforum for discussions and atechnical blog to document larger design concepts.

modm is optimized for the harsh requirements of theEurobot competition,where our robots need to run reliably and completely autonomously for the game's100 second duration. Our robots contain a lot of different microcontrollers, somewithout a lot of resources, so modm needs to fulfill a diverse set of objectives,like small code size with small memory consumption, predictable program flow,extreme portability.

The library source code is licensed as MPLv2 with any external source code undercompatible licenses (BSD, Apache2, MIT). So feel free to fork this project andadapt it to your needs. The only thing we ask of you is to contribute your changesback so everyone can benefit.

Please clone modm recursively, you need all the submodules:

git clone --recurse-submodules --jobs 8 https://github.com/modm-io/modm.git

Features

  • Efficient and fast object-oriented C++23 API.
  • Support for thousands of AVR and ARM Cortex-M microcontrollers from Microchip, STMicroelectronics and Raspberry Pi.
  • Build system agnostic: Choose SCons, CMake, Makefile or use your own.
  • Modular, data-driven, target-specific HAL generation using the lbuild code generator.
  • No memory allocations in HAL with very low overall RAM consumption.
  • Highly configurable modules with sensible defaults and lots of documentation.
  • Cross-platform peripheral interfaces incl. bit banging:
    • GPIO, External Interrupt and IO expanders.
    • ADC, DAC and Comparators.
    • UART, I2C, SPI, CAN and Ethernet.
  • Interfaces and drivers for many external I2C and SPI sensors and devices.
  • Debug/logging system with IOStream and printf interface.
  • Cooperative, stackful fibers and scheduler.
  • Functional (partial) libstdc++ implementation for AVRs.
  • Useful filter, interpolation and geometric algorithms.
  • Lightweight unit testing system (suitable for AVRs).
  • Hundreds of tests to ensure correct functionality.
  • Integration of useful third-party software:

Microcontrollers

modm can create a HAL for 3839 devices of these vendors:

  • STMicroelectronics STM32: 3034 devices.
  • Microchip SAM: 416 devices.
  • Microchip AVR: 388 devices.
  • Raspberry Pi: 1 device.

Here is a table with all device families and the peripheral drivers they support:

  • ✅ Implemented as a software driver in modm.
  • ○ Available in hardware but missing a software driver in modm.
  • ✕ Unavailable in hardware or device with that peripheral not supported by modm.

Note that this is a summary overview and your specific device may not have allthe peripherals in this table.Pleasediscover modm's peripheral drivers for your specific device.

STM32SAMRPAT
PeripheralC0F0F1F2F3F4F7G0G4H7L0L1L4L5U5D1x
D2x
DAx
D5x
E5x
E7x
S7x
V7x
G5x2090MegaTiny
ADC
CAN
Comparator
DAC
DMA
Ethernet
External Interrupt
External Memory
GPIO
I2C
Internal Flash
IWDG
Random Generator
RTC
SPI
System Clock
Timer
UART
Unique ID
USB

We are only a small team of developers and are limited in the amount of deviceswe can support and test in hardware.Open a discussion to ask ifyour specific device is supported out-of-the-box and how you can add it otherwise.

Boards

We have out-of-box support for many development boards including documentation.

AL-AVREB-CANArduino NANOArduino UNOBlack Pill F103
Black Pill F401Black Pill F411Blue Pill F103DEVEBOX-STM32F4XX
DEVEBOX-STM32H750VBDISCO-F051R8DISCO-F072RBDISCO-F100RB
DISCO-F303VCDISCO-F401VCDISCO-F407VGDISCO-F411VE
DISCO-F429ZIDISCO-F469NIDISCO-F746NGDISCO-F769NI
DISCO-L152RCDISCO-L476VGFEATHER-M0FEATHER-M4
FEATHER-RP2040MEGA-2560-PRONUCLEO-C031C6NUCLEO-F031K6
NUCLEO-F042K6NUCLEO-F072RBNUCLEO-F091RCNUCLEO-F103RB
NUCLEO-F303K8NUCLEO-F303RENUCLEO-F334R8NUCLEO-F401RE
NUCLEO-F411RENUCLEO-F429ZINUCLEO-F439ZINUCLEO-F446RE
NUCLEO-F446ZENUCLEO-F746ZGNUCLEO-F767ZINUCLEO-G070RB
NUCLEO-G071RBNUCLEO-G431KBNUCLEO-G431RBNUCLEO-G474RE
NUCLEO-H723ZGNUCLEO-H743ZINUCLEO-L031K6NUCLEO-L053R8
NUCLEO-L152RENUCLEO-L432KCNUCLEO-L452RENUCLEO-L476RG
NUCLEO-L496ZG-PNUCLEO-L552ZE-QNUCLEO-U575ZI-QOLIMEXINO-STM32
Raspberry Pi PicoSAMD21-MINISAMD21-XPLAINED-PROSAME54-XPLAINED-PRO
SAME70-XPLAINEDSAMG55-XPLAINED-PROSAMV71-XPLAINED-ULTRASmart Response XE
STM32-F4VESTM32F030-DEMOTHINGPLUS-RP2040WEACT-C011F6

Drivers

We also have a number of completely target-independent drivers for externaldevices connected via I2C, SPI, UART, BitBang, etc. Most of thesealso give you access to the entire device so you can easily configure them foryour specific needs.

AD7280AAD7928ADIS16470ADNS9800ADS101XADS7828
ADS7843ADS816xAMS5915APA102AS5047AS5600
AT24MAC402SPI FlashBME280BMI088BMP085BNO055
CAT24AACYCLE-COUNTERDRV832XDS1302DS1631DS18B20
DW3110EA-DOGEncoder InputEncoder Input BitBangEncoder Output BitBangFT245
FT6x06Gpio SamplerHCLAxHD44780HMC58xHMC6343
HX711I2C-EEPROMILI9341IS31FL3733ITG3200IXM42XXX
L3GD20LAN8720ALAWICELLIS302DLLIS3DSHLIS3MDL
LM75LP503xLSM303ALSM6DS33LSM6DSOLTC2984
MAX31855MAX31865MAX6966MAX7219MCP23x17MCP2515
MCP3008MCP7941xMCP990XMMC5603MS5611MS5837
NOKIA5110NRF24TFT-DISPLAYPAT9125ELPCA8574PCA9535
PCA9548APCA9685QMC5883LSH1106SIEMENS-S65SIEMENS-S75
SK6812SK9822SSD1306ST7586SST7789STTS22H
STUSB4500SX1276SX128XTCS3414TCS3472TLC594x
TMP102TMP12xTMP175TOUCH2046VL53L0VL6180
WS2812

Please seeour examples for a complete list of tested targets and drivers.

How can I contribute?

The easiest way for you and the best way for us to see if something is unclearor missing, is if you use the library and give us some feedback byfiling a bugreport or if you have a fix alreadyopening a pull request.

SeeCONTRIBUTING.md for our contribution guidelines.

The modm project is maintained byNiklas Hauser (@salkinium),Raphael Lehmann (@rleh), andChristopher Durand (@chris-durand) with significant contributions fromSascha Schade (@strongly-typed),Fabian Greif (@dergraaf),Kevin Läufer (@ekiwi),Martin Rosekeit (@thundernail),Daniel Krebs (@daniel-k),Georgi Grinshpun (@georgi-g),David Hebbeker (@dhebbeker),Thorsten Lajewski (@TheTh0r),Mike Wolfram (@mikewolfram),andmany more contributors.

Folder structure

examples
Example projects that show the usage of parts of the modm library. These projects are always up to date and are tested to compile by our CI.
src
This folder contains the actual source code of modm grouped into several modules.
test
Contains hundreds of tests for making sure modm works the way we expect it to.
docs
General documentation about this library and how to use it.
ext
Third-party code used in this library.
tools
Support tools, scripts and files.

[8]ページ先頭

©2009-2025 Movatter.jp