PhilG

Chris,

Thanks for the reply.

I think I followed the directions correctly.  It tells me that the specified location does not contain information about my hardware and then cycles back to the previous screen (see attached). 

More info:  I tried uninstalling the driver first and got the same result.  I also downloaded the SDK again and ran repair but that didn't help. 

So, if I were to replace my NPs  with NP2's would this problem be fixed along with the data corruption problems I have had after writing to SD and power cycling?  I need to spend more of my time doing code development.

If I hold the reset button while powering up my Netduino + it sometimes works.  Very flakey though.  You know when it's going to work if you do a Ping and it returns info on the bootloader rather than the TinyCLR.

Noom,

Ok. Does the Netduino Plus have the abiltiy to notify my program of  brownout or power down to allow me to take the appropriate action?  And, do I have program control over mounting and unmounting?  Should I mount, write and unmount each time?

Chris,

I was able without too much further difficulty get my system debugged and deployed.  So now I thought it's time to build a second prototype to replace the one shiping out for further testing.  The process of updating the board didn't go any better than the first one.  After erasing a reinstalling a couple of times it is now okay. 

On another topic, how can I have someone in the field who doesn't necessarily have VS2010 update the application code? 

Phil

Chris,

Today it seems to working without a problem. It was a long drudge to get to this place with a few cockpit errors thrown in because of the fiddly firmware update process.  So now with 4.2.0.1 things are working pretty well.  I did run into a problem where my app was debouncing IO pins with a case statement that had to change to else ifs because the pin definitions are no longer CONSTs but are STATICs.  It was a surprise but not a show stopper.  During the development last year I spent as much time babying the VS/Netduino connections than doing app development.  Hopefully that will no longer be the case. 

I think I will leave things as they are now and get back to development.

Thanks for the reply.

Phil