I have a Netduino Plus on which I have been developing on for a year. My application was running on it just fine but I just got it back from the field to do a application update. I could not get .NET 2010 dev system to connect to the board. MFDeploy would only occasionally connect and it showed v188.8.131.52. I deleted .NET and Netduino SDK and updated to 184.108.40.206 and then erased the board. When replugged into the PCs USB port, it installed a atmel6124.sys driver. I ran SAM-BA and installed the TinyBootloaderDecompressor.bin from the 220.127.116.11 firmware release. Now MFDeploy does not see the board at all. I uninstalled the atmel driver and reconnected the Netduino and it reinstalled the atmel driver.
I am using Win XP. What am I doing wrong. I really need to get this up and running quickly to get it back out for testing.
Update: I updated SAMBA from 2.1.0 to 2.1.2 with patch and reinstalled the driver. Now SAMBA does not display anything after the connection page is clicked through. It just keeps getting better.
Further update: Removed patch, rebooted PC, now SAMBA works. Still doesn't change the device id to Netduino.
Following the step by step installation carefully turned the brick into a Netduino. So far so good.
VS will still not deploy or debug the code.
MFDeploy 18.104.22.168 pings okay every time but Device/Capabilities says "Not Supported"
Redid the firmware update and now MFDeploy works okay. Still can't deploy or debug from VS
If I unplug the USB cable after starting the Deploy it deploys. Pretty ugly but if that's what has to happen then it will be done.