Netduino Plus Firmware v4.2.0

Version: 4.2.0 (version 4.2.0.0)

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:
64KB Flash
42KB+ RAM (50% more RAM than 4.1.0.6)

This firmware includes the following updates:
1. 50% more RAM: 42KB (4.2.0.0) vs. 28KB (4.1.0.6)
2. Visual Basic is now a supported language for .NET MF
3. New core AnalogInput and PWM classes; backwards-compatible classes available via add-on assemblies.
4. New WinUSB drivers (to remedy BSOD issues in 4.2 beta)
5. Garbage collector now fully collects old objects
6. See netmf.codeplex.com for full details of all bugfixes

To find the current version of your Netduino Plus 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 Plus into your PC using a Micro USB cable.
4. In the Device section at top, select USB instead of Serial. Your Netduino Plus 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.

Users of firmware version 4.2.0.0 RC5 or earlier may update to this new firmware:
1. Erase your Netduino Plus by applying 3V3 power to the gold ERASE pad
a. Detach and reattach your Netduino Plus (power cycle)
2. Flash TinyBooterDecompressor.bin using SAM-BA v2.12+
a. Detach and reattach your Netduino Plus (power cycle)
3. Flash TinyCLR using MFDeploy v4.2+
a. Click "Browse..." and select the TinyCLR files (ER_CONFIG and ER_FLASH).
b. Press "Deploy". It will take a few minutes to update your Netduino Plus.
c. Detach and reattach your Netduino Plus (power cycle)

After flashing, to set your network settings using MFDeploy.
a. Start your Netduino Plus in TinyBooter mode by holding the pushbutton while plugging it into your PC using a MicroUSB cable.
b. Select the Target > Configuration > Networking menu. Re-enter your IP address settings and MAC address.
c. Detach and reattach your Netduino Plus (power cycle)

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

Chris

Chris, You did not tell that also Netduino SDK 4.2.0.1 and .NET Micro Framework SDK v4.2Q2 is needed Without windows can not recognize the Netduino. Ellen

Hi Ellen,

Chris, You did not tell that also Netduino SDK 4.2.0.1 and .NET Micro Framework SDK v4.2Q2 is needed
Without windows can not recognize the Netduino.

Good point! The updated SDK includes the necessary WinUSB drivers.

I just added "Netduino SDK 4.2.0.1" to the pre-requisites note in the first post.

Thank you for pointing this out.

Chris

Hi Ellen,

Good point! The updated SDK includes the necessary WinUSB drivers.

I just added "Netduino SDK 4.2.0.1" to the pre-requisites note in the first post.

Thank you for pointing this out.

Chris

I installed the latest version and it is showing up as 4.2.0002

Is that not the correct version?

Greg

Hi GregR,

I installed the latest version and it is showing up as 4.2.0002

Is that not the correct version?

You have the correct version. The version number you're seeing is from the setup file and is due to a feature of InstallShield. We'll see if there's a way to sync these version numbers in the future to avoid any confusion.

Chris

Is there in this version 4.2.0.1 support for the SD HC 8 gieg card? Dim fs As FileStream = File.Create("\jj.txt") error: An unhandled exception of type 'System.IO.IOException' occurred in System.IO.dll If there is not than i can stop with finding out. gr Ellen

Hi Ellen,

Is there in this version 4.2.0.1 support for the SD HC 8 gieg card?

Dim fs As FileStream = File.Create("\jj.txt")

error:
An unhandled exception of type 'System.IO.IOException' occurred in System.IO.dll

If there is not than i can stop with finding out.
gr Ellen

The .NET MF team updated the SD card drivers in .NET MF 4.2. If there are any cards which worked with 4.1.1 but aren't working with the official 4.2 release, we want to make sure we get those supported.

Can you please provide the manufacturer and model number of your card, and we'll try to get one here to test against?

Chris

Is there in this version 4.2.0.1 support for the SD HC 8 gieg card?

