|Project Name||Stars||Downloads||Repos Using This||Packages Using This||Most Recent Commit||Total Releases||Latest Release||Open Issues||License||Language|
|Tasmota||19,754||a day ago||11||gpl-3.0||C|
|Alternative firmware for ESP8266 and ESP32 based devices with easy configuration using webUI, OTA updates, automation using timers or rules, expandability and entirely local control over MQTT, HTTP, Serial or KNX. Full documentation at|
|Esp32marauder||2,429||a day ago||44||mit||C++|
|A suite of WiFi/Bluetooth offensive and defensive tools for the ESP32|
|Mongoose Os||2,383||3 months ago||89||other||C|
|Iotsecurity101||2,068||20 days ago||1||gpl-3.0|
|A Curated list of IoT Security Resources|
|Emba||1,870||2 days ago||19||gpl-3.0||Shell|
|EMBA - The firmware security analyzer|
|🌧 An easy-to-use API for devices that use Tuya's cloud services. Documentation: https://codetheweb.github.io/tuyapi.|
|Awesome Embedded And Iot Security||1,183||a month ago||1||cc0-1.0|
|A curated list of awesome embedded and IoT security resources.|
|Lua Rtos Esp32||1,016||6 months ago||36||other||C|
|Lua RTOS for ESP32|
|Unofficial iRobot Roomba and Braava (i7/i7+, 980, 960, 900, e5, 690, 675, m6, etc) node.js library (SDK) to control your robot|
|Home||743||15 days ago||81|
|:house: The landing page for .NET nanoFramework repositories.|
Document Language: English | 简体中文
This Home repository is the starting point for developers that want to learn about .NET nanoFramework, contribute to it or opening issues. It contains links to the various GitHub repositories used by .NET nanoFramework.
.NET nanoFramework goal is to be a platform that enables the writing of managed code applications for constrained embedded devices. Developers can harness the familiar IDE Visual Studio and their .NET (C#) knowledge to quickly write applications without having to worry about the low level hardware intricacies of a micro-controller.
It is part of the .NET Foundation.
Being a developer you'll probably will fit in one (or maybe both 😉) of the following profiles:
Most of the core team members and contributors are embedded systems enthusiasts, passionate about coding and people that like challenges. The work on .NET nanoFramework is done mostly on their free time. Some of the core members happen to work on companies that sponsor heavily nanoFramework and offer their work hours to the project. If you use .NET nanoFramework for serious work or want to support it, please donate. This allow for paying the infrastructure cost and more time to be invested on the project. Besides monetary contributions, there are several other ways to contribute. Please read the documentation about this here.
This is how we use the donations:
Sponsors will get their logo and link to a website on our GitHub readme and also on our home page.
Backers are individuals who contribute with money to help support nanoFramework. Every little bit helps and we appreciate all contributions, even the smallest ones.
There are other people and organizations that have contributed to .NET nanoFramework along the time in several ways: sponsoring the coding of a feature that was missing or needed improvement, paying for an expense, coding a feature or... We would like to acknowledge these sponsors.
Each of the following ZIP files contains the image files for nanoBooter and nanoCLR in various formats (HEX, BIN and DFU). They should be flashed in the target boards using an appropriate software utility.
The stable versions are RTM builds with the smallest possible size. They include the latest stable version. The debugging feature is disabled and only minimal (or none) error messages.
The preview versions are continuous builds of the reference targets. They include the latest version of all features and bug corrections. They also have the debugging feature enabled along with detailed error messages.
The above firmware builds include support for the class libraries and features marked bellow.
Besides the above firmware images, you can find several others for community provided target boards. Check the available ones and download links on the Community Targets repo.
Our GitHub organization holds the various repositories for firmware, class libraries, documentation and tools. You can find here a list and a description of each of them.
Some of the best ways to contribute are to try things out, file bugs, and join in design conversations.
If you have a question, need clarification on something, need help on a particular situation or want to start a discussion, do not open an issue here. It is best to ask the question on Stack Overflow using the
nanoframework tag or to start a conversation on one of our Discord channels. Make sure to select the channel that's most appropriate to the context so subject matter experts are most likely to answer promptly.
If you've find a bug or can't use Discord, please open an issue at Issues. We ask you to open an issue only when you have a real and confirmed one. Don't open an issue for support requests or to start a discussion. For that you'll get a better (and quicker!) support/feedback in one of the Discord channels.
You can also ask questions on Stack Overflow and tag them with #nanoframework.
Looking for something to work on? Check the list of up-for-grabs issues on the Home repo, that's a great place to start.
See some of our guides for more details:
.NET nanoFramework libraries, firmware images, tools and samples are licensed under the MIT license.
The project documentation is a great place to find information about .NET nanoFramework, no matter if you are newcomer or a veteran. It's organized in the following categories:
There is a blog where we try to post detailed updates about the development status, technical posts about a particular feature ou a design option.
We also have a YouTube channel where with video tutorials along with feature demos and teasers about new ideas that we are experimenting with.
This project has adopted the code of conduct defined by the Contributor Covenant to clarify expected behavior in our community. For more information see the .NET Foundation Code of Conduct.