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)


  • Please log in to reply
34 replies to this topic

#1 Chris Walker

Chris Walker

    Secret Labs Staff

  • Moderators
  • 7767 posts
  • LocationNew York, NY

Posted 24 September 2012 - 10:02 PM

Version: 4.2.0 Update 1 (version 4.2.0.1)

This firmware requires use of the .NET Micro Framework v4.2 SDK (QFE2) and Netduino 4.2.0.1 SDK.

With this firmware, you will have the following resources available for your code:
384KB Flash
100KB+ RAM

This firmware includes the following update:
1. Added preliminary support for GoBus 1.5 beta
2. New InterruptPort support (GoBus virtual i/o)
3. GoBus 1.5 now supports virtual i/o from any thread (including events)

To find the current version of your Netduino Go firmware:
1. Go to the Start Menu > Programs > Microsoft .NET Micro Framework 4.2 > Tools
2. Run MFDeploy.exe. Be careful to run MFDeploy.exe and not MFDeploy.exe.config (as file extensions are hidden by default)
3. Plug your Netduino Go into your PC using a Micro USB cable.
4. In the Device section at top, select USB instead of Serial. Your Netduino Go should appear in the drop-down; if not, select it.
5. Select the Target menu, Device Capabilities option.
6. In the output box, find the "SolutionReleaseInfo.solutionVersion" value. This is your firmware version.

To flash this firmware:
1. Detach your Netduino Go
2. Press and hold your Netduino Go's pushbutton while plugging it in via USB; this will put it in bootloader mode.
3. Flash the attached .DFU file using the ST DfuSe Demonstrator application
a. Locate the "Upgrade or Verify Action" pane (bottom-right pane)
b. Press "Choose..." and select the attached DFU file
c. Check the "Verify after download" option
d. Press "Upgrade". It will take a few minutes to update your Netduino Go.
e. Detach and reattach your Netduino Go (power cycle) or press "Leave DFU mode"

If the verification step of flashing fails, erase the chip before re-flashing.

Enjoy, and please let us know if you run into any troubles.

Chris

Attached Files



#2 neslekkim

neslekkim

    Advanced Member

  • Members
  • PipPipPip
  • 350 posts
  • LocationOslo, Norway

Posted 24 September 2012 - 10:12 PM

this is only for the main go board right?, not for the shieldbase yet? The shielbase are still going to take 4 sockets?

--
Asbjrn


#3 Chris Walker

Chris Walker

    Secret Labs Staff

  • Moderators
  • 7767 posts
  • LocationNew York, NY

Posted 24 September 2012 - 10:18 PM

Hi neslekkim,

this is only for the main go board right?, not for the shieldbase yet?
The shielbase are still going to take 4 sockets?

This update enables the new ShieldBase firmware, using GoBus 1.5.

We've moved the Shield Base from the custom UART transport it was using (which we borrowed from our automated test jigs) to the asynchronous GoBus 1.5 transport (using UART).

The GoBus 1.5 transport is the pre-requisite we have been waiting on to add InterruptPort, SerialPort, SPI, and I2C support to Shield Base. We have already added InterruptPort support in the latest Shield Base firmware and will be adding these other virtual i/o features shortly.

Once we know the UART transport is working well, we'll be updating the Shield Base to the SPI transport. This will enable Shield Base to run at a faster speed and occupy only one GoPort.

So for the moment... Shield Base beta still requires exclusive use of 4 GoPorts. But that requirement will be going away this season.

Chris

#4 neslekkim

neslekkim

    Advanced Member

  • Members
  • PipPipPip
  • 350 posts
  • LocationOslo, Norway

Posted 24 September 2012 - 10:21 PM

Great!

--
Asbjrn


#5 neslekkim

neslekkim

    Advanced Member

  • Members
  • PipPipPip
  • 350 posts
  • LocationOslo, Norway

Posted 25 September 2012 - 11:36 AM

