Netduino home hardware projects downloads community

Jump to content


Photo

Unable to deploy without disconnect\reconnect USB cable


  • Please log in to reply
27 replies to this topic

#1 Earthed

Earthed

    Member

  • Members
  • PipPip
  • 20 posts
  • LocationAustralia

Posted 25 July 2011 - 11:40 PM

Hi List, Problem: I'm finding that I can not deploy and debug each time without disconnecting and reconnecting the USB cable to the NetduinoPlus RevB. I'm worried I'll wear out the USB socket! Besides that, it's damned annoying! and a total time waste. I'm using the following: C#.NET Express 2010 v4.0.30319 SP1 Rel .NET Micro Framework v4.1 01014-169-2560017-70953 Netduino Plus Rev.B Board Is anyone else experiencing this? I find that the project builds fine, and runs fine after a disconnect\reconnect Sometimes the Error window shows: An error has occurred: please check your hardware If I stop debugging - and program does not exit programatically, and then try and restart the debugger the output window only shows the following: (no errors are show) ===================================================================================== Incrementally deploying assemblies to device Deploying assemblies for a total size of 18652 bytes ===================================================================================== Below is the Output window when its working correctly: ===================================================================================== Rebooting... TinyCLR (Build 4.1.2821.0) Starting... Found debugger! Create TS. Loading start at 14d29c, end 162dd4 Attaching file. Assembly: mscorlib (4.1.2821.0) (3880 RAM - 33236 ROM - 19134 METADATA) Attaching file. Assembly: Microsoft.SPOT.Native (4.1.2821.0) (1144 RAM - 6516 ROM - 4479 METADATA) Attaching file. Assembly: Microsoft.SPOT.Hardware (4.1.2821.0) (1752 RAM - 11440 ROM - 7371 METADATA) Attaching file. Assembly: Microsoft.SPOT.Net (4.1.2821.0) (704 RAM - 5060 ROM - 2452 METADATA) Attaching file. Assembly: System (4.1.2821.0) (872 RAM - 5992 ROM - 3206 METADATA) Attaching file. Assembly: Microsoft.SPOT.IO (4.1.2821.0) (740 RAM - 4620 ROM - 2522 METADATA) Attaching file. Assembly: System.IO (4.1.2821.0) (1548 RAM - 13292 ROM - 5862 METADATA) Attaching file. Assembly: Microsoft.SPOT.Hardware.SerialPort (4.1.2821.0) (508 RAM - 3440 ROM - 1527 METADATA) Attaching file. Assembly: Microsoft.SPOT.Hardware.Usb (4.1.2821.0) (580 RAM - 3740 ROM - 1844 METADATA) Attaching file. Assembly: SecretLabs.NETMF.Hardware (4.1.0.0) (256 RAM - 1108 ROM - 491 METADATA) Attaching file. Assembly: SecretLabs.NETMF.Diagnostics (4.1.0.0) (180 RAM - 440 ROM - 166 METADATA) Loading Deployment Assemblies. Attaching deployed file. Assembly: SecretLabs.NETMF.Hardware.NetduinoPlus (4.1.0.0) (268 RAM - 816 ROM - 423 METADATA) Attaching deployed file. Assembly: SecretLabs.NETMF.Hardware.Netduino (4.1.0.0) (268 RAM - 796 ROM - 423 METADATA) Attaching deployed file. Assembly: Microsoft.SPOT.Graphics (4.1.2821.0) (388 RAM - 2268 ROM - 1357 METADATA) Attaching deployed file. Assembly: NetduinoPlusLibrary (1.0.0.0) (1532 RAM - 14768 ROM - 5198 METADATA) Resolving. Total: (12776 RAM - 107532 ROM - 56455 METADATA) Total: (12776 RAM - 107532 ROM - 56455 METADATA) The debugging target runtime is loading the application assemblies and starting execution. Ready. 'Microsoft.SPOT.Debugger.CorDebug.dll' (Managed): Loaded 'C:\Program Files\Microsoft .NET Micro Framework\v4.1\Assemblies\le\mscorlib.dll', Symbols loaded. 'Microsoft.SPOT.Debugger.CorDebug.dll' (Managed): Loaded 'C:\Program Files\Microsoft .NET Micro Framework\v4.1\Assemblies\le\Microsoft.SPOT.Native.dll', Symbols loaded. 'Microsoft.SPOT.Debugger.CorDebug.dll' (Managed): Loaded 'C:\Program Files\Microsoft .NET Micro Framework\v4.1\Assemblies\le\Microsoft.SPOT.Hardware.dll', Symbols loaded. 'Microsoft.SPOT.Debugger.CorDebug.dll' (Managed): Loaded 'C:\Program Files\Microsoft .NET Micro Framework\v4.1\Assemblies\le\Microsoft.SPOT.Net.dll', Symbols loaded. 'Microsoft.SPOT.Debugger.CorDebug.dll' (Managed): Loaded 'C:\Program Files\Microsoft .NET Micro Framework\v4.1\Assemblies\le\System.dll', Symbols loaded. 'Microsoft.SPOT.Debugger.CorDebug.dll' (Managed): Loaded 'C:\Program Files\Microsoft .NET Micro Framework\v4.1\Assemblies\le\Microsoft.SPOT.IO.dll', Symbols loaded. 'Microsoft.SPOT.Debugger.CorDebug.dll' (Managed): Loaded 'C:\Program Files\Microsoft .NET Micro Framework\v4.1\Assemblies\le\System.IO.dll', Symbols loaded. 'Microsoft.SPOT.Debugger.CorDebug.dll' (Managed): Loaded 'C:\Program Files\Microsoft .NET Micro Framework\v4.1\Assemblies\le\Microsoft.SPOT.Hardware.SerialPort.dll', Symbols loaded. 'Microsoft.SPOT.Debugger.CorDebug.dll' (Managed): Loaded 'C:\Program Files\Microsoft .NET Micro Framework\v4.1\Assemblies\le\Microsoft.SPOT.Hardware.Usb.dll', Symbols loaded. 'Microsoft.SPOT.Debugger.CorDebug.dll' (Managed): Loaded 'C:\Program Files\Secret Labs\Netduino SDK\Assemblies\v4.1\le\SecretLabs.NETMF.Hardware.dll', Symbols loaded. 'Microsoft.SPOT.Debugger.CorDebug.dll' (Managed): Loaded 'SecretLabs.NETMF.Diagnostics' 'Microsoft.SPOT.Debugger.CorDebug.dll' (Managed): Loaded 'C:\Program Files\Secret Labs\Netduino SDK\Assemblies\v4.1\le\SecretLabs.NETMF.Hardware.NetduinoPlus.dll', Symbols loaded. 'Microsoft.SPOT.Debugger.CorDebug.dll' (Managed): Loaded 'C:\Program Files\Secret Labs\Netduino SDK\Assemblies\v4.1\le\SecretLabs.NETMF.Hardware.Netduino.dll', Symbols loaded. 'Microsoft.SPOT.Debugger.CorDebug.dll' (Managed): Loaded 'C:\Program Files\Microsoft .NET Micro Framework\v4.1\Assemblies\le\Microsoft.SPOT.Graphics.dll', Symbols loaded. 'Microsoft.SPOT.Debugger.CorDebug.dll' (Managed): Loaded 'F:\NETDIONU.MASTER\Dev\NetdionoPlus_ALL\Blinking LED\bin\Debug\le\NetduinoPlusLibrary.exe', Symbols loaded. The thread '<No Name>' (0x2) has exited with code 0 (0x0). Gateway: 10.0.0.138, IP: 10.0.0.111, Mask: 255.255.255.0 =====================================================================================

