EDIT: Link to the ports collection:
Alright, I’m ready to take the plunge and start a community edition fork of NETMF. I’m looking for suggestions, ideas, and organizational tips from other members of the community.
Right now, I can picture the community edition consisting of two branches:
Mainline 4.3 + community extras + community ports
This branch would use a stable NETMF 4.3 base, but also include extra functionality in the form of additional interop libraries (Native DSP, image processing routines, whatever).
It would contain forks of all the GHI OSHW ports with community bugfixes (as well as other ports for other platforms). It would also contain support for non-GHI boards and other new platforms (we could really use a SAM4S port right now, as well as a high-performance port targeting one of the 400 MHz ARM9 MCUs) .
This branch would also contain native drivers for devices (and device types) not currently supported by NETMF.
This branch would compile under both GCC and MDK, and all components would be Solution Wizard-compatible, which would allow novice users to quickly add and remove features without having to mess with all the XML configuration files. Since solutions would compile against the mainline 4.3 branch, users would be able to use the existing 4.3 SDK to develop applications.
This branch contains everything above, but breaks compatibility with the 4.3 SDK by introducing bug fixes and new features to core NETMF components. Because of this, this branch’s ports would not work with the 4.3 SDK.
Two separate branches can be a hassle to take care of, but while I’m interested in making core modifications to NETMF, I’m sure there are lots of developers who just need something simple fixed, or would like a native method to do ____. The Community Edition would provide a place for people to experiment, as well as to get problems fixed quickly.
I have an SVN repository set up with mainline 4.3 + the GHI open source ports + NicolasG’s Cerberus changes with quadrature encoder functionality. My changes that are part of the initial fork:
[ul]New “PacketRadio” HAL library category, which will support packet-based wireless transceivers.
CC1101 support for the above-mentioned HAL category
Managed interface to the PacketRadio HAL library category
Bugfixes to SPI interface on STM32F4 builds
Additional native utilities methods for doing things with arrays[/ul]
And soon to come:
[ul]Full power management support for STM32F4
Managed partial implementation of SimpliciTI WSN protocol
Native DSP library[/ul]
I’d love to hear people’s comments, concerns, and questions!