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.
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.
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.
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)
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.
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).
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
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.
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.
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.
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.
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).
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.
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.");
}
}
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.
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.
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
NeduinoGoFirmware_4.2.0.1.zip 189.95KB
91 downloads
,
