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

🏠 The landing page for .NET nanoFramework repositories.

License

NotificationsYou must be signed in to change notification settings

nanoframework/Home

Repository files navigation

#yourfirstprAverage time to resolve an issuePercentage of issues still openDiscord

nanoFramework logo


Document Language:English |简体中文

.NETnanoFramework Home

ThisHome repository is the starting point for developers that want to learn about .NETnanoFramework, contribute to it or opening issues.It contains links to the various GitHub repositories used by .NETnanoFramework.

.NETnanoFramework 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 adeveloper you'll probably will fit in one (or more than one😉) of the followingprofiles:

  • You can enjoy to develop C# applications for micro-controllers.
  • You can become a contributor as there are lots of areas to express yourself:
    • C/C++ native drivers working low level directly on the MCU with our Platform Abstraction Layer and Hardware Abstraction Layer, RTOS, developing .NET CLR for nanoFramework.
    • Managed C# to write new classes and drivers to add more bindings, libraries to .NET nanoFramework.
    • Managed C# to write tools like the Visual Studio Extensibility, debugger and others mostly .NET Core/.NET 5 CLI applications.
    • Help in setting up Azure DevOps pipelines to automate as much as possible.
    • Writing and improving our Unit Tests.
    • Helping others by answering their questions.
    • Writing and improving documentation, doing PR reviews or participating in the overall project organization.

.NET nanoFramework is a fun and interesting way to learn. It’s a complete project with a lot of deep engineering. You’ll find a vibrantcommunity to help you and you’ll be able to help as well. We do welcome all kind of contributions and we aim to give visibility to our contributors.

Sponsoring .NETnanoFramework

Most of the core team members and contributors are embedded systems enthusiasts, passionate about coding and people that like challenges. The work on .NETnanoFramework is done mostly on their free time. Some of the core members happen to work on companies that sponsor heavilynanoFramework and offer their work hours to the project. If you use .NETnanoFramework 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 thishere.

This is how we use the donations:

  • Pay for infrastructure costs.
  • Develop public relation actions to get the project known.
  • Support maintainers and contributors that invest a large amount of time in the project.
  • Support projects that .NETnanoFramework depends on.
  • Produce documentation, tutorials and other content to support developers using .NETnanoFramework.
  • Organize events to demo .NETnanoFramework.

Sponsors

Sponsors will get their logo and link to a website on our GitHub readme and also on our home page.

Bronze Sponsors





Backers

Backers are individuals who contribute with money to help support nanoFramework. Every little bit helps and we appreciate all contributions, even the smallest ones.

Other backers and sponsors

There are other people and organizations that have contributed to .NETnanoFramework 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.

ChibiOS RTOS

Firmware for reference boards

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.

Thestable versions are continuous builds of the reference targets. They include the latest version of all features and bug corrections. They also havemanaged debugging features enabled along with detailed error messages, but excludenative debugging features and only minimal (or no) error messages.

For native debugging, please download thenf-interpreter repository and build locally.

Besides the firmware images below, you can find several others for community provided target boards. Check the available ones and download links on theCommunity Targets repo.

ESP32 modules and boards

TargetStable
ESP32_PSRAM_REV0Latest Version @ Cloudsmith
ESP32_REV0Latest Version @ Cloudsmith
ESP32_PSRAM_XTAL26_REV0Latest Version @ Cloudsmith
ESP32_PSRAM_REV3Latest Version @ Cloudsmith
ESP32_REV3Latest Version @ Cloudsmith
ESP32_BLE_REV0Latest Version @ Cloudsmith
ESP32_BLE_REV3Latest Version @ Cloudsmith
ESP_WROVER_KITLatest Version @ Cloudsmith
ESP32_PICOLatest Version @ Cloudsmith
ESP32_LILYGOLatest Version @ Cloudsmith
FEATHER_S2Latest Version @ Cloudsmith
KALUGA_1Latest Version @ Cloudsmith
ESP32_C3Latest Version @ Cloudsmith
ESP32_C3_REV3Latest Version @ Cloudsmith
ESP32_OLIMEXLatest Version @ Cloudsmith
XIAO_ESP32C3Latest Version @ Cloudsmith
ESP32_S3Latest Version @ Cloudsmith
ESP32_S3_BLELatest Version @ Cloudsmith

M5Stack

TargetStable
M5CoreLatest Version @ Cloudsmith
M5StickCLatest Version @ Cloudsmith
M5StickCPlusLatest Version @ Cloudsmith
M5Core2Latest Version @ Cloudsmith
AtomS3Latest Version @ Cloudsmith

STM32 boards and chip based

