Netduino home hardware projects downloads community

Jump to content


Photo

Netduino Plus 1 Firmware v4.2.0 (update 1)


  • Please log in to reply
144 replies to this topic

#1 Chris Walker

Chris Walker

    Secret Labs Staff

  • Moderators
  • 7767 posts
  • LocationNew York, NY

Posted 19 September 2012 - 10:03 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:
64KB Flash
42KB+ RAM (50% more RAM than 4.1.0.6)

This firmware includes the following update:
1. PWM bugfix (period/frequency now set correctly)

This firmware also includes the following prior 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+ do not need to update TinyBooter.

Users of firmware version 4.2.0.0 RC5 or earlier may update TinyBooter as follows:
1. Erase your Netduino by applying 3V3 power to the gold ERASE pad
a. Detach and reattach your Netduino (power cycle)
2. 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.
c. Detach and reattach your Netduino (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[url=http://wiki.netduino...ep-by-step.ashx] 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.
c. Detach and reattach your Netduino (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

Attached Files



#2 Gutworks

Gutworks

    Advanced Member

  • Members
  • PipPipPip
  • 363 posts
  • LocationOttawa, Ontario

Posted 20 September 2012 - 02:12 AM

Hi Chris,

After flashing my firmware using MFDeploy, TinyBooter mode still displayed 4.2.0.0 as the Bootloader build info, and not the expect version of 4.2.0.1. Thanks to your tip in chat, I had to boot the Netduino Plus in TinyCLR mode (do not press the reset button while powering on). Then I was then able to display the Device Capabilities (Ctrl+Shift+c) which then showed show the VendorInfo as Netduino Plus (v4.2.0.1) by Secret Labs LLC.

From my understanding if I do not completely erase the Netduino prior to flashing, the TinyBooter will not be updated, which at first glance makes it appear to have not upgraded the Netduino firmware. I just wanted to post the result in case anyone else makes the same slip as me :)

Thanks,
Steve

#3 Igor Kondrasovas

Igor Kondrasovas

    Advanced Member

  • Members
  • PipPipPip
  • 105 posts
  • LocationPorto, Portugal

Posted 20 September 2012 - 06:37 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.


Hi Chris,

Is Netduino 4.2.0.1 SDK available at: http://www.netduino....bit_NETMF42.exe url?

When I try to install, it says is from August! Is that correct?

Another question (this is to understand how the fix process takes place): If the update was in the PWM class, and this class is on NETMF 4.2, why do you have to update Netduino SDK? Wouldn't it be a NETMF SDK update?

Thank you,


Igor

Igor Kondrasovas

www.inovativatec.com


#4 Chris Walker

Chris Walker

    Secret Labs Staff

  • Moderators
  • 7767 posts
  • LocationNew York, NY

Posted 20 September 2012 - 08:02 PM

Hi Igor,

Is Netduino 4.2.0.1 SDK available at: http://www.netduino....bit_NETMF42.exe url?

When I try to install, it says is from August! Is that correct?

Another question (this is to understand how the fix process takes place): If the update was in the PWM class, and this class is on NETMF 4.2, why do you have to update Netduino SDK? Wouldn't it be a NETMF SDK update?

The Netduino SDK has not changed. In this case, only the firmware for the board was updated.

We only update the Netduino SDK when there's a change to the Visual Studio integration or features are changed in the managed code classes. The NETMF SDK only gets updated for big changes (QFEs, new versions, etc.)

Chris

#5 Igor Kondrasovas

Igor Kondrasovas

    Advanced Member

  • Members
  • PipPipPip
  • 105 posts
  • LocationPorto, Portugal

Posted 20 September 2012 - 09:12 PM

Hum... so it seems I have problem after updating firmware to 4.2.0 update 1.

I created a new Netduino Plus project and instantiated a new PWM class. When I start debugging the deployment is succeeded but I got an unhandled exception "System.InvalidOperationException" in Microsoft.SPOT.Hardware.dll

Here are the device capabilities (from MFDeploy tool):

HalSystemInfo.halVersion: 4.2.0.0

HalSystemInfo.halVendorInfo: Netduino Plus (v4.2.0.1) by Secret Labs LLC

HalSystemInfo.oemCode: 34

HalSystemInfo.modelCode: 177

HalSystemInfo.skuCode: 4097

HalSystemInfo.moduleSerialNumber: 00000000000000000000000000000000

HalSystemInfo.systemSerialNumber: 0000000000000000

ClrInfo.clrVersion: 4.2.0.0

ClrInfo.clrVendorInfo: Netduino Plus (v4.2.0.1) by Secret Labs LLC

ClrInfo.targetFrameworkVersion: 4.2.0.0

SolutionReleaseInfo.solutionVersion: 4.2.0.0

SolutionReleaseInfo.solutionVendorInfo: Netduino Plus (v4.2.0.1) by Secret Labs LLC

SoftwareVersion.BuildDate: Sep 19 2012

SoftwareVersion.CompilerVersion: 410894

FloatingPoint: True

SourceLevelDebugging: True

ThreadCreateEx: True

LCD.Width: 0

LCD.Height: 0

LCD.BitsPerPixel: 0

AppDomains: True

ExceptionFilters: True

IncrementalDeployment: True

SoftReboot: True

Profiling: False

ProfilingAllocations: False

ProfilingCalls: False

IsUnknown: False


What do you suggest? I already tried changing USB ports and reseting the PC.

I was using firmware 4.2.0 before and it was OK...

Igor.

Igor Kondrasovas

www.inovativatec.com


#6 Chris Walker

Chris Walker

    Secret Labs Staff

  • Moderators
  • 7767 posts
  • LocationNew York, NY

Posted 20 September 2012 - 09:15 PM

Hi Igor,

Hum... so it seems I have problem after updating firmware to 4.2.0 update 1.

Can you share the code which is throwing the exception?

Chris

#7 Igor Kondrasovas

Igor Kondrasovas

    Advanced Member

  • Members
  • PipPipPip
  • 105 posts
  • LocationPorto, Portugal

Posted 20 September 2012 - 09:23 PM

Hi Chris, here you go:

Hi Igor,


Can you share the code which is throwing the exception?

Chris


public static void Main()

{

Microsoft.SPOT.Hardware.PWM led = new Microsoft.SPOT.Hardware.PWM(PWMChannels.PWM_PIN_D9, 1, 0.5, false);

led.Start();

System.Threading.Thread.Sleep(Timeout.Infinite);

}

The exception is thrown on the led constructor. Please tell me I am doing something silly :-)




Igor Kondrasovas

www.inovativatec.com


#8 Chris Walker

Chris Walker

    Secret Labs Staff

  • Moderators
  • 7767 posts
  • LocationNew York, NY

Posted 20 September 2012 - 09:36 PM

Microsoft.SPOT.Hardware.PWM led = new Microsoft.SPOT.Hardware.PWM(PWMChannels.PWM_PIN_D9, 1, 0.5, false);

At first glance, are you setting the frequency to 1Hz? That may be too slow for the 16-bit PWM. Can you change that to a faster frequency (perhaps 100 Hz?) and see if that works?

Chris

#9 Igor Kondrasovas

Igor Kondrasovas

    Advanced Member

  • Members
  • PipPipPip
  • 105 posts
  • LocationPorto, Portugal

Posted 20 September 2012 - 09:48 PM

At first glance, are you setting the frequency to 1Hz? That may be too slow for the 16-bit PWM. Can you change that to a faster frequency (perhaps 100 Hz?) and see if that works?

Chris


You see, I was right about making something silly! :blink:

It is working great now!

I think I know what you mean being too slow. The PWM works with the micro controller internal counters and they cannot count up to such a big value. This is what happens when you do not have to look at datasheets to program !

Thank you,

Igor.

Igor Kondrasovas

www.inovativatec.com


#10 Ellen

Ellen

    Advanced Member

  • Members
  • PipPipPip
  • 65 posts
  • LocationRotterdam, Netherlands

Posted 25 September 2012 - 02:35 PM

Hi Chris, PWM problem solved in the update, servo is working fine now. Thank you. Ellen

#11 grimduck

grimduck

    New Member

  • Members
  • Pip
  • 2 posts

Posted 26 September 2012 - 10:19 PM

I just updated my netduino plus but it seems to have gone a bit wrong.

At the moment I cannot select it in visual studio as a device.
In MFDeploy I can ping it:
Pinging... TinyBooter
Bootloader build info: Netduino Plus (v4.2.0.1) by Secret Labs LLC


For a few seconds but then the blue onboard led goes dark and communication stops.
The power led is still on.

Pinging... Error: Can not connect to device

If I select the device capabilities I get following result:

Not Supported

I hope this can be fixed.

#12 mrb0y

mrb0y

    New Member

  • Members
  • Pip
  • 2 posts

Posted 27 September 2012 - 04:22 PM

I'm having a problem trying to update from 4.1.x. I unfortunately followed the instructions step by step assuming that if there were issues it would be documented. I zeroed my Netduino by 3.3v to the square and set about installing the ATMEL software on my windows 7 64bit machine only to find out that I'm not able to connect to the netduino??? Now I'm stuck with a bricked netduino and no way to update? I tried re-installing and several attempts at connect via the sam-cb. It sees the connection to USB and asks for a chip type and com port but after that it just sits there??? Any help would be greatly appreciated. I suggest that on the instructions to update the boot loader your preface the procedure with the "if is doesn't work for you you might want to try..." before the zeroing of the device.

#13 Paulo Jardim

Paulo Jardim

    New Member

  • Members
  • Pip
  • 8 posts

Posted 27 September 2012 - 08:05 PM

same problem here... after i do it and i click in ping.. Pinging... TinyCLR ( FINE ) But after i click in network, crash and never more come to TinyCLR now aways show : Pinging... TinyBooter Bootloader build info: Netduino Plus (v4.2.0.1) by Secret Labs LLC

#14 techie2sh

techie2sh

    New Member

  • Members
  • Pip
  • 1 posts

Posted 29 September 2012 - 11:16 AM

I am running netduino Plus on Windows 8 RTM. I have installed .net Micro Framework SDK v4.2(QFE2) and netduino SDK v4.2 64bit on my 64 bit system. I loaded the firmware v4.2.0.1 with SAM BA tool. But when I am not able to see anything on MFDeploy when I select USB though I can see the USB drivers installed for netduino. In addition to it, when I load the firamware v 4.2.0.0 RC4 then it displays NetduinoPlus_NetduinoPlus in USB of MSDeploy. But when I click on ping then it only shows Pinging... TinyCLR but not the second line. Also I am not able to deploy er_config and er_app from this.

#15 mrb0y

mrb0y

    New Member

  • Members
  • Pip
  • 2 posts

Posted 01 October 2012 - 12:15 AM

I got mine installed and updated. The problem was an incorrect selection for the chip on the Atmel tool. After I installed the 2.10v SAM-BA the pull down list had more selections including the one I was looking for. The tool does not default to the tab required to do the update though still allows you to choose a firmware and upload.

#16 grimduck

grimduck

    New Member

  • Members
  • Pip
  • 2 posts

Posted 06 October 2012 - 02:51 PM

My problem resolved after disable/enable of the netduino in the windows device manager. Not entire sure if this can even effect it :huh:

#17 Howie Goodell

Howie Goodell

    Member

  • Members
  • PipPip
  • 28 posts

Posted 09 October 2012 - 06:51 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.
...
To flash this firmware:
1. Detach your Netduino
2. Press and hold your Netduino's pushbutton while plugging it in via USB; this will put it in TinyBooter mode.
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.
c. Detach and reattach your Netduino (power cycle)

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

Chris


Hi Chris,

I finally am trying to upgrade my Netduino plus to this version, after encountering various problems trying to compile and deploy the 4.1.0.6 firmware. I installed TinyBooterDecompressor
http://wiki.netduino...ep-by-step.ashx
and tried 5x to download this firmware
NetduinoPlus_Firmware_4.2.0.1\tinyclr.hex\ER_FLASH and ER_CONFIG
following the instructions at
http://wiki.netduino...ep-by-step.ashx
Usually I first hit Erase for the Deployment and User Storage; once I also erased Firmware. Repeatedly disconnected and reconnected with the button down.

Each time, near the end of the progress bar to deploy ER_FLASH, I get a pop-up:
"Error: Unable to deploy to device"
Power cycle: comes back to Tiny Booter.

I didn't see exactly this problem in other forum posts. Anybody else have it?

Howie

#18 Chris Walker

Chris Walker

    Secret Labs Staff

  • Moderators
  • 7767 posts
  • LocationNew York, NY

Posted 09 October 2012 - 07:01 PM

Hi Howie, Are you using custom-compiled firmware or the pre-built firmware? Chris

#19 Howie Goodell

Howie Goodell

    Member

  • Members
  • PipPip
  • 28 posts

Posted 09 October 2012 - 07:08 PM

Hi Chris,

I finally am trying to upgrade my Netduino plus to this version, after encountering various problems trying to compile and deploy the 4.1.0.6 firmware.


My goal in switching to the latest version was to make my mistakes where they would be more useful. It seems I am already succeeding.

When I ran the Atmel SAM-BA utility and looked for the TinyBooterDecompressor.bin file, it was already selected. Gullible me: I thought by un-installing all the 4.1 SDKs etc. and re-installing 4.2 versions, it had selected the new version. Nope -- it was showing me the 4.1 version I had compiled yesterday, deep in the hierarchy of the 4.1 Porting Kit output directories (which uninstalling doesn't remove). Turkey!

I flashed the new version downloaded with the 4.2.0.1 firmware using SAM-BA. Now I can deploy the firmware, and it pings -- TinyCLR. Yah!

Howie

#20 Howie Goodell

Howie Goodell

    Member

  • Members
  • PipPip
  • 28 posts

Posted 09 October 2012 - 08:00 PM

One more question: the source link on the Downloads page gives me 8/12 sources. Chris, for those who want to compile interop changes, where can we get the sources that correspond with Update 1 firmware? Thanks! Howie




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.