Netduino home hardware projects downloads community

Jump to content


The Netduino forums have been replaced by new forums at community.wildernesslabs.co. This site has been preserved for archival purposes only and the ability to make new accounts or posts has been turned off.
Photo

Long time to debug with 4.2 RC3?


  • Please log in to reply
5 replies to this topic

#1 Cabadam

Cabadam

    Advanced Member

  • Members
  • PipPipPip
  • 90 posts

Posted 10 December 2011 - 12:51 AM

I previously had I believe 4.2 RC1, since just upgrading to 4.2 RC3, when I "start debugging" from Visual Studio (2010), it now takes about a full minute for it to hit a breakpoint on the very first line of Main(). I get the "NotImplementedException" in the Output window fairly quickly, but then it just sits. At first, I thought it wasn't actually executing anything, but then I found if I just let it sit, it would eventually hit my breakpoint and be able to run my program. My program isn't horribly big, 20908 bytes. Is anyone else seeing this? Thanks, Adam

#2 Chris Walker

Chris Walker

    Secret Labs Staff

  • Moderators
  • 7767 posts
  • LocationNew York, NY

Posted 11 December 2011 - 05:37 AM

Hmm I haven't seen this, but I'd love to know why... The reset mechanism changed quite dramatically in 4.2; are you using the 4.2 beta drivers for Netduino by any chance? If you run a simple "blinky" or "hello world" type of app, do you still get the same delay? Chris

#3 Cabadam

Cabadam

    Advanced Member

  • Members
  • PipPipPip
  • 90 posts

Posted 11 December 2011 - 03:20 PM

OK, I created a new application from the ND+ template, simply:
    public class Program
    {
        public static void Main()
        {
            Debug.Print("Hello World");
        }

    }

I actually timed it this time, and it took almost exactly 50 seconds from the time "NotImplementedException" appeared in the Output window to print out the "Hello World" message.

My output window:

A first chance exception of type 'System.NotImplementedException' occurred in Microsoft.SPOT.Native.dll
The thread '<No Name>' (0x2) has exited with code 0 (0x0).
Hello World
The thread '<No Name>' (0x1) has exited with code 0 (0x0).
Done.
Waiting for debug commands...
The program '[2] Micro Framework application: Managed' has exited with code 0 (0x0).


I do not know if it is related, but that thread that ends right before the Hello World - that message prints at basically the same time as Hello World, which might imply it is waiting on whatever that thread is doing to complete before moving on to execute the program.

#4 Cabadam

Cabadam

    Advanced Member

  • Members
  • PipPipPip
  • 90 posts

Posted 11 December 2011 - 03:21 PM

Oh, and I am using the new 4.2 Beta drivers. Unfortunately, I was troubleshooting a couple things earlier, and I'm not sure I remember if the problem occurred before I installed them or not.

#5 Chris Walker

Chris Walker

    Secret Labs Staff

  • Moderators
  • 7767 posts
  • LocationNew York, NY

Posted 11 December 2011 - 04:40 PM

Hi Cabadam, Is there any chance that you can take a quick video (screenshot capture or cameraphone video) of the 60-seconds from right before you press "play" until the "hello world" program actually runs? This appears to be an issue with the 4.2 NETMF SDK on the PC (which is provided by Microsoft), so we'll want to post a bug report on netmf.codeplex.com so they can address it. The video should help them understand the issue. BTW, two other thoughts: 1. If you press the reset button on the Netduino during the 50 seconds you're waiting for the app to start, does that make your app start faster? What about if you unplug and re-attach your Netduino? 2. Are you using a Netduino Plus or a Netduino? If a Netduino Plus, is a network cable attached? If you flash it with the non-Plus firmware, do you still have the delay? Chris

#6 Cabadam

Cabadam

    Advanced Member

  • Members
  • PipPipPip
  • 90 posts

Posted 11 December 2011 - 05:23 PM

Interesting... Yes, I had a network cable connected. I tried unplugging it, no change. But trying that made me think about other peripherals... such as say, the SD card which I am currently having problems with. I removed the SD card and suddenly the delay was gone. So, this may end up being more tied to over in that thread (http://forums.netdui...ng-on-n-42-rc3/). Obviously, no idea if the OP there and myself have problems with the same cause, but it definitely looks like the Netduino is trying to load/mount the SD card, it finally fails/timeouts, and then execution continues. With that said - I think long delay here is not actually a problem, but a symptom of the SD card failing.




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.