mu | libnklabs | |
---|---|---|
5 | 4 | |
539 | 20 | |
1.3% | - | |
7.1 | 5.3 | |
6 days ago | 4 months ago | |
Python | C | |
GNU General Public License v3.0 or later | GNU General Public License v3.0 or later |
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.
mu
- Welcome to Project Mu
-
Purpose: Project Mu Payload
yes kkkkkk, the project mu have a strange way to build, and project mu have a not usable documentation, i think is because microsoft is microsoft, the project mu is a OEM Firmware as Service, the reason for not have a easy documentation can be for seal a service. in the past i have make a question about coreboot support https://github.com/microsoft/mu/issues/121
-
Framework: Open Sourcing Our Firmware
The stock edk2 menu has, like, two items.
System76 have built a more serious setup UI: https://github.com/system76/firmware-setup
Microsoft’s https://github.com/microsoft/mu also probably contains UI from the Surface line or something??
- Surfac-ify
libnklabs
-
Keyboard Shortcuts every Command Line Hacker should know about GNU Readline
Two issues with readline: it's GPL and it's big. For embedded systems intended to become products you really need something else. My tiny variant is this, but for sure there are many others:
https://github.com/nklabs/libnklabs
("nkreadline" has editing, tab-completion (for embedded "nkcli" commands) and history)
-
Rtems Real Time Operating System
I used RTEMS on Movius Myriad vision CPU (running on LEON- a SPARC clone).
I remember the RTEMS event concept was not very good- the events are globally shared. You are better off using semaphores.
>I have realized that for a majority of the embedded software using an RTOS is an overkill
I agree with this. Instead of an OS, we like to use a small framework that provides a CLI, database and UART communications (YMODEM protocol). It's a single stack system that provides a simple work-queue for scheduling future tasks / callbacks, and for interrupt code to schedule non-interrupt code. It works for almost everything as long as you are comfortable programming in an event-driven style.
https://github.com/nklabs/libnklabs
(recently added support for AVR 8-bit processors).
-
Framework: Open Sourcing Our Firmware
I've extracted the Chromium-EC encryption functions, they are convenient for signing / verifying firmware on other platforms. Chromium-ec is nice for example code like this:
https://github.com/jhallen/rsa-verify
On the other hand, if you are looking for some generic embedded system code all in C, here is our library:
https://github.com/nklabs/libnklabs
I think it's most unique feature is the embedded schema-based database- so you can save things like calibration and configuration information in local flash memory. Recently I've been adding device drivers for all common devices I can find on break-out boards for the Arduino and Raspberry-PI communities.
- Show HN: Library to quickly make MCU-based products
What are some alternatives?
fwhunt-scan - Tools for analyzing UEFI firmware and checking UEFI modules with FwHunt rules
carl9170fw - CARL9170 Firmware Source Repository
InitWare - The InitWare Suite of Middleware allows you to manage services and system resources as logical entities called units. Its main component is a service management ("init") system.
firmware-setup - Firmware Setup
qiling - A True Instrumentable Binary Emulation Framework
linenoise - A small self-contained alternative to readline and libedit
esp32-elfloader - esp32 component to load in ram and relocate elf file
Ventoy - A new bootable USB solution.
input-polling-test - Tests the scan behavior of your keyboard/mouse
open-ath9k-htc-firmware - The firmware for QCA AR7010/AR9271 802.11n USB NICs
rsa-verify