Dim fs As FileStream = File.Create("\jj.txt")

error:
An unhandled exception of type 'System.IO.IOException' occurred in System.IO.dll

If there is not than i can stop with finding out.
gr Ellen

Hi Ellen,

The mountpoint is not correct, I think you want:

Dim fs As FileStream = File.Create("\SD\jj.txt")

Hi Ellen,


The .NET MF team updated the SD card drivers in .NET MF 4.2. If there are any cards which worked with 4.1.1 but aren't working with the official 4.2 release, we want to make sure we get those supported.

Can you please provide the manufacturer and model number of your card, and we'll try to get one here to test against?

Chris

It took a while....
Chris, Stefan, I start with the bottom line, There is no way that we could read or write from the mini SDcard. I think there is a lot to re-write and test in the system.dll
What we did: purchased a second N+ and a second 4 gieg mini SDcard. Just to exclude that the first N+ or card was broken.
We did test it in the most unthinkable way and code, mixed...in ...out...power recycle...format....other computer, ....you name it, we did it.
Those who have a working SDcard must see themselves as the lucky ones. If there is someone who can tell ... with these steps and program code it must go well...
Ellen

Hi Ellen, I just checked with Chris and tested it on my own Netduino Plus. SDHC is not yet supported in 4.2. The only firmware it is supported in right now is 4.1.1.1 beta. Community member Kodedaemon worked on the SDHC support in the previous release, but Microsoft has made some major changes to SD support so they must be re-evaluated. I must say I sympathize with you, I wished SDHC support would be in this release too, but until then, you are stuck with <=2GB cards (which are still widely available and cheap btw!)

When i click on MFDeploy on "Device Capabilities", the program say: Not Supported Is there a error or is that normal? in RC5 i became all infos mfg gfc

Hi gfc,

When i click on MFDeploy on "Device Capabilities", the program say: Not Supported

Is there a error or is that normal? in RC5 i became all infos

Press ping...are you in TinyBooter mode or TinyCLR mode?

If you're in TinyBooter mode, then unplug and reattach your Netduino... That will boot into TinyCLR mode and you can list the Device Capabilities then.

Chris

Hi Ellen,

I just checked with Chris and tested it on my own Netduino Plus.
SDHC is not yet supported in 4.2. The only firmware it is supported in right now is 4.1.1.1 beta.

Community member Kodedaemon worked on the SDHC support in the previous release, but Microsoft has made some major changes to SD support so they must be re-evaluated.

I must say I sympathize with you, I wished SDHC support would be in this release too, but until then, you are stuck with <=2GB cards (which are still widely available and cheap btw!)

Thanks Stefan, Chris,
Now we have clearness in this case. Now i can stop thinking about what did I wrong, what didn't I see. I buy a 2gieg and let you know.
Ellen

When i click on MFDeploy on "Device Capabilities", the program say: Not Supported

I'm also getting some flaky behaviour after a 4.2 upgrade on a N+. I've poked around a fair bit but was going to do some more before posting, but your issues sound similar to mine.

I ensured earlier versions of everything (SAM-BA, .NET MF, Netduino SDK) were removed and the latest installed. I completely erased, flashed TinyBooter using SAM-BA 2.12 and then the new firmware via the 4.2 QFE2 version of MFDeploy.

I could get Device Capabilities but teh device would often hang afterwards. I would get "not supported in this version" when trying to set the IP address in MFDeploy. That finally stuck, but it's now being very reluctant to connect in Visual Studio. I've totally erased and reflashed a couple of times. I'll do some more prodding and poking when I get a chance, but I've got lots on at the moment and it may get left for a while.

Hi Fred,

I'm also getting some flaky behaviour after a 4.2 upgrade on a N+. I've poked around a fair bit but was going to do some more before posting, but your issues sound similar to mine.

