nickfenlon

Paul Newton, you legend! That was exactly it, all I need to see was that one little thing.

Originally when I followed this tutorial, I didn't know where "MFDeploy" was coming from so I googled it and downloaded it from Microsoft. Watching the video you recommended I noticed that the guy was running MFDeploy from his MF4.2 installation!!! That was the Key.

The standalone MFDeploy didn't see my Netduino. The Version that's bundled with the Micro Framework did!!!!!!! I'm up and running again.

This not withstanding, I did still have problems with SAM-BA running on Win7.

Upgrade from MF4.1 to 4.2 gone horibly wrong on Netduino Plus!!! Please help.

Ok so after just one day of using my Netduino Plus, I decided to upgrade to MF4.2 so I can code in VB.

Started by following this: http://wiki.netduino...ep-by-step.ashx

But then realised I needed to install TinyBooterDecompressor as per these instructions: http://wiki.netduino...ep-by-step.ashx

Had a lot of trouble on Win7 64bit when trying to connect to the device with SAM-BA. Couldn't select any com port in the drop down box so coundn't connect to the device to re-flash.... Moved the whole setup over to an XP 32bit machine and found I was able to connect via the correct com port.  I got the TinyBooterDecompressor flashed on and now the Netduino appears as it should in the Device manager.

https://dl.dropbox.c...1562481/xx1.JPG

Now the problem I have is that when I run MFDeply I cant find my device to connect to in the drop down box!!!!!

https://dl.dropbox.c...1562481/xx2.JPG

I've fully gone through this thread and I've tried this on both XP & Win7. I've tried erasing the flash in SAM-BA. I've tried using the other set of drivers in the mfusb folder as well as the winusb drivers.

I cannot get any good of this and now I'm about the microwave my Netduino!!!!!!!!!!

Please please please can anyone help?

Thanks