The Netduino forums have been replaced by new forums at community.wildernesslabs.co.
This site has been preserved for archival purposes only
and the ability to make new accounts or posts has been turned off.
If EnableStaticIP writes to flash, will each call to it write, or only if changed? Reason I ask is because I call EnableStaticIP in the NetworkAvailabilityChanged handler, and when a socket exception occurs.
Is this a bad idea? If so, what should be in the NetworkAvailabilityChanged handler?
I would recommend changing the IP settings only when they need changing. It's best to assume that changing the IP configuration will write to the setting sector in flash.
OK, what code should go into the NetworkAvailabilityChanged handler?
Are you using a Static IP or DHCP?
If you're using a Static IP, you shouldn't need to do anything in the NetworkAvailabilityChanged handler. And actually, same goes for DHCP--it _should_ automatically get an address.
If these are not happening properly in the latest .NET MF 4.2 beta, then we should file a bug report on netmf.codeplex.com. Now's the perfect time to fix bugs in the NETMF lwIP implementation...before NETMF 4.2 goes gold.
We'll dig into it and make sure we're not exposing any nasty "gotchas". The space is very limited, and some of it is already taken (by the USB name, networking, etc.). My biggest worry is what would happen if the data were written only partially before a reset...and then the device might not be able to boot. Since the whole sector might have to be re-written all at once.
We'll dig into it. I'll post more when I have some good info...
I would recommend changing the IP settings only when they need changing. It's best to assume that changing the IP configuration will write to the setting sector in flash.
Chris
Ouch!!!! Writing the IP address to flash with every call is a nasty side effect for that subroutine - I have been calling it in a function that runs every single time my test N+ boots! I wonder how many writes I have left in the config block??? I wonder how many other people are burning up there N+'s by not knowing that?
Seriously - There needs to be an optional Boolean parameter added to that function that tells it to just change the IP, not write it to the config sector. Even better, make it so you HAVE to tell it to write the new IP into flash before it does!
Seriously - There needs to be an optional Boolean parameter added to that function that tells it to just change the IP, not write it to the config sector. Even better, make it so you HAVE to tell it to write the new IP into flash before it does!
This might be a good recommendation to make for the .NET Micro Framework "vNext". Could you post a feature request for this at netmf.codeplex.com?
Hey there, is this still in work, so we can give hope on this ?
Yes there is still some work on this, but there is relatively little room left after all the new 4.2 features.
It looks like there is some progress on bugfixes for the 4.2 core (netmf.codeplex.com). Once the firmware goes gold, we'll be able to dig into this with more speed.
Yes there is still some work on this, but there is relatively little room left after all the new 4.2 features.
It looks like there is some progress on bugfixes for the 4.2 core (netmf.codeplex.com). Once the firmware goes gold, we'll be able to dig into this with more speed.
Chris
Chris any news about that feature? Thanks a million
Hey John,
We're going to pull this feature over from our AGENT codebase. It should be making it into a Netduino 4.3.x release for Netduino 2, Netduino Plus 2 and Netduino Go a bit later this year.
Chris
