Netduino Go Firmware v4.2.0 (Update 1) - Page 2 - Netduino Go - Netduino Forums
   
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

Netduino Go Firmware v4.2.0 (Update 1)

Started by Chris Walker, Sep 24 2012 10:02 PM

  • Please log in to reply
34 replies to this topic

#21 Nicky

Nicky

    Advanced Member

  • Members
  • PipPipPip
  • 78 posts
  • LocationDenmark

Posted 08 October 2012 - 04:08 PM

I also have to replug my NGo 90% of attempts to deploy code to it after upgrading.

Further more, and this seems totally random, sometimes the NGo "looses" it's entry point, and then I have to erase the chip and reflash before I can run my code. I can't deploy another project neither.

Output from Build:
------ Skipped Deploy: Project: ComLink, Configuration: Debug Any CPU ------
Project not selected to build for this solution configuration 
------ Skipped Deploy: Project: OS, Configuration: Debug Any CPU ------
Project not selected to build for this solution configuration 
------ Deploy started: Project: NetduinoGoApplication2, Configuration: Debug Any CPU ------
------ Deploy started: Project: NetduinoGoApplication2, Configuration: Debug Any CPU ------
------ Skipped Deploy: Project: LV-MaxSonar-EZ, Configuration: Debug Any CPU ------
Project not selected to build for this solution configuration 
------ Skipped Deploy: Project: AM2302, Configuration: Debug Any CPU ------
Project not selected to build for this solution configuration 
========== Deploy: 1 succeeded, 0 failed, 4 skipped ==========

Output from Micro Framework Device Deployment
Incrementally deploying assemblies to device
Deploying assemblies for a total size of 219324 bytes
Assemblies successfully deployed to device.

Output from Debug
Create TS.

 Loading start at 8056ce0, end 806dd8c

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 '[3] Micro Framework application: Managed' has exited with code 0 (0x0).

ntools
TCP Listener (Beta) · FTP Server (Alpha)
Netduino Plus Go Module · Xml Parser
http://ntools.codeplex.com/

#22 indimini

indimini

    Member

  • Members
  • PipPip
  • 15 posts

Posted 08 October 2012 - 04:58 PM

Just to confirm, this only happens right after the second+ Visual Studio deployment?

And if you unplug and replug your Netduino Go, it works properly?

Or do you have to erase/reflash the core firmware to get it back to a happy state?

Chris

Chris,

In my case, I've been able to rebuild/debug by disconnecting and then reconnecting the Go to the USB power source

#23 Chris Walker

Chris Walker

    Secret Labs Staff

  • Moderators
  • 7767 posts
  • LocationNew York, NY

Posted 08 October 2012 - 05:07 PM

Hi Nicky, The redeployment issue seems to be related to applications bigger than 128KB (one sector). We're looking into it and should have a permanent fix for that later this month. In the meantime, your current workaround should continue to work. Chris

#24 AlfredBr

AlfredBr

    Advanced Member

  • Members
  • PipPipPip
  • 138 posts
  • LocationConnecticut, USA

Posted 08 October 2012 - 06:33 PM

