GHI is excited to bring you NETMF 4.2 to all available devices. This only happens after plenty of testing and evaluation and there are many libraries to be moved to NETMF 4.2, so this is major work and take a while to complete. Also, this is an opportunity for GHI to make breaking changes on the libraries if necessary.
We offers 3 SDKs that need to be changed, GHI Premium SDK, GHI OSHW SDK and GHI Gadgeteer SDK.
So, here is the plans:
NETMF 4.2 OSH SDK beta for FEZ Cerberus (and its derivatives) - March.
Validate functionality and test with gadgeteer 4.2 (we need Gadgeteer 4.2 from Microsoft first) - April.
Completely move GHI OSH SDK and GHI Gadgeteer SDK to NETMF 4.2, including Hydra - April/May
A beta for GHI SDK 4.2 (USBizi, EMX, CWX…) May
Those are estimates not guarantees. GHI is not guaranteeing 4.2 will be available for older devices and no plans on what devices to drop yet, maybe none. To learn when new releases are available, watch the beta forum or subscribe to one of our channels (RSS, Twitter, facebook, google+) http://www.ghielectronics.com/contact/
I have bought the FEZ Spider Starter Kit. How will I be able to upgrade that to 4.2, once you guys support this? Will this be through some kind of firmware upgrade ?
I tell you what, I too am new to this and am confused about what will run on what boards.
In fact, I have spent some time re-arranging code of existing projects to make them work on the hardware I have.
It would probably be helpful to other beginners if I could re-post code on the forums that’s been re-arranged to work on different hardware. Is that allowed? Obviously I wouldn’t pass it off as my own work, I just kept hitting it until it started working!
I know Cerbuino is beta, but I’m trying to get OneWIre to work with it - and I’m unclear on which assembly it would need. Cerbereus is 4.2 only, the latest package has GHI NETMF v4.1 - which has the GHIElectronics.NETMF.Hardware.DLL.
So am I taking crazy pills, or should this not work? Additionally, what are he LE and BE directories with the same assemblies within he package?