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. 

Hi everyone

I've been revisiting this community over the past days and thought I would send out a link to this real time clock driver I wrote for the Maxim DS3232. I've been able to get it working for all but the alarm -- mainly due to lack of time to complete it. Anyone ambitious enough could fill in this last remaining class, or else I will sometime.

If there are any questions feel free to message me on this site or post to this forum. Enjoy!

https://github.com/b...k/RealTimeClock

I resorted to 4.1 firmware and do not encounter this issue. Both TinyCLR and RESET are working.

After looking through the posts here, I see that the 4.2.0.0 firmware is not available. Does anyone have a copy of it that I can test?

Although this doesn't answer your question, I just read a nice article that makes an argument against software watchdogs:

http://www.ganssle.com/watchdogs.htm

I found this article on Hackaday: http://hackaday.com/...iting-code-etc/

I deployed a simple LED blinker program to the Mini and it works great. But, when I power cycle, the program doesn't boot up until I clear the boot flag in MFDeploy. 

I'm also noticing that my RESET pin isn't working. If I ground the pin, the Mini is not rebooting. 

I want to add to this post by saying that I also tried loading the TTL version of the firmware with the same behavior. I'm going to try to deploy some code and see what happens.

I have flashed my Netduino Plus in the past and I didn't run into this. 

I just upgraded my mini to 4.2 firmware and bootloader over RS232. Each time I power cycle and ping from MFDeploy, I get a response from TinyBooter instead of TinyCLR. 

The catch is that if I go to 'Debug' in MFDeploy and clear bootloader flag, I receive response from TinyCLR after ping. 

I'm sending /RESET pin 22 to 3.3V to avoid activating reset during start-up. Does anyone have any suggestions?

Thanks for the help in advance.