7 replies to this topic

[alhardy]

Hi, I'm very new to Netduino and only recently purchased a netduino go starter kit. Everything was going smoothly until I was playing around with a couple of motors connected to the go shieldbase. I know can't seem to deploy any simple application. At first when I was deploying I was getting a null instance after creating a new shieldbase and the netduino seemed to always have socket 4 lite up in blue instead of 5 which I had the sheildbase plugged into. Now when I unplug and plug back into the usb all blue socket lights light up briefly than go out. I've tried re-flashing to 4.2 and erasing the deployment using MFDeply and re-deploying with no luck. Here's the output from VS when trying to debug which hits no break points Create TS. Loading start at 8056cd0, end 806dbf8 Assembly: mscorlib (4.2.0.0) Assembly: Microsoft.SPOT.Native (4.2.0.0) Assembly: Microsoft.SPOT.Hardware (4.2.0.0) Assembly: Microsoft.SPOT.Hardware.SerialPort (4.2.0.0) Assembly: Microsoft.SPOT.IO (4.2.0.0) Assembly: System.IO (4.2.0.0) Assembly: Microsoft.SPOT.Hardware.PWM (4.2.0.1) Assembly: Microsoft.SPOT.Hardware.Usb (4.2.0.0) Assembly: SecretLabs.NETMF.Diagnostics (4.2.0.0) Assembly: SecretLabs.NETMF.IO (4.2.0.0) Loading Deployment Assemblies. Resolving. The debugging target runtime is loading the application assemblies and starting execution. Ready. Cannot find any entrypoint! Done. Waiting for debug commands... 'Microsoft.SPOT.Debugger.CorDebug.dll' (Managed): Loaded 'C:\Program Files (x86)\Microsoft .NET Micro Framework\v4.2\Assemblies\le\mscorlib.dll', Symbols loaded. 'Microsoft.SPOT.Debugger.CorDebug.dll' (Managed): Loaded 'C:\Program Files (x86)\Microsoft .NET Micro Framework\v4.2\Assemblies\le\Microsoft.SPOT.Native.dll', Symbols loaded. 'Microsoft.SPOT.Debugger.CorDebug.dll' (Managed): Loaded 'C:\Program Files (x86)\Microsoft .NET Micro Framework\v4.2\Assemblies\le\Microsoft.SPOT.Hardware.dll', Symbols loaded. 'Microsoft.SPOT.Debugger.CorDebug.dll' (Managed): Loaded 'C:\Program Files (x86)\Microsoft .NET Micro Framework\v4.2\Assemblies\le\Microsoft.SPOT.Hardware.SerialPort.dll', Symbols loaded. 'Microsoft.SPOT.Debugger.CorDebug.dll' (Managed): Loaded 'C:\Program Files (x86)\Microsoft .NET Micro Framework\v4.2\Assemblies\le\Microsoft.SPOT.IO.dll', Symbols loaded. 'Microsoft.SPOT.Debugger.CorDebug.dll' (Managed): Loaded 'C:\Program Files (x86)\Microsoft .NET Micro Framework\v4.2\Assemblies\le\System.IO.dll', Symbols loaded. 'Microsoft.SPOT.Debugger.CorDebug.dll' (Managed): Loaded 'C:\Program Files (x86)\Microsoft .NET Micro Framework\v4.2\Assemblies\le\Microsoft.SPOT.Hardware.PWM.dll', Symbols loaded. 'Microsoft.SPOT.Debugger.CorDebug.dll' (Managed): Loaded 'C:\Program Files (x86)\Microsoft .NET Micro Framework\v4.2\Assemblies\le\Microsoft.SPOT.Hardware.Usb.dll', Symbols loaded. 'Microsoft.SPOT.Debugger.CorDebug.dll' (Managed): Loaded 'C:\Program Files (x86)\Secret Labs\Netduino SDK\Assemblies\v4.2\le\SecretLabs.NETMF.Diagnostics.dll', Symbols loaded. 'Microsoft.SPOT.Debugger.CorDebug.dll' (Managed): Loaded 'C:\Program Files (x86)\Secret Labs\Netduino SDK\Assemblies\v4.2\le\SecretLabs.NETMF.IO.dll', Symbols loaded. The program '[7] Micro Framework application: Managed' has exited with code 0 (0x0). If I right click the project and choose deploy i get this output from VS, however my application isn't deployed? Incrementally deploying assemblies to device Deploying assemblies for a total size of 12640 bytes Assemblies successfully deployed to device. Could I have somehow screwed up my netduino by incorrectly connecting wires on my breadboard? Any help is appreciated thanks.

[Chris Walker]

Hi alhardy,

It looks like there's either flash corruption or the app failed to deploy (but looks like it did anyway). Very strange. If you can consistently reproduce this, we'd love to dig in and take a look at what's going on.

In the meantime, let's get you up and running. The first thing to do is to completely erase your board. Reflashing it may only write over existing regions, leaving corrupted data in application regions intact.

Instructions to completely erase a Netduino Go mainboard:

• Install ST's DFUSE app if you haven't already done so
• Unplug your Netduino Go from the PC
• Hold down the pushbutton on your Netduino Go and plug its USB connection into your PC
• Run the "STDFU Tester" app
• Click the "Protocol" tab up top
• Select the "Erase" option in the "Operation" box on left
• Press the "Create from Map" button
• Press Go

Once the board is erased, you can reflash it via the DFUSE Demonstrator app.