#2 Chris Walker

Chris Walker

    Secret Labs Staff

  • Moderators
  • 7767 posts
  • LocationNew York, NY

Posted 25 July 2011 - 11:59 PM

Hi earthed, Sorry for the trouble there. Let's see if we can assist... What happens if you tap the reset button on the Netduino Plus? Does that help the debugger reconnect? If you want to post a bug report over at netmf.codeplex.com, there's a chance that Microsoft can address this in the .NET MF 4.2 SDK (if they haven't already). Welcome to the Netduino community, Chris

#3 Mike P

Mike P

    Advanced Member

  • Members
  • PipPipPip
  • 41 posts
  • LocationAuckland, New Zealand

Posted 26 July 2011 - 10:00 AM

Same thing happens to me. If I hit the reset button then the I need to replug the usb connection before visual studio will reconnect to it. Running WinXP32. NetduinoPlus 4.1.0.6

#4 Dan Morphis

Dan Morphis

    Advanced Member

  • Members
  • PipPipPip
  • 188 posts

Posted 26 July 2011 - 08:01 PM

Problem:
I'm finding that I can not deploy and debug each time without disconnecting and reconnecting the USB cable to the NetduinoPlus RevB. I'm worried I'll wear out the USB socket! Besides that, it's damned annoying! and a total time waste.


I experienced those issues as well. What I did to work around the issue was build a USB on/off switch.

While still slightly annoying, its much faster to toggle the switch than plug and unplug.

-dan

#5 Mike P

Mike P

    Advanced Member

  • Members
  • PipPipPip
  • 41 posts
  • LocationAuckland, New Zealand

Posted 30 August 2011 - 09:47 PM

I thouth I would give this thread another kick to see if anyone else has any ideas. Is this behaviour normal then? Does everyone just unplug their netduino every time they deploy? I've tried all the available firmwares in the hope this might be a bug that has been addressed. 4.106 through to 4.2RC1

#6 Scott Green

Scott Green

    Advanced Member

  • Members
  • PipPipPip
  • 34 posts

Posted 01 September 2011 - 04:35 PM

I am running the 4.1.1 Onewire ALPHA firmware, and I have the same problem. Every time I want to move code over the the netduino I have to unplug USB power to get it to send the code over. I hit the reset button but it doesnt help. Interesting thing though. Seems like it should be completely unrelated, but this problem seems to happen more often the larger your code gets. When I first got my new netduino it was working fine with small programs, now I am up to the point where I only have about 20k free memory and I have the problem every time I try to debug or deploy. I'm hoping that the 4.2 release helps. Scott...

#7 Chris Walker

Chris Walker

    Secret Labs Staff

  • Moderators
  • 7767 posts
  • LocationNew York, NY

Posted 01 September 2011 - 05:59 PM

Hi Mike, Are you writing large amounts of info out via Debug.Print? This can happen if the debug output stream is too busy and Visual Studio "can't get a word in edge-wise..." Otherwise, this might be a good issue to bring up on the netmf.codeplex.com site...a recommendation for something to tweak in the desktop-side SDK. Chris

#8 Valkyrie-MT

Valkyrie-MT

    Advanced Member

  • Members
  • PipPipPip
  • 315 posts
  • LocationIndiana, USA

Posted 01 September 2011 - 06:40 PM

I am running the 4.1.1 Onewire ALPHA firmware, and I have the same problem. Every time I want to move code over the the netduino I have to unplug USB power to get it to send the code over. I hit the reset button but it doesnt help.


Yup, I have been doing the same thing. When you are debugging, if you press stop in VS, I think the debugger detaches, but the app continues running on the netduino. Then when you try to run again it won't reset the Netduino and start up. And I also noticed that it happened more with large applications. I have a routine now where I stop the debugger, make my code changes, unplug USB, re-plug USB, then when the onboard blue LED goes out, I immediately run. That sequence works well for me and doesn't really bother me much anymore. 4.2 does not fix it. In fact, if you press the reset button before the debugger detaches, you get a BSOD after the 4.2 upgrade. Also, if I disconnect the USB when a deployment does not work, I get a BSOD. I have to Cancel the Build in VS and wait for the cancel to complete. Then, it becomes safe to replug the USB. I've been doing this since the 4.2 Beta was released. Oh well...

I am VERY concerned though that this will GREATLY discourage new users. BSODs are NOT acceptable.

I am running Windows 7 x64.

It seems clear that the problem is not the actual device firmware, but the software that comes with 4.2. Because I have since gone back to 4.1 firmware builds that previously had no BSOD issues, but now have the BSOD problem. But, both 4.1 and 4.2 versions need the USB replug with big apps.

-Valkyrie-MT

#9 Chris Walker

Chris Walker

    Secret Labs Staff

  • Moderators
  • 7767 posts
  • LocationNew York, NY

Posted 01 September 2011 - 07:28 PM

Hi Valkyrie-MT, We and the community are working with Microsoft to fix the BSOD issue in the NETMF 4.2 SDK/drivers before .NET MF 4.2 officially ships. Thank you for any/all crash data you can submit at codeplex relating to this issue. http://netmf.codeple...m/workitem/1049 Chris

#10 Scott Green

Scott Green

    Advanced Member

  • Members
  • PipPipPip
  • 34 posts

Posted 02 September 2011 - 04:02 AM

So I read all of the comments on CodePlex. Are they not able to recreate this problem? I can recreate it 100% of the time. I can never deploy my current app without having to unplug the USB cable and replug. It happens every time. This bug is so obvious I dont understand why they cant re-create it if that is the problem. Such a pain in the butt. Scott...

#11 Chris Walker

Chris Walker

    Secret Labs Staff

  • Moderators
  • 7767 posts
  • LocationNew York, NY

Posted 02 September 2011 - 04:18 AM

Hi Scott,

So I read all of the comments on CodePlex. Are they not able to recreate this problem? I can recreate it 100% of the time. I can never deploy my current app without having to unplug the USB cable and replug. It happens every time.

This bug is so obvious I dont understand why they cant re-create it if that is the problem. Such a pain in the butt.

If you erase your current app (using the Erase button in MFDeploy), do you have the same deployment issue?

Unfortunately, it seems like this is an issue specific to certain computer hardware. If you can consistently reproduce it with the latest .NET MF 4.2 release, please post a bug report on netmf.codeplex.com.

Chris

#12 Scott Green

Scott Green

    Advanced Member

  • Members
  • PipPipPip
  • 34 posts

Posted 06 September 2011 - 04:31 PM

Hi Scott,

If you erase your current app (using the Erase button in MFDeploy), do you have the same deployment issue?

Unfortunately, it seems like this is an issue specific to certain computer hardware. If you can consistently reproduce it with the latest .NET MF 4.2 release, please post a bug report on netmf.codeplex.com.

Chris


Spent all of the long weekend coding / debugging. Probably spent more time unpluging the Netduino+ than I actually did debugging and coding.

Erasing the app seems to work about 50% of the time. Again, I'm running the 4.1.1 Onewire Alpha firmware. I'd love to try the 4.2 RC but I've not seen a onewire build for that version yet. Couple of questions:

1) Not sure what everyone means by blue screen of death. Are you talking about the PC BSODing when you unplug, or the Netduino? Not sure how the netduino BSODs, but I know what a PC BSOD is, and that is not happening to me. Basically what happens is that the deployment just freezes. I have to unplug / replug the netduino 2 or more time to get it to work. Question: Is the 4.2 update causing the PC to BSOD on usb unplug during deployment? If so, I definately dont want to add more frustration to the process to have to reboot every time I change 1 line of code during a debug session.

