Dan Kowalczyk

Hi, is there a way to deploy via Xamarin Studio running on Windows?

Chris,

Thanks for the helpful outline of the steps involved. It's a bit over my head at this point in time, but it's a worthy goal and I wouldn't mind the learning experience. I will definitely read through the current drivers for inspiration.

I've forked the GitHub repo you linked to and will add a directory to house the gen1 ARM link layer code. Anyone who would like to contribute, please send your pull requests!

Thanks

Dan

Is there any progress on fixing this firmware bug for 4.2.0.1? Will it be more likely to expect 4.3?

Hi Chris, I would be interested in having .NETMF 4.3 run on NP1. What would need to happen for 4.3 firmware to fit on NP1?

EDIT: To be more specific, where can I start learning about the Netduino.IP stack? What are the steps involved in porting it to gen1?

I have been researching this topic and the best sources for understanding this feature have been the following articles:

• http://msdn.microsof...y/ee435036.aspx
• http://msdn.microsof...y/ee435045.aspx

From these articles and others on this forum, you can create a deployment by

1. Deploying through Visual Studio to the device
2. Using MFDeploy to create a .hex file and signing it with a key pair generated through MFDeploy

Now, the firmware you install on the Netduino (or other .NET Micro Framework device) can only be updated by those who can provide the public key associated with the private key used to sign the device application deployment.

Although I have been able to create deployment images, sign them with keys, and manage device keys for my firmware and deployment sectors, it all hasn't seemed to work. I am still able to load unsigned images onto my device. I will report back if I figure this out.