I ensured earlier versions of everything (SAM-BA, .NET MF, Netduino SDK) were removed and the latest installed. I completely erased, flashed TinyBooter using SAM-BA 2.12 and then the new firmware via the 4.2 QFE2 version of MFDeploy.

I could get Device Capabilities but teh device would often hang afterwards. I would get "not supported in this version" when trying to set the IP address in MFDeploy. That finally stuck, but it's now being very reluctant to connect in Visual Studio. I've totally erased and reflashed a couple of times. I'll do some more prodding and poking when I get a chance, but I've got lots on at the moment and it may get left for a while.

Netduino acts a bit differently with the new WinUSB drivers than with the old MFUSB drivers.

For instance, you need to be in TinyBooter mode (by pressing and holding the pushbutton while plugging in your Netduino) to change the IP settings. Also, to even enumerate as a WinUSB device in MFDeploy or Visual Studio...it can't have an open connection in another instance of either program.

When you have time...if you can give us a bit more info on the experience you're having we can walk through it and hopefully help sort out what's happening.

Chris

For instance, you need to be in TinyBooter mode (by pressing and holding the pushbutton while plugging in your Netduino) to change the IP settings. Also, to even enumerate as a WinUSB device in MFDeploy or Visual Studio...it can't have an open connection in another instance of either program.

I wasn't aware of that. I'll give it a go and see what difference that makes. Does that mean we have to press the button and reset every time we want to program and debug? My plus appears fine as "Netduino" in device manager - I just can't do much with it.

Hi Fred,

I wasn't aware of that. I'll give it a go and see what difference that makes. Does that mean we have to press the button and reset every time we want to program and debug? My plus appears fine as "Netduino" in device manager - I just can't do much with it.

No, you don't need to reset to deploy, program, or debug. The Netduino will take care of that automatically.

As opposed to MFUSB, the WinUSB drivers make a single connection to the NETMF board and then hold onto it. TinyBooter and TinyCLR are two separately applications running on the Netduino, and both of them need to grab onto that WinUSB connection to perform their duties.

When a Netduino running 4.2 firmware boots, it looks to see if the pushbutton is being held down. If so, then TinyBooter grabs the WinUSB connection so you can change settings on or do maintenance to your Netduino. If the button isn't being held down then it starts up TinyCLR and lets it grab the WinUSB connection instead.

When you change settings from MFDeploy, if TinyCLR is running then it tries to reboot the board to switch to the TinyBooter application. The board reboots but TinyBooter can't grab the WinUSB connection (since it was established with TinyCLR).

So to change settings...boot into TinyBooter mode by holding the pushbutton during boot. To deploy and debug applications, just use your Netduino like before... The only behavioral change is switching into TinyBooter for IP settings/flashing/maintenance.

Chris

The only behavioral change is switching into TinyBooter for IP settings/flashing/maintenance.

This seemed to be the key to it! I'm now sorted. Without pressing the onboard button when plugging in before using MFDeploy it seems that you can reflash the firmware but end up with a badly behaving Netduino. Very odd.

Revised: It worked if I moved to another USB port (??!?!). After SAM-BA has detected the USB driver and I've selected at91sam7x512-ek and then click "Connect", SAM-BA pops up "Error in startup script" "Error h_handle returned zero" etc. I'm using Windows 7 64, .NET 4.2 and SDK 4.2. Any idea what could cause this to happen? Cheers, Anders

Hi Anders,

Revised: It worked if I moved to another USB port (??!?!).


After SAM-BA has detected the USB driver and I've selected at91sam7x512-ek and then click "Connect", SAM-BA pops up "Error in startup script" "Error h_handle returned zero" etc.

I'm using Windows 7 64, .NET 4.2 and SDK 4.2.

Any idea what could cause this to happen?

Cheers,
Anders

That's very odd. So it did work alright after moving the Netduino to another USB port?

Also, are you using SAM-BA v2.12+? The earlier versions had some issues with Win7 x64.

Chris