btw, how did it go with WinUSB, is that included in the QFE2? or do we have to wait for 4.3? (I think it have been discussed before, but couldn't find it again)

--
Asbjrn


#6 Chris Walker

Chris Walker

    Secret Labs Staff

  • Moderators
  • 7767 posts
  • LocationNew York, NY

Posted 25 September 2012 - 05:53 PM

Hi neslekkim,

btw, how did it go with WinUSB, is that included in the QFE2? or do we have to wait for 4.3? (I think it have been discussed before, but couldn't find it again)

Netduino and Netduino Plus are using WinUSB with QFE2.

Netduino Go is still using MFUSB (SpotUSB) at the moment. The USB hardware configuration is a bit different which helps MFUSB but also requires some additional testing for WinUSB. We plan to enable WinUSB support for Netduino Go with a future update.

Chris

#7 neslekkim

neslekkim

    Advanced Member

  • Members
  • PipPipPip
  • 350 posts
  • LocationOslo, Norway

Posted 25 September 2012 - 07:01 PM

ok, so still some time until we get rid of the bluescreen problems some have?

--
Asbjrn


#8 Chris Walker

Chris Walker

    Secret Labs Staff

  • Moderators
  • 7767 posts
  • LocationNew York, NY

Posted 25 September 2012 - 07:09 PM

Hi neslekkim,

ok, so still some time until we get rid of the bluescreen problems some have?

The issue should be assuaged somewhat by the newer drivers and the enhanced circuitry on Netduino Go, but it's still possible with the legacy MFUSB drivers. We've been having good stability with MFUSB and Netduino Go here.

We'll update the Netduino Go to WinUSB once all testing is complete (and you'll still have the option of manually switching to MFUSB if you want...just like on Netduino Plus).

Chris

#9 Lunddahl

Lunddahl

    Advanced Member

  • Members
  • PipPipPip
  • 152 posts
  • LocationEurope, Denmark

Posted 25 September 2012 - 08:56 PM

6. In the output box, find the "SolutionReleaseInfo.solutionVersion" value. This is your firmware version.


Verify failed the first time, but after using the STDFU Tester application there was no errors, but no matter what i do i can't get it to 4.2.0.1...:-(

SolutionReleaseInfo.solutionVersion:    4.2.0.0
SolutionReleaseInfo.solutionVendorInfo: Netduino Go (v4.2.0.1) by Secret Labs LLC

- Ulrik Lunddahl

#10 Chris Walker

Chris Walker

    Secret Labs Staff

  • Moderators
  • 7767 posts
  • LocationNew York, NY

Posted 25 September 2012 - 09:07 PM

Hi Ulrik,

Verify failed the first time, but after using the STDFU Tester application there was no errors, but no matter what i do i can't get it to 4.2.0.1...:-(

SolutionReleaseInfo.solutionVersion:    4.2.0.0
SolutionReleaseInfo.solutionVendorInfo: Netduino Go (v4.2.0.1) by Secret Labs LLC

Take a look at "solutionVendorInfo" in your quote. You are good to go :)

We didn't update the solutionVersion (partly because it's using MFUSB drivers). Sorry for any confusion.

#11 carb

carb

    Advanced Member

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

Posted 29 September 2012 - 10:57 PM

Chris,

Last night I watched Steve helping a member update his Netduino Go. Most of the problems were associated either with getting the wrong file or missed steps.

