Shield Request: Self-upgrade shield
#1
Posted 07 November 2010 - 01:10 AM
#2
Posted 07 November 2010 - 08:28 AM
#3
Posted 08 November 2010 - 03:54 AM
#4
Posted 08 November 2010 - 07:28 AM
There is "Remote firmware update middleware" feature in the official .NET Micro Framework roadmap planned (resp. committed) for the next release, and "Most likely an HTTP-based implementation will be provided as well as a sample...".By network, or any other data path over which the firmware could be passed and then stored on the NVRAM.
#5
Posted 08 November 2010 - 09:55 AM
#6
Posted 08 November 2010 - 06:09 PM
#7
Posted 09 November 2010 - 11:52 PM
What I think would be far more useful would be the ability to update your own code over ethernet rather than the firmware. Firmware updates aren't that frequent, and if there's a problem your device is probably not in use.
Bug fixes and updates to my own code in my permanently installed home automation application however - fairly likely.
It's all stored in the flash, be it our own app or the .NET firmware. The idea was to have a prebaked flash upgrade package that contains the firmware and our own app ready to go that could simply be copied to the chip's internal flash by the boot loader upon discovery.
Alternatively, I don't see any reason why an app couldn't be loaded on its own in the same manor, this would just require the boot loader to be able to recognize the difference and load the app at the appropriate address.
#8
Posted 21 November 2010 - 06:50 AM
#9
Posted 21 November 2010 - 06:00 PM
Any news on something like this, even if it is just for our managed code?
Hi Charles,
Were you proposing building something like this? Asking to start a community project to build one? Asking for us to build one? Etc.
From your initial post, I assumed that you were thinking of building such a shield...
Chris
#10
Posted 21 November 2010 - 06:36 PM
#11
Posted 21 November 2010 - 07:15 PM
Does that mean that it would be technically possible to do this without the external storage?
Yes. You could use appdomains to do this on the fly through 100% managed code, or could build a feature into the Netduino firmware which would download and replace the application on the fly.
[Theoretically, you could also send the Netduino bootloader and/or firmware over the network, save it to an SD card and then read it back and reflash. Lots of possibilities.]
There's some work being done to support this with .NET Micro Framework 4.2. We don't want to duplicate that, but perhaps we can get an early cut of it ported over... It's very early right now.
Chris
#12
Posted 21 November 2010 - 10:44 PM
0 user(s) are reading this topic
0 members, 0 guests, 0 anonymous users