Embedded Master User Manual

The Microsoft .NET Micro Framework combines the reliability and efficiency of managed code with the premier development tools of Microsoft Visual Studio to deliver exceptional productivity for developing embedded applications on small devices.

The .NET Micro Framework brings a rich, managed-code environment to smaller, less expensive, and more resource-constrained devices. Requiring only a few hundred kilobytes of RAM and an inexpensive processor, the .NET Micro Framework was built from the ground up to let you build applications using familiar Visual Studio development tools. With .NET Micro Framework SDK, you can develop your embedded solutions in C# using a subset of the .NET libraries focused on embedded applications. Your development environment is Visual Studio, where you can take advantage of its powerful editing, object browsing, project management, and debugging capabilities. These capabilities are available when using the .NET Micro Framework SDK’s extensible device emulation system or on real hardware.

What is Embedded Master Module
Embedded Master Module a very small hardware module (1.55”x1.55” for Revision 2.x - 1.55”x1.8” for TFT version) that is programmed to host the Microsoft .NET Micro framework. Developers can now use .NET Micro Framework and write managed code (C#) without having to deal with much complexity and without the need to acquire any license from Microsoft for using .NET Micro Framework. Embedded Master Module license for .NET Micro Framework is covered by GHI Electronics.

Not only .NET Micro Framework, Embedded Master Module has many exclusive additional features that are not supported in any other .NET Micro Framework device. Files can be accessed using the embedded FAT file system. Those files can be on SD card or on USB memory devices. Other peripherals libraries are also natively added such as Analog inputs, Analog outputs, PWM and more.
All libraries are written below the CLR layer, in the HAL layer. They are not managed libraries; for that, these libraries run much faster. Above CLR layer, there are manged “wrappers” so users can use the unmanaged libraries.

Get pdf Embedded Master User Manual

Related Searches: , , , ,

Comments

Leave a Reply