I discussed with Steve the need for a procedure to follow (Yes, I work in nuclear power plants and we don't do anything without a procedure).

Today I updated both of my Netduino Go's and ShiedBases and wrote a procedure / checklist that I hope will be a help to others. If you see anything else that should be added please let me know.

I will add the Checklist to Wiki. Checklist PDF Wiki Page

Don't Drink any 32 oz. soft drinks :lol: ,

Chuck

#12 Arron Chapman

Arron Chapman

    Advanced Member

  • Members
  • PipPipPip
  • 289 posts
  • LocationOregon, USA

Posted 30 September 2012 - 12:27 AM

Chris,

Last night I watched Steve helping a member update his Netduino Go. Most of the problems were associated either with getting the wrong file or missed steps.

I discussed with Steve the need for a procedure to follow (Yes, I work in nuclear power plants and we don't do anything without a procedure).

Today I updated both of my Netduino Go's and ShiedBases and wrote a procedure / checklist that I hope will be a help to others. If you see anything else that should be added please let me know.

I will add the Checklist to Wiki. Checklist PDF Wiki Page

Don't Drink any 32 oz. soft drinks :lol: ,

Chuck


Chuck it looks good, but can I persuade you to making it directly on the wiki, so that it is more easily searchable?

When you talk EE use small words, I'm just a Software Developer :)
My Blog/Site and Everything Else

If my post helped you please consider pressing the "Like This" button in the bottom right-hand corner.

 

Oh my. So many things, so little money!!

 


#13 Gutworks

Gutworks

    Advanced Member

  • Members
  • PipPipPip
  • 363 posts
  • LocationOttawa, Ontario

Posted 01 October 2012 - 02:16 AM


I will add the Checklist to Wiki. Checklist PDF Wiki Page

Chuck, brilliant job. I find this extremely helpful. In fact we're using it in chat as we speak!

Thanks!!
Steve

#14 indimini

indimini

    Member

  • Members
  • PipPip
  • 15 posts

Posted 07 October 2012 - 01:01 PM

Hi guys, I've just bought into the Netduino Go platform, and I am having a potential noob moment. I followed the checklist/procedures for flashing the 4.2.0.1 firmware and shieldbase updates. Everything worked without a hitch - except after completing all of the steps, MFDeploy is still showing SolutionReleaseInfo.solutionVendorInfo: Netduino Go (V4.2.0.0 by Secret Labs LLC). The dfu file is named NeduinoGoFirmware_4.2.0.1.dfu with a creation date of 9/24/12. Any help would be appreciated.

#15 indimini

indimini

    Member

  • Members
  • PipPip
  • 15 posts

Posted 07 October 2012 - 01:19 PM

As a follow-up to my previous post, I now have a strange occurrence when trying to build/debug some simple test software. I started a new project and simply set up the code to set the RgbLed color and update the brightness via the POT. I compiled/debugged and all worked fine. Then, I made a simple code change - adding the button module and handlers for the press and release events. Compile was fine, but when I tried to debug, I got the following output messages. The GoBus dll included in the project reference is 1.0.0.0 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. Attaching deployed file. Assembly: NetduinoGo.Button (1.0.1.0) Attaching deployed file. Assembly: NetduinoGo.Potentiometer (1.0.1.0) Resolving. Link failure: some assembly references cannot be resolved!! Assembly: NetduinoGo.Button (1.0.1.0) needs assembly 'GoBus' (1.0.0.0) Assembly: NetduinoGo.Potentiometer (1.0.1.0) needs assembly 'GoBus' (1.0.0.0) Error: a3000000 Waiting for debug commands... The program '[6] Micro Framework application: Managed' has exited with code 0 (0x0).

#16 Chris Walker

Chris Walker

    Secret Labs Staff

  • Moderators
  • 7767 posts
  • LocationNew York, NY

Posted 07 October 2012 - 04:35 PM

Hi indimini,

Really quickly...can you please try erasing your Netduino Go before re-flashing it?
http://forums.netdui...flashing-fails/

The text version of the firmware will appear as 4.2.0.0 still, although the solutionVersion will be 4.2.0.1.

Attaching deployed file.

Assembly: NetduinoGo.Button (1.0.1.0)
Attaching deployed file.
Assembly: NetduinoGo.Potentiometer (1.0.1.0)
Resolving.
Link failure: some assembly references cannot be resolved!!
Assembly: NetduinoGo.Button (1.0.1.0) needs assembly 'GoBus' (1.0.0.0)
Assembly: NetduinoGo.Potentiometer (1.0.1.0) needs assembly 'GoBus' (1.0.0.0)
Error: a3000000

If erasing and re-flashing your board doesn't solve this particular issue as well, then it may be best to have you upload a zipped copy of your solution. Or remove and re-add the GoBus.dll assembly. Visual Studio seems to be missing something.

Chris

#17 indimini

indimini

    Member

  • Members
  • PipPip
  • 15 posts

Posted 07 October 2012 - 11:05 PM

Hi Chris, First, thanks for the quick response. I did erase prior to reflashing just to make sure that wasn't the issue. What is strange is when I start Visual Studio, the first time I build/debug the project it works fine. If I make a minor code change, rebuild and debug, I get the error posted. If I physically unplug the Go from the USB power and re-connect, the code runs. It seems like whatever soft reboot is taking place is causing the problem. 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. public class Program { static NetduinoGo.Button myButton; static NetduinoGo.Potentiometer myPOT; static NetduinoGo.RgbLed myLED; public static void Main() { myButton = new NetduinoGo.Button(GoSockets.Socket1); myButton.ButtonPressed += new NetduinoGo.Button.ButtonEventHandler(myButton_ButtonPressed); myButton.ButtonReleased += new NetduinoGo.Button.ButtonEventHandler(myButton_ButtonReleased); myPOT = new NetduinoGo.Potentiometer(GoSockets.Socket2); myLED = new NetduinoGo.RgbLed(GoSockets.Socket3); myLED.SetColor(255, 255, 255); while (true) { myLED.SetBrightness(myPOT.GetValue()); Thread.Sleep(100); } } static void myButton_ButtonReleased(object sender, bool isPressed) { Debug.Print("Button pressed."); } static void myButton_ButtonPressed(object sender, bool isPressed) { Debug.Print("Button released."); } }

#18 carb

carb

    Advanced Member

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

Posted 08 October 2012 - 12:22 AM

Hi indimini,

Really quickly...can you please try erasing your Netduino Go before re-flashing it?
http://forums.netdui...flashing-fails/

The text version of the firmware will appear as 4.2.0.0 still, although the solutionVersion will be 4.2.0.1.


If erasing and re-flashing your board doesn't solve this particular issue as well, then it may be best to have you upload a zipped copy of your solution. Or remove and re-add the GoBus.dll assembly. Visual Studio seems to be missing something.

Chris

Chris,


I am getting the same error with a Go and just the DAQ module plugged in. It works the first try then Error:A3000000 message. The Only way I can get the program to deploy a second time is to unplug the Go board, press the deploy, wait about 5 seconds, then plug the Go back in and the programs runs.



I also got it to work by opening MFDeploy, erase, then deply from Visual Studio.



Chuck

#19 OleNorway

OleNorway

    New Member

  • Members
  • Pip
  • 4 posts

Posted 08 October 2012 - 07:50 AM


I did erase prior to reflashing just to make sure that wasn't the issue. What is strange is when I start Visual Studio, the first time I build/debug the project it works fine. If I make a minor code change, rebuild and debug, I get the error posted. If I physically unplug the Go from the USB power and re-connect, the code runs. It seems like whatever soft reboot is taking place is causing the problem.


+1

I have the same experience, the first compile/deploy after a coldboot of the Board is ok. The second++ always fails.

/O

#20 Chris Walker

Chris Walker

    Secret Labs Staff

  • Moderators
  • 7767 posts
  • LocationNew York, NY

Posted 08 October 2012 - 03:24 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




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.