2) Is there still additional data that is needed from users to resolve this problem? I see quite a bit of back and forth on Codeplex, but I do not see any mention of having everything that is needed to solve the issue.

Scott...

#13 Cabadam

Cabadam

    Advanced Member

  • Members
  • PipPipPip
  • 90 posts

Posted 06 September 2011 - 05:40 PM

Question: Is the 4.2 update causing the PC to BSOD on usb unplug during deployment? If so, I definately dont want to add more frustration to the process to have to reboot every time I change 1 line of code during a debug session.


I do believe some people started experiencing the BSOD after upgrading to 4.2. That said, I did the upgrade this weekend and spent an evening doing development without experiencing a BSOD. I did have many occasions where the deployments stopped working and I had to unplug/plug it back in though.

I have not yet tracked it down to a particular cause yet. At one point I thought it might be somehow related to how the VS Debugger disconnects (aka: "Detach" vs "Stop"), but I believe I've now seen it occur both ways.

#14 Scott Green

Scott Green

    Advanced Member

  • Members
  • PipPipPip
  • 34 posts

Posted 12 September 2011 - 04:25 PM

Hi Mike,

Are you writing large amounts of info out via Debug.Print? This can happen if the debug output stream is too busy and Visual Studio "can't get a word in edge-wise..."