Does this get you back up and running?

Chris

[alhardy]

Hi alhardy,

It looks like there's either flash corruption or the app failed to deploy (but looks like it did anyway). Very strange. If you can consistently reproduce this, we'd love to dig in and take a look at what's going on.

In the meantime, let's get you up and running. The first thing to do is to completely erase your board. Reflashing it may only write over existing regions, leaving corrupted data in application regions intact.

Instructions to completely erase a Netduino Go mainboard:

• Install ST's DFUSE app if you haven't already done so
• Unplug your Netduino Go from the PC
• Hold down the pushbutton on your Netduino Go and plug its USB connection into your PC
• Run the "STDFU Tester" app
• Click the "Protocol" tab up top
• Select the "Erase" option in the "Operation" box on left
• Press the "Create from Map" button
• Press Go

Once the board is erased, you can reflash it via the DFUSE Demonstrator app.

Does this get you back up and running?

Chris

Hi Chris,

Thanks for the prompt reply, yes that got me back up and running! Cheers.

I'll let you know if it happens again and give you more details steps to reproduce.

Thanks again.

Allan

[Christopher Clark]

Instructions to completely erase a Netduino Go mainboard:

• Install ST's DFUSE app if you haven't already done so
• Unplug your Netduino Go from the PC
• Hold down the pushbutton on your Netduino Go and plug its USB connection into your PC
• Run the "STDFU Tester" app
• Click the "Protocol" tab up top
• Select the "Erase" option in the "Operation" box on left
• Press the "Create from Map" button
• Press Go

Hi, I am completely new to NetDuino Go. After experiencing the issue several others have, where Visual Studio deploy crashes NetDuino Go, by installing code that makes it unresponsive. I was struggling last night, I searched the forums, Found ST DFUSE, did the erase several times, and installed the firmware 4.2.0.0 several times to no success. What I was not doing correctly, was the step "Press the Create from Map button", even though I was using Erase, and to the novice like me, it appeared to work, since it went through the progress bar and said it was successful. It evidently didn't work. Pressing that Create from Map, made it work. Now I can see my NetDuino Go in MFDeploy and ping it. Where as before it would show up but not ping, I would get communication errors to the device.

It's all a learning experience for me, and even if I bricked it, I would keep going. My background is software for 15 years, so this new hardware stuff is very interesting. Lots to learn.

-Chris

[AlfredBr]

Chris,

I can reproduce this deployment issue consistently. I'm on a Windows8 PC with VS2010 and all the VS updates. My Netduino Go has both the latest firmware and .NETMF. There is nothing connected to it. I can deploy a program to the Netduino Go and it will run fine (my program blinks the LED's on the Netduino Go board).

My program does not have an infinite loop in it, but both VS2010 and the Netduino Go act as if it does. I can stop the debug session in the VS2010 IDE, but that does not stop the Netduino Go. If I try to redeploy this program or another program, I get the 'Cannot find entrypoint" problem. If I powercycle the Netduino Go, only then can I deploy my program to the Netduino Go and continue.

I have found that if I stick a 'return;' at the bottom of Main(), sometimes this allows the program to exit so I can redeploy, but this 'fix' does not work 100% of the time. I've also added an interrupt handler for the on board button that will attempt to reboot the Netduino Go, but this 'fix' does not work 100% of the time either.

The program that I am deploying is not very complex. Here it is....

 public class Program
    {
        private static readonly InterruptPort ResetButton = new InterruptPort(Pins.Button,
                                                                              false,
                                                                              Port.ResistorMode.Disabled,
                                                                              Port.InterruptMode.InterruptEdgeBoth);

        public static void Main()
        {
            ResetButton.OnInterrupt += delegate
                                           {
                                               Debug.Print("RESET pressed");
                                               PowerState.RebootDevice(true);
                                           };
            ResetButton.EnableInterrupt();

            var socketLeds = new OutputPort[8];

            socketLeds[0] = new OutputPort((Cpu.Pin) 0x16, false);
            socketLeds[1] = new OutputPort((Cpu.Pin) 0x17, false);
            socketLeds[2] = new OutputPort((Cpu.Pin) 0x18, false);
            socketLeds[3] = new OutputPort((Cpu.Pin) 0x19, false);
            socketLeds[4] = new OutputPort((Cpu.Pin) 0x26, false);
            socketLeds[5] = new OutputPort((Cpu.Pin) 0x27, false);
            socketLeds[6] = new OutputPort((Cpu.Pin) 0x28, false);
            socketLeds[7] = new OutputPort((Cpu.Pin) 0x29, false);

            const int sleepTime = 100;
            
            for (int j = 0; j < 5; j++)
            {
                for (int i = 1; i <= 8; i++)
                {
                    OutputPort led = socketLeds[i - 1];

                    led.Write(true);

                    Thread.Sleep(sleepTime);
                }

                for (int i = 1; i <= 8; i++)
                {
                    OutputPort led = socketLeds[i - 1];

                    led.Write(false);

                    Thread.Sleep(sleepTime);
                }
            }

            return;
        }
    }

[Chris Walker]

Hi Alfred, Thank you for the repro. We're hoping to post a firmware update for this by next weekend. Chris

[AlfredBr]

12:09am. Man Chris, you are awesome...

[Chris Walker]

Alfred, Quick update: power has been out for the last week due to Sandy. We finished the update before the power went out, but it'll take a few days to test it. We should have the firmware update for Netduino Go posted by Thursday morning. Chris