bm8563
STMems_Standard_C_drivers
| bm8563 | STMems_Standard_C_drivers | |
|---|---|---|
| 1 | 9 | |
| 8 | 664 | |
| - | 1.4% | |
| 0.0 | 7.2 | |
| over 2 years ago | 13 days ago | |
| C | C | |
| MIT License | BSD 3-clause "New" or "Revised" License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
bm8563
-
Best practices for embedded libraries / architecture overall
I am not sure if the above can be considered best practices but they were where I took the inspiration. I also tend to keep the driver API simple, usually consisting only of init, read, write, ioctl and close methods.
STMems_Standard_C_drivers
-
Best Practices for Standard C Drivers Embedded in the Git Repository
I did a quick search and found that STM only creates one repo for all their MEMS Sensors. On the other hand, Bosch creates an account and then an independent repository for each MEMS Sensor.
-
Sensor Drivers in embedded C: Best Practices
I have been using several STM and Bosch embedded C Drivers in my work. As a hobby I sometimes play with Arduino and use drivers from Adafruit that are implemented in C++.
-
How can I effectively write, document and publish libraries for STM32 on Github?
See how STM32 writes in its own C libraries and replicate it: https://github.com/STMicroelectronics/STMems_Standard_C_drivers
- Library design that is not fixed to a specific mcu
- IMU recomendations
- New to IOT resources
-
What shuld be the reason for not getting output from the MOTION GC library?
I'm working on the "STEVAL-MKI182V2" mounted on the STEVAL-MKI109V3 development board. Initially, I downloaded the Standard c Drivers from the following link https://github.com/STMicroelectronics/STMems_Standard_C_drivers where I found the .ioc file called _prj_MKI109V3 which is specifically developed for the MKI109V3 board.
- Interfacing with HTS221 using STM32's HAL
-
Best practices for embedded libraries / architecture overall
There are some exceptions too such as STMems Standard C Drivers and Bosch Sensortec Drivers.
What are some alternatives?
rpi - Microcontroller projects (RPi, Arduino, ATTiny85, ESP, Pico, STM8/32)
BlueNRG-1-VSCode - This repo is a template for setting up VSCode to compile and debug code for the BlueNRG-1 chip
buck50 - STM32F103 logic analyzer and more
stm32f429 - Keil projects and libraries for STM32F4xx devices
M5-ESP32-keyer - ESP32 based remote CW keyer
lis2de12-pid - lis2de12 platform independent driver based on Standard C language and compliant with MISRA standard
ssd1306 - Driver for SSD1306, SSD1331, SSD1351, IL9163, ILI9341, ST7735, PCD8544, Nokia 5110 displays running on Arduino/ESP32/Linux (Rasperry) platforms
axp192 - Platform agnostic I2C driver for AXP192 power system management IC
furble - A wireless remote shutter release/button for Fujifilm (eg. GFX100II, GFX100S, X-H2S, X-S10, X-T3, X-T30, X-T4, X-T5, X100V) and Canon EOS (eg. M6, RP) cameras.
u8g2 - U8glib library for monochrome displays, version 2
STM32-HAL-HD44780-16x2LCD - A simple library for STM32 microcontrollers to drive 16x2 LCD displays based on the HD44780 controller