Otherwise, this might be a good issue to bring up on the netmf.codeplex.com site...a recommendation for something to tweak in the desktop-side SDK.

Chris


Any update on this bug? Looks like they recommended some firmware changes on Codeplex, but thats the last thing I saw that indicated any progress had been made on resolution.

Scott...

#15 mcinnes01

mcinnes01

    Advanced Member

  • Members
  • PipPipPip
  • 325 posts
  • LocationManchester UK

Posted 12 September 2011 - 07:05 PM

I too am having this issue, but I have litterally been unable to deploy any code that interfaces with any devices. The only things that have deployed are LED blink and button push. This has been going on for 2 weeks, the crystal on my RTC had stop working so the time was no longer incrementing, the code I was using hadn't really changed much for a while and neither had my hardware. I removed the rtc and commented out all related lines so I could continue working while I waited for my replacement. Nothing really changed in the meantime then I replace the RTC in my circuit and uncommented the lines, went to deploy and found this problem and it wont go away. I have strip my project down to individual parts, just the 1-wire temp probe (using the 4.1.1 firmware by the way and have been issue free till this point) and related code, no joy. The rtc and debug.print the time, wouldn't deloy either. I tried deploying an old version and the current version off my old laptop. I removed all of visual studio and reinstalled, that didn't work either. Reinstalled 4.1 SDK Reflashed tiny booter and the 4.1.1 firmware on my netduino and again no joy. I would really appreciate some help, I have a feeling it relates to some reference, but I have tried recreating the project from scratch and copying the code in to new class modules, but again the same issue came up. I hope someone can help, this hardware and code worked perfectly before. Cheers Andy

