13 replies to this topic

[orange]

Hello, I frequently run into cases where MS Visual C# gets stuck or delays deployment where the message is: "Preparing to deploy assemblies to the device." My solution is to disconnect USB and reconnect. Sometimes it fails and I redo, sometimes it simply works and reboots netduino and we are done. Overall this process is very slow and gets on people's nerves. I don't see this in forums being addressed. Is there a solution for this? My firmware and Visual C# are the latest stable versions. Thanks

[Magpie]

I find it a bit tedious too, if it really doesn't want to cooperate Cancel any deploy that is happening. I pull out the usb Tell VS to Deploy app Wait 5 seconds plug in the usb

Edited by Magpie, 13 March 2012 - 11:10 AM.

[orange]

I find it a bit tedious too, if it really doesn't want to cooperate
I pull out the usb
Tell VS to Deploy app
Wait 5 seconds
plug in the usb

Exactly ! ) I found out that's the best path after doing it 200,300 times. Very interesting that you found the same thing.

However, sometimes I have to do fail, cancel, retry. Yet other times even this gets %100 stuck and doesn't go forward after a minute.

Perhaps timing should be kinda accurately 5 seconds...

[Magpie]

I think (but I'm not really sure) that by telling visual studio to download before the Netduino is powered, It gives an oppurtunity to catch the Netduino in the bootloader. Otherwise if you dont catch it in the bootloader and if you have a certain type of bug in your code, possibly a very tight loop, you may somehow never give breathing space to the debug mechanism, to talk with VS via it's normal pins and/or give its thread enough time etc.

[willgeorge]

My solution is to disconnect USB and reconnect.. Mine also.. I have had this problem since day one but I have learned not to let it get to me. Now it is part of the 'fun' of coding the Netduino. I do have to admit that the USB connector on the Netduino is of the best quality based upon the amount of times I have had to unplug and plug it back in ;>). I also have occasional restarting of the Microsoft Visual Express 2010 (Sort of re-boots itself) as in the visual express application closes itself and restarts. It does restart with the Netduino application I was working with. The only thing I know for sure that causes it is having something running in a tight loop as Magpie has noted.

[JerseyTechGuy]

I think (but I'm not really sure)
that by telling visual studio to download before the Netduino is powered, It gives an oppurtunity to catch the Netduino in the bootloader.

Otherwise if you dont catch it in the bootloader and if you have a certain type of bug in your code, possibly a very tight loop, you may somehow never give breathing space to the debug mechanism, to talk with VS via it's normal pins and/or give its thread enough time etc.

I agree with your assessment. I actually built into my menu on my ND+ a "Upgrade" item that stops the tight loop. This enabled the deploy to work reliably.

[Valkyrie-MT]

I have a similar routine of unplugging the USB cable and re-plugging. I usually wait for the blue light on the netduino to go off, but it still doesn't always work. I have a main loop, but I certainly would not characterize it as tight, although I do have multiple threads, each running a loop. I wonder if it could be high CPU Utilization on the Netduino that is blocking or slowing the subsequent deployment.... hmmm. -Valkyrie-MT

[ElectricHillbilly]

I have gotten around this by running the Reboot and Stop command from the plugins -> debug menu in MFDeploy. On my x64 machine, MFDeploy is at C:\Program Files (x86)\Microsoft .NET Micro Framework\v4.1\Tools. I run this command before every deployment, and i havent had the problem creep up on my recently. Could be coincidence, but It seems to work.

[Bendage]

I find it a bit tedious too, if it really doesn't want to cooperate
I pull out the usb
Tell VS to Deploy app
Wait 5 seconds
plug in the usb

What firmware are you using? I upgraded to 4.2 last night and now when I pull the usb plug out I get a Blue Screen of Death. This happening to anyone?

[Magpie]

Yes using 4.2 rc4 you must cancel deploy before pulling out the usb.

[Geancarlo2]

What I used to do was: -cancel deployment/compilation on VS -disable netduino driver on Device Manager -replug netduino into usb -enable netduino once again This solved BSOD issues as far as i remember.

[Bendage]

Am I missing something? When the compiler is waiting for the board to respond, I do not recall a cancel button.

[Geancarlo2]

You gotta add that build toolbar and press the red circled button or hit ctrl+break(on my default configuration).

Attached Files

•  cancel build.png   16.78KB   98 downloads

[Bendage]

Well I'll be dammed! nice find!