This happens to me too. Started happening after the upgrade. (But I'm not sure its exclusive to > 128K. Will check.)

#25 Chris Walker

Chris Walker

    Secret Labs Staff

  • Moderators
  • 7767 posts
  • LocationNew York, NY

Posted 08 October 2012 - 06:40 PM

But I'm not sure its exclusive to > 128K. Will check.

It seems to happen to some users _after_ deploying a >128KB app. Such as the Shield Base updater.

Most users' apps are well under 128KB so it doesn't happen to many users...but those upgrading their Shield Bases will probably see it at some point.

We're digging into it. Will have an update for it this month for sure.

Chris

#26 Gutworks

Gutworks

    Advanced Member

  • Members
  • PipPipPip
  • 363 posts
  • LocationOttawa, Ontario

Posted 08 October 2012 - 06:42 PM


Here's the code - it's stupid simple - just playing with the three basic modules. As I mentioned, if I do the build/debug it works. Then I went in and simply commented out the 3 lines for myButton and got the incremental linker error I posted earlier.


Hi indimini,

I tried to reproduce your error using the above code but did not get an error. After a couple deploys I commented out the 3 lines for the myButton, and still had zero issues. I wonder if this is similar to the seemingly random USB issue we used to have with the Netduino. I do believe at some point in the near future we will also see a move to the WinUSB drivers for the Netduino Go as well. Perhaps that will helps solve some of these issues where you need to unplug and plug your device back in.

Steve

Twiiter: https://twitter.com/Gutworks

#27 Nicky

Nicky

    Advanced Member

  • Members
  • PipPipPip
  • 78 posts
  • LocationDenmark

Posted 08 October 2012 - 07:08 PM

Hi indimini,

I tried to reproduce your error using the above code but did not get an error. After a couple deploys I commented out the 3 lines for the myButton, and still had zero issues. I wonder if this is similar to the seemingly random USB issue we used to have with the Netduino. I do believe at some point in the near future we will also see a move to the WinUSB drivers for the Netduino Go as well. Perhaps that will helps solve some of these issues where you need to unplug and plug your device back in.

Steve


I also have this one.. almost all the time. I'm running a N+ at the same time... could this have something to do with it?

ntools
TCP Listener (Beta) · FTP Server (Alpha)
Netduino Plus Go Module · Xml Parser
http://ntools.codeplex.com/

#28 Chris Walker

Chris Walker

    Secret Labs Staff

  • Moderators
  • 7767 posts
  • LocationNew York, NY

Posted 08 October 2012 - 07:12 PM

Hi Nicky, We'll be moving Netduino Go to WinUSB with the .NET MF 4.3 upgrade. There are a number of MFUSB-driver-related issues which can cause this; the enhanced USB circuitry on Netduino Go combined with WinUSB should make Visual Studio much happier. Chris

#29 neslekkim

neslekkim

    Advanced Member

  • Members
  • PipPipPip
  • 350 posts
  • LocationOslo, Norway

Posted 08 October 2012 - 07:21 PM

but the 4.3 is well past newyear right?

--
Asbjørn

#30 Chris Walker

Chris Walker

    Secret Labs Staff

  • Moderators
  • 7767 posts
  • LocationNew York, NY

Posted 08 October 2012 - 07:23 PM

but the 4.3 is well past newyear right?

Unless there is some showstopper, .NET MF 4.3 should ship this year.

Chris

#31 carb

carb

    Advanced Member

  • Members
  • PipPipPip
  • 352 posts
  • LocationCrystal River, Florida

Posted 08 October 2012 - 07:42 PM

It seems to happen to some users _after_ deploying a >128KB app. Such as the Shield Base updater.

Most users' apps are well under 128KB so it doesn't happen to many users...but those upgrading their Shield Bases will probably see it at some point.

We're digging into it. Will have an update for it this month for sure.

Chris

Chris,


The app that I am deploying is the time.cs for the DAQ moduke samples. It assembly size shows 32484 bytes.


using System;
using System.Threading;
using Microsoft.SPOT;
using Microsoft.SPOT.Hardware;
using SecretLabs.NETMF.Hardware.NetduinoGo;
using Nwazet.Go.DAQ;
namespace Tutorials {
    public class Time {
        public static NwazetDAQ daq = new NwazetDAQ();
        public static void Main() {
            daq.Initialize(GoSockets.Socket1);
            var state = daq.GetClockState();
            if (state == NwazetDAQ.ClockState.Invalid) 
						{
                daq.SetDateTime(new DateTime(2012, 09, 12, 17, 57, 00));
            }
						Debug.Print("Time: " + DateTime.Now.ToString());
						while (true)
						{
							var dt = daq.GetDateTime();
							Thread.Sleep(10000);
							Debug.Print("Time: " + dt.ToString() );
						}

        }
    }
}

It seems to be with anything that I have tried so far.

Thanks,
Chuck

#32 indimini

indimini

    Member

  • Members
  • PipPip
  • 15 posts

Posted 08 October 2012 - 09:12 PM

Steve, Chris,

Again, thanks for the quick responses. Posted Image


I did run the Shield Base updater. It sounds like that may have been what started these issues. Is there a way to revert those updates or should I just keep cycling power for the near term? My next steps in learning to use Netduino Go will depend on the shield base and the SPOT.Hardware.OneWire code, so I'm not sure if there are more benefits to keeping the update installed vs. rolling back.

Thanks,

Bob

#33 Chris Walker

Chris Walker

    Secret Labs Staff

  • Moderators
  • 7767 posts
  • LocationNew York, NY

Posted 08 October 2012 - 09:16 PM

Hi Bob, I would stick with the latest and greatest...but erase and reflash your mainboard with the latest firmware after updating your Shield Base. We're working on an elegant automatic solution to that issue. Chris

#34 indimini

indimini

    Member

  • Members
  • PipPip
  • 15 posts

Posted 08 October 2012 - 09:49 PM

Hi Bob,

I would stick with the latest and greatest...but erase and reflash your mainboard with the latest firmware after updating your Shield Base.

We're working on an elegant automatic solution to that issue.

Chris


Chris,

I just erased and reflashed the main board again, and I am no longer getting the errors w/in Visual Studio! I had originally updated the Go firmware first and then updated the shield base. It seems that by reflashing the main board, the code-build-debug cycle now works again for me.

Still looking forward to the update, but thought I'd pass along that bit of news re: the order of applying updates as it may work for others too.

Bob

#35 Gutworks

Gutworks

    Advanced Member

  • Members
  • PipPipPip
  • 363 posts
  • LocationOttawa, Ontario

Posted 08 October 2012 - 10:32 PM


It seems that by reflashing the main board, the code-build-debug cycle now works again for me.


Fantastic news Bob!

Twiiter: https://twitter.com/Gutworks

Back to Netduino Go


1 user(s) are reading this topic

0 members, 1 guests, 0 anonymous users

  1. Netduino Forums
  2. → Hardware
  3. → Netduino Go
  4. Privacy Policy
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.