#16 mcinnes01

mcinnes01

    Advanced Member

  • Members
  • PipPipPip
  • 325 posts
  • LocationManchester UK

Posted 12 September 2011 - 09:58 PM

The plot thickens... I just managed to bit bang some shift registers and that worked a treat, I then plugged everything else back in and ran the shift register code and the LEDs stop flashing in the correct sequence. I then removed the one-wire device and it worked fine. I then ran the full code for all components and I got the same error??

#17 Scott Green

Scott Green

    Advanced Member

  • Members
  • PipPipPip
  • 34 posts

Posted 14 September 2011 - 01:02 AM

Bump...

#18 mcinnes01

mcinnes01

    Advanced Member

  • Members
  • PipPipPip
  • 325 posts
  • LocationManchester UK

Posted 14 September 2011 - 05:23 PM

Got my LCD and RTC back now, but still no 1-wire! //which is a problem for an aquarium project! I think it is a reference issue but I have no idea what with. EDIT: One wire is now working, I think this could be from a reference issue I will post back when I've tried it all together again

#19 Silent12

Silent12

    New Member

  • Members
  • Pip
  • 5 posts

Posted 15 September 2011 - 04:12 AM

Got the same problem here with the 4.2RC1, a power cycle of the interface is required before every deploy.

#20 Scott Green

Scott Green

    Advanced Member

  • Members
  • PipPipPip
  • 34 posts

Posted 17 September 2011 - 05:25 AM

Got the same problem here with the 4.2RC1, a power cycle of the interface is required before every deploy.



So this is the latest update on this problem from the Codeplex site...

Comments
lorenzte wrote Today at 5:33 PM
Several suggestions are in the hands of SecretLabs to produce a new firmware image.


sagreen83 wrote Today at 5:02 PM
Has any progress been made fixing this bug?


Has the new firmware image been created? If so, does it fix the problem?

Scott...




0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users

home    hardware    projects    downloads    community    where to buy    contact Copyright © 2016 Wilderness Labs Inc.  |  Legal   |   CC BY-SA
This webpage is licensed under a Creative Commons Attribution-ShareAlike License.