Netduino home hardware projects downloads community

Jump to content


Photo

Netduino 1 Firmware v4.2.0 (update 1)


  • Please log in to reply
44 replies to this topic

#1 Chris Walker

Chris Walker

    Secret Labs Staff

  • Moderators
  • 7767 posts
  • LocationNew York, NY

Posted 19 September 2012 - 10:47 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:
128KB Flash
60KB+ RAM

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

This firmware also includes the following prior updates:
1. Visual Basic is now a supported language for .NET MF
2. New core AnalogInput and PWM classes; backwards-compatible classes available via add-on assemblies.
3. New WinUSB drivers (to remedy BSOD issues in 4.2 beta)
4. Garbage collector now fully collects old objects
5. 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 into your PC using a Micro USB cable.
4. In the Device section at top, select USB instead of Serial. Your Netduino 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)

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)

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

Chris

Attached Files



#2 antoniekruger

antoniekruger

    New Member

  • Members
  • Pip
  • 6 posts

Posted 10 October 2012 - 04:23 PM

Hi Chris, I've flashed the bootloader - 4.2.0.1, but then my PC do not recognise the Netduino board anymore. Ive repeated the flash a few times to make sure I get it right, but still nothing. Is it possible for the PC to be unable to associate the board identity with the driver after the bootloader flash? I removed the driver and re-plugged the board - it does not recognise the board or associate it with the supplied drivers. Any ideas? Antonie

#3 Chris Walker

Chris Walker

    Secret Labs Staff

  • Moderators
  • 7767 posts
  • LocationNew York, NY

Posted 10 October 2012 - 04:26 PM

Hi Antonie,

Hi Chris,
I've flashed the bootloader - 4.2.0.1, but then my PC do not recognise the Netduino board anymore. Ive repeated the flash a few times to make sure I get it right, but still nothing. Is it possible for the PC to be unable to associate the board identity with the driver after the bootloader flash?
I removed the driver and re-plugged the board - it does not recognise the board or associate it with the supplied drivers.


Did you upgrade the Netduino SDK to 4.2.0.1+ before flashing your board? The newest firmware uses the new WinUSB driver--which comes with the updated Netduino SDK.

Chris

#4 Mihail Romanov

Mihail Romanov

    New Member

  • Members
  • Pip
  • 2 posts

Posted 13 October 2012 - 09:24 AM

Hi, Chris

I tried to update firmware. Process completed OK, but i can't work with USBClient.

If i write then code
  var controllers = UsbController.GetControllers();

I get message

An unhandled exception of type 'System.NotSupportedException' occured in Microsoft.SPOT.Hardware.Usb.dll


This message appear if i only add reference to Microsoft.SPOT.Hardware.Usb in my project.

Also i tried, change Usb Configuration throug MFDeploy, but on this operation MFDeploy was not respond. I reattached Netduino and understood? that firmware wasn't load (MFDeploy on png commang write "Pinging ... TinyBooter").
I reflash firmware but situation wasn't change.

#5 Chris Walker

Chris Walker

    Secret Labs Staff

  • Moderators
  • 7767 posts
  • LocationNew York, NY

Posted 13 October 2012 - 03:33 PM

Hi Mihail,

I tried to update firmware. Process completed OK, but i can't work with USBClient.

We included beta support for UsbClient in the Netduino 4.1 firmware. It worked for specific applications, but not with the reliability and flexibility we wanted it to work.

With .NET MF 4.2, the new WinUSB driver configuration required that we remove the beta UsbClient support from NETMF (for reliability reasons). You could tweak the firmware and compile it back in, but it will be at the same beta state as in .NET MF 4.1.

BTW, there are several bug fixes in .NET MF 4.3 related to WinUSB. We'll explore options for UsbClient with this new release.

Welcome to the Netduino community,

Chris

#6 antoniekruger

antoniekruger

    New Member

  • Members
  • Pip
  • 6 posts

Posted 14 October 2012 - 08:29 PM

Hi Antonie,



Did you upgrade the Netduino SDK to 4.2.0.1+ before flashing your board? The newest firmware uses the new WinUSB driver--which comes with the updated Netduino SDK.

Chris


Hi Chris, thanks, I'm sorted. You were spot on. :D

#7 Mihail Romanov

Mihail Romanov

    New Member

  • Members
  • Pip
  • 2 posts

Posted 15 October 2012 - 04:40 AM

With .NET MF 4.2, the new WinUSB driver configuration required that we remove the beta UsbClient support from NETMF (for reliability reasons). You could tweak the firmware and compile it back in, but it will be at the same beta state as in .NET MF 4.1.


Thank you, Chris. I will wait 4.3 version.

#8 daGuy

daGuy

    New Member

  • Members
  • Pip
  • 3 posts

