Bryan T

In theory, if you have trouble then just repower the Netduino by detaching and reattaching its USB cable.

If there's a scenario where the 4.2 firmware is causing a Netduino to get into an invalid state, we would love a repro case. The new WinUSB drivers require changes to a few "old ways of doing things" but they shouldn't get Netduino into an invalid state.

Thank you for posting about this. I'm glad it's working for you now. If you have any other troubles, please let us know!

Chris

Chris, as Nak said, what appears to happen is that if, after you have flashed to the new firmware, you attempt to edit the network settings while you are in "tinyCLR" mode (of course, you won't be successful), then you repower the N+ while holding down the button to get to "tinybooter"mode, It will now stay in that mode until you reflash the firmware. Cycling power has no effect. As long as you don't try to change those network settings while in the "tinyCLR" mode, everything works correctly.

I got ahead of myself the first time and forgot that I had to go through the "hold the button" step to reset the network stuff, or I wouldn't have seen the issue.

Bryan

I have had this happen if I have tried to set nework settings in tinyclr mode, as stated reflashing seems to fix everything



Nak.

Yes, that seems to be the issue. I did that the first time. I have now flashed two more N+'s and have no issues.

I had the same problem. After repeating the whole process of flashing it just worked.

Yeah, I just reflashed and everything's OK. Interesting.

I'm going to show my ignorance here, but how does an LM317T compare to those mentioned above? I happen to have one of those I've been playing with.

Hi Bryan,


If you start with a Netduino Plus template, you'll want to remove the "System.Net" and "System" assembly references and swap out the "NetduinoPlus" dll for the "Netduino" dll.

You can deploy Netduino projects to a Netduino Plus without change...although you'll need to select your board in the project properties (USB transport).

Chris

Thanks Chris. That's exactly the info I was looking for.