TargetStable
ST_STM32F429I_DISCOVERY (B01)Latest Version @ Cloudsmith
ST_NUCLEO64_F091RCLatest Version @ Cloudsmith
ST_STM32F769I_DISCOVERYLatest Version @ Cloudsmith
ORGPAL_PALTHREELatest Version @ Cloudsmith

Silicon Labs Giant Gecko boards

TargetVersion
SL_STK3701ALatest Version @ Cloudsmith
SL_STK3701A_REVBLatest Version @ Cloudsmith

NXP boards

TargetStable
NXP_MIMXRT1060_EVKLatest Version @ Cloudsmith

TI boards

TargetStable
TI_CC1352R1_LAUNCHXL_868Latest Version @ Cloudsmith
TI_CC1352R1_LAUNCHXL_915Latest Version @ Cloudsmith
TI_CC3220SF_LAUNCHXLLatest Version @ Cloudsmith

The above firmware builds include support for the class libraries and features marked below.

Click to expand!
TargetGpioSpiI2cPwmAdcDacSerialOneWireEventsSWONetworkingBluetooth BLELarge HeapUI
ESP32_PSRAM_REV0✔️✔️✔️✔️✔️✔️✔️✔️✔️✔️✔️
ESP32_REV0✔️✔️✔️✔️✔️✔️✔️✔️✔️✔️✔️
ESP32_PSRAM_XTAL26_REV0✔️✔️✔️✔️✔️✔️✔️✔️✔️✔️✔️
ESP32_PSRAM_REV3✔️✔️✔️✔️✔️✔️✔️✔️✔️✔️✔️
ESP32_REV3✔️✔️✔️✔️✔️✔️✔️✔️✔️✔️✔️
ESP32_BLE_REV0✔️✔️✔️✔️✔️✔️✔️✔️✔️✔️✔️
ESP32_BLE_REV3✔️✔️✔️✔️✔️✔️✔️✔️✔️✔️✔️
ESP_WROVER_KIT✔️✔️✔️✔️✔️✔️✔️✔️✔️✔️✔️✔️
ESP32_PICO✔️✔️✔️✔️✔️✔️✔️✔️✔️✔️
ESP32_LILYGO✔️✔️✔️✔️✔️✔️✔️✔️✔️✔️ Wi-Fi + Ethernet
FEATHER_S2✔️✔️✔️✔️✔️✔️✔️✔️✔️✔️
KALUGA_1✔️✔️✔️✔️✔️✔️✔️✔️✔️✔️✔️
ESP32_C3✔️✔️✔️✔️✔️✔️✔️✔️✔️
ESP32_OLIMEX✔️✔️✔️✔️✔️✔️✔️✔️✔️✔️ Wi-Fi + Ethernet✔️
M5Core✔️✔️✔️✔️✔️✔️✔️✔️✔️✔️ Wi-Fi✔️
M5StickC✔️✔️✔️✔️✔️✔️✔️✔️✔️✔️ Wi-Fi✔️
M5StickCPlus✔️✔️✔️✔️✔️✔️✔️✔️✔️✔️ Wi-Fi✔️
M5Core2✔️✔️✔️✔️✔️✔️✔️✔️✔️✔️ Wi-Fi✔️
ST_STM32F429I_DISCOVERY (B01)✔️✔️✔️✔️✔️✔️✔️✔️✔️✔️
ST_NUCLEO64_F091RC✔️✔️✔️✔️✔️✔️✔️✔️
ST_STM32F769I_DISCOVERY✔️✔️✔️✔️✔️✔️✔️✔️✔️✔️✔️✔️✔️
ORGPAL_PALTHREE✔️✔️✔️✔️✔️✔️✔️✔️✔️✔️✔️✔️
TI_CC1352R1_LAUNCHXL✔️
TI_CC3220SF_LAUNCHXL✔️✔️✔️✔️✔️✔️✔️
NXP_MIMXRT1060_EVK✔️✔️✔️✔️✔️

Repositories

Our GitHub organization holds the various repositories for firmware, class libraries, documentation and tools.You can findhere a list and a description of each of them.

How to Engage, Contribute and Provide Feedback

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. We ask you to open an issue only when you have a real and confirmed one.It is best to ask the question on one of ourDiscord channels. Make sure to select the channel that's most appropriate to the context so subject matter experts are most likely to answer promptly. Or you can go over toStack Overflow and ask the question there, make sure to use thenanoframework tag.

If you can't use Discord, you should start a conversation atDiscussion.

Looking for something to work on? Check the list ofup-for-grabs issues on the Home repo, that's a great place to start.

See some of our guides for more details:

License

.NETnanoFramework libraries, firmware images, tools and samples are licensed under theMIT license.

Documentation

The project documentation is a great place to find information about .NETnanoFramework, 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.

Code of Conduct

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.


[8]ページ先頭

©2009-2025 Movatter.jp