Posted 28 October 2012 - 07:36 PM

Hi, I just updated to this version (4.2.0.1) following all the steps and the Netduino works perfectly...until I try to use the PWM classes. Whenever I create a pwm output the whole Netduino freezes and is not recognized by windows anymore. I have to do a complete erase and flash the firmware again to revive it. Am I missing something important or is there a bug that nobody else seems to have seen so far? Googling didn't bring up any answers for me. Thanks for your help! Jens

#9 Arian

Arian

    Member

  • Members
  • PipPip
  • 18 posts

Posted 14 November 2012 - 06:06 AM

I'm about ready to give up. I'm trying to update the firmware and I'm not having any luck with the Tinybootloader upgrade. I bridged the gold dot and 3v, and I can get a GPS Camera Detect serial port (image0.png), but when I point Sam-ba to it, it accepts the port and chip type (image1.png), then simply disappears. If I try to run it again, I get a message indicating it's still running (image2.png), but I never see it again! What do I need to do?

Attached Files



#10 Chris Walker

Chris Walker

    Secret Labs Staff

  • Moderators
  • 7767 posts
  • LocationNew York, NY

Posted 14 November 2012 - 07:01 AM

Hi Arian, Are you running the latest version of SAM-BA (2.12+)? Have you tried rebooting your PC, unplugging and reattaching the board, and then running SAM-BA again? Chris

#11 Arian

Arian

    Member

  • Members
  • PipPip
  • 18 posts

Posted 14 November 2012 - 08:42 PM

Are you running the latest version of SAM-BA (2.12+)?

Have you tried rebooting your PC, unplugging and reattaching the board, and then running SAM-BA again?


Yes to all of the above.

#12 Chris Walker

Chris Walker

    Secret Labs Staff

  • Moderators
  • 7767 posts
  • LocationNew York, NY

Posted 14 November 2012 - 08:43 PM

Yes to all of the above.

Are you running Windows 8 by any chance? Sometimes I have to boot with driver signing enforcement disabled to get SAM-BA to work under Windows 8 x64.

Chris

#13 Yeison

Yeison

    New Member

  • Members
  • Pip
  • 5 posts

Posted 16 November 2012 - 01:55 AM

Are you running Windows 8 by any chance? Sometimes I have to boot with driver signing enforcement disabled to get SAM-BA to work under Windows 8 x64.

Chris


hi Chris.

I have the same problem Arian, I use Windows 7 but to give connect the window disappears.

Thank you.

#14 Chris Walker

Chris Walker

    Secret Labs Staff

  • Moderators
  • 7767 posts
  • LocationNew York, NY

Posted 16 November 2012 - 02:21 AM

Quick follow-up: On my Windows 8 laptop, SAM-BA works the first time. But when I re-open and try to use it again, it fails. I have to reboot to get it to work again. This happens consistently each time, working again after reboot. Atmel typically releases a new version of SAM-BA after each new version of Windows is released, so hopefully we will have a SAM-BA 2.13 soon and won't need this workaround. Chris

#15 jkrarup

jkrarup

    New Member

  • Members
  • Pip
  • 8 posts

Posted 19 November 2012 - 03:59 AM

Having the same problem. I am running System 7 32 bit and after choosing the device, SAM-BA 2.12 just disapears. When I try to run it again is says there is a instance of it already running, do I want to open another. Nothing seems to allow me to see the SAM-BA 2.12 app window. I see mention of a 2.12+. Is this a newer version or just to indicate 2.12 and above? I fixed the driver to use the new driver after is was defaulting to GPS Camera Detect driver so that is not the issue. I am running the SAM-BA as administrator also. I have rebooted many times. Do I need to use an older version and where can I download an older version?

#16 Big Bear Brian

Big Bear Brian

    Member

  • Members
  • PipPip
  • 17 posts

Posted 21 November 2012 - 07:32 AM

Hi Arian,

Are you running the latest version of SAM-BA (2.12+)?

Have you tried rebooting your PC, unplugging and reattaching the board, and then running SAM-BA again?

Chris


Chris,

I'm getting the same issue as Arian.

I'm getting it on Windows 8 (32-bit, running on a Netbook), Windows 7 (64-bit, Vaio), and Windows XP (32-bit, ancient Presario). I tried multiple machines to try to eliminate OS, processor type, and driver install problem as causes.

In each case, I'm using the latest Sam-Ba (v2.12), freshly installed.

I had great difficulties, but EVENTUALLY got the "GPS Camera Detect (COM11)" recognized.

No matter which machine, though, running in normal mode or in Administrator mode, Sam-Ba starts up, gives me the opportunity to connect to the Netduino as I've just specified (the GPS Camera...), and then disappears. Task manager shows that it is still running, and attempting to run Sam-Ba again results in the warning about running multiple instances.

Frustrated- is it possible to send the board back in and have it examined, and reflashed if possible?

Thanks,

Brian

#17 Chris Walker

Chris Walker

    Secret Labs Staff

  • Moderators
  • 7767 posts
  • LocationNew York, NY

Posted 21 November 2012 - 02:57 PM

Hi jkrarup,

Having the same problem. I am running System 7 32 bit and after choosing the device, SAM-BA 2.12 just disapears. When I try to run it again is says there is a instance of it already running, do I want to open another.

Hmm, it sounds like SAM-BA is getting stuck somewhere. Can you please try re-erasing your board, detaching and re-attaching it via USB, rebooting your computer, and then using SAM-BA before anything else?

Also, please verify that nothing is plugged into your Netduino (or its SD card slot) and that your Netduino is plugged directly into your PC via USB.

Nothing seems to allow me to see the SAM-BA 2.12 app window. I see mention of a 2.12+. Is this a newer version or just to indicate 2.12 and above?

Just a placeholder. We're hoping for a 2.13 with Windows 8 compatibility.

I fixed the driver to use the new driver after is was defaulting to GPS Camera Detect driver so that is not the issue. I am running the SAM-BA as administrator also. I have rebooted many times.

What does the device appear as in Device Manager now?

Do I need to use an older version and where can I download an older version?

If you need an older version, PM me with your e-mail address. But you may need access to an older machine (Windows XP mode?) for the older versions.

Chris

#18 Chris Walker

Chris Walker

    Secret Labs Staff

  • Moderators
  • 7767 posts
  • LocationNew York, NY

Posted 21 November 2012 - 03:00 PM

Hi Big Bear Brian,

I'm getting it on Windows 8 (32-bit, running on a Netbook), Windows 7 (64-bit, Vaio), and Windows XP (32-bit, ancient Presario). I tried multiple machines to try to eliminate OS, processor type, and driver install problem as causes.


If you have a Windows XP 32-bit machine, let's use it. And get you the older v2.09 firmware. Please PM me with your e-mail address.

Frustrated- is it possible to send the board back in and have it examined, and reflashed if possible?

How old is your Netduino? Are you in the USA by any chance? We don't have a system in place for this...but if we can't get reflashing to work for you then we can find a way :)

BTW, this is one of the things I love about Netduino Plus 2... Re-flashing the board does not require an erase pad. I wish the Atmel chips could work that way too; would be awesome.

Chris

#19 jkrarup

jkrarup

    New Member

  • Members
  • Pip
  • 8 posts

Posted 22 November 2012 - 05:22 AM

Sorry Chris,

I tried your suggestions with no luck. I see the sam-ba.exe process in the task manager but after the device selection window on startup, there is nothing. Any other suggestions? This is my first Netduino Plus and I have yet to be able to play with it. Would an older version of SAM-BA work better for me?

Hi jkrarup,


Hmm, it sounds like SAM-BA is getting stuck somewhere. Can you please try re-erasing your board, detaching and re-attaching it via USB, rebooting your computer, and then using SAM-BA before anything else?

Also, please verify that nothing is plugged into your Netduino (or its SD card slot) and that your Netduino is plugged directly into your PC via USB.


Just a placeholder. We're hoping for a 2.13 with Windows 8 compatibility.


What does the device appear as in Device Manager now?


If you need an older version, PM me with your e-mail address. But you may need access to an older machine (Windows XP mode?) for the older versions.

Chris



#20 Big Bear Brian

Big Bear Brian

    Member

  • Members
  • PipPip
  • 17 posts

Posted 22 November 2012 - 08:17 AM

If you have a Windows XP 32-bit machine, let's use it. And get you the older v2.09 firmware. Please PM me with your e-mail address.

How old is your Netduino? Are you in the USA by any chance? We don't have a system in place for this...but if we can't get reflashing to work for you then we can find a way :)


OK, partial success. I suspect it's been so long since I used Windows XP that I had forgotten how to properly run a program under Administrator permissions instead of just elevated user permissions. Shame on me. Too much W7, W8, and so forth.

Was able to get into Sam-Ba.
Was able to run the scripts, and send the bootstrapper.
Upon disconnecting and reconnecting the Netduino, though, it didn't recognize a device (that is, SAW that something was plugged in, but couldn't figure out what it was. Didn't show up in Device Manager, oddly-enough).

Will experiment more tomorrow (that's that this thing is for, right?) I've got another Netduino, a Mini, and a Plus for the projects I'm working on, at least, but I am kinda hoping to get them all flashed up to .NET MF 4.2 so that I can use a common code base in my project.

And I live in Sammamish, WA, working for a "little" software company in Redmond, WA.... ;-)

Brian




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.