13 replies to this topic

[bryancostanich]

when i debug in VS, i often get stuck at "Preparing to Deploy Assemblies to the Device." It just hangs there in that state. i have to cancel the build and force quit VS from task manager and restart. anyone else get this? know what's causing it?

[Phil R]

Yep, I encountered this several times during my first tests yesterday. I'm using Win7 Ultimate on a Parallels VM and VS2010 Professional, if that is interesting. Phil

[greg]

Yep, I encountered this several times during my first tests yesterday. I'm using Win7 Ultimate on a Parallels VM and VS2010 Professional, if that is interesting.

Phil

yes - I'm the user Chris mentioned who's been fighting parallels. Secret Labs has traced it back to the Atmel USB code so they're trying to come up with a fix but for now it's kind of a PITA.

[bryancostanich]

ah, yeah, i'm using parallels as well. tried to use VMWare, but it doesn't work at all in there.

[greg]

ah, yeah, i'm using parallels as well. tried to use VMWare, but it doesn't work at all in there.

VMWare requires serial deployment. I did the competitive upgrade to parallels.

[bryancostanich]

FYI, the .netmf team release a QFE that is supposed to address this. haven't tried it yet, it's here: http://www.netmf.com...86-069caeb293ac

[greg]

FYI, the .netmf team release a QFE that is supposed to address this. haven't tried it yet, it's here: http://www.netmf.com...86-069caeb293ac

It doesn't work.

[bryancostanich]

It doesn't work.

sad robot O_o

[Chris Walker]

We've tested the QFE and can verify that it works with Netduino...but it doesn't address this particular issue. The QFE does include a number of bug fixes that were contributed back to the .NET MF trunk (based on community bug reports and submissions here on the Netduino forums--thanks to the community members here). Chris

[greg]

Sorry, I should have been more precise. As Chris said it doesn't resolve this specific issue with deploying code under parallels.

[DanN]

Hi guys,

I had this error too and managed to solve it.

Since I recently got the new netduino, I realised I am required to do an update to NetduinoFirmware_v4.1.0.3.
I ran the MFDeploy.exe under C:\Program Files\Microsoft .NET Micro Framework\v4.1\Tools
Then browsed to my unzipped NetduinoFirmware_v4.1.0.3 folder and selected all the files inside that folder.
With the USB plugged in and selecting USB which automatically selected the Netduino_Netduino device, I clicked on deploy and it just basically froze.

Solution
So, in order to counter this, I had to end the process tree in the Task Manager. Then unplugged the USB of the netduino.
I openned up the MFDeploy.exe again.
Browsed and Selected the NetduinoFirmware_v4.1.0.3 files.
Ready my USB of the netduino.
Plugged in the USB,
Then QUICKLY:
Selected USB Device
then Click Deploy.
And it began updating.

After that, the debugging in Visio Studio should run well.

Hope this works for everyone.

If you have already updated the firmware and still getting the frozen debugging process, then I could only think of erasing through MFDeploy.exe and then retry debugging it.


DanN

[CW2]

Then QUICKLY: Selected USB Device

Tip: To come around the timeouts, press F5 or launch 'Target/Connect' menu command to establish a connection to the device, then disconnect it (Ctrl+F5) to release the device (e.g. for Visual Studio deployment).

[Crispin]

I get this quite frequently and normally after some dodgy code (hence, frequently ) caused an exception. A quick press of the reset button on the Netduino and VS wakes up. Annoyance which I chalk up to MS

[Chris Walker]

Crispin, The new v4.1.0.6 firmware may alleviate this issue... http://forums.netdui...pdate-6-beta-1/ Chris