Netduino home hardware projects downloads community

Jump to content


Photo

Netduino Plus 1 Firmware v4.1.0 (update 6)


  • Please log in to reply
17 replies to this topic

#1 Chris Walker

Chris Walker

    Secret Labs Staff

  • Moderators
  • 7767 posts
  • LocationNew York, NY

Posted 02 March 2011 - 12:36 AM

Here is the Netduino Plus firmware. This update is recommended for all users. Version: 4.1.0 Update 6 (version 4.1.0.6) With this firmware, you will have the following resources available for your code: 64KB Flash 28KB+ RAM This firmware includes the following updates: 1. Enhanced Parallels, VMWare, and VirtualBox compatibility 2. Garbage collection 'status messages' updated 3. Visual Studio debugger should connect to Netduino easier during deployment (on non-virtual machines) 4. Bugfixes: DHCP should now work properly on more/all routers 5. Bugfixes: Network cables can now be connected after board is powered up 6. Bugfixes: SerialPort.DataReceived event should now fire properly 7. Bugfixes: SerialPort.Read() timeout now implemented properly 8. Bugfixes: Misc. SPI bugfixes To find the current version of your Netduino Plus firmware: 1. Go to the Start Menu > Programs > Microsoft .NET Micro Framework 4.1 > 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.1.0.5 or earlier may update to this new firmware using the MFDeploy tool: 1. Download and unzip the attached file to a directory on your computer. 2. Go to the Start Menu > Programs > Microsoft .NET Micro Framework 4.1 > Tools 3. Run MFDeploy.exe. Be careful to run MFDeploy.exe and not MFDeploy.exe.config (as file extensions are hidden by default) 4. Plug your Netduino Plus into your PC using a Micro USB cable. If your Netduino Plus does not connect successfully, try plugging the USB cable into your Netduino first...and then your PC. 5. In the Device section at top, select USB instead of Serial. Your Netduino Plus should appear in the drop-down; if not, select it. 6. Click "Browse..." and select the unzipped files from step #1 (ER_CONFIG and ER_FLASH). 7. Press "Deploy". It will take a few minutes to update your Netduino Plus. 8. Select the Target > Configuration > Networking menu. You will need to re-enter your IP address settings and MAC address. We will try to eliminate this step in the future. The following previous updates are also included in this release: 1. USB and serial deployment now selectable via software tool 2. Data corruption fix for MicroSD card access 3. Enhanced networking performance 4. Netduino Plus boots faster when not using networking 5. Network timeouts should now occur (instead of board lockup) 6. Tight loops no longer lock out debugger 7. Exception thrown when mounting incompatible/non-existent MicroSD card 8. Reduced memory usage for SD card access 9. Garbage collection 'status messages' updated 10. .NET MF 4.1 Post-QFE1 HAL bugfixes NOTE FOR ADVANCED USERS: you can erase your Netduino Plus and reflash it with Netduino firmware (TinyBooterDecompressor via SAM-BA and then .NET Micro Framework via MFDeploy). This will give you 128KB of Flash and 60KB of RAM--but will remove the lwIP networking feature.

Attached Files



#2 Chris Walker

Chris Walker

    Secret Labs Staff

  • Moderators
  • 7767 posts
  • LocationNew York, NY

Posted 02 March 2011 - 12:39 AM

Some users may erase their Netduino Pluses completely to use them as low-cost ARM development boards or to otherwise tinker. In this case, it will necessary to redeploy the TinyBooter bootloader before redeploying the Netduino Plus firmware. If you want to switch between Netduino firmware and Netduino Plus firmware, you will need to erase your Netduino Plus completely and re-flash the respective bootloader using Atmel SAM-BA. This may require access to a 32-bit Windows PC. To use the new "USB and serial - deployment selection" feature, you'll need to erase your Netduino and reflash the bootloader as well. The TinyBooter booloader (v4.1.0.6) is attached to this post for your convenience.

Attached Files



#3 Chris Walker

Chris Walker

    Secret Labs Staff

  • Moderators
  • 7767 posts
  • LocationNew York, NY

Posted 02 March 2011 - 12:44 AM

One final note... A small number of Netduino Pluses were available for a "public beta" at MakerFaire NY and from worldwide resellers in September 2010. These Netduino Pluses shipped with a bootloader which only enabled 48KB of codespace (instead of 64KB of codespace). To upgrade to v4.1.1 and newer firmware releases, users of the "public beta" units will need to update their bootloaders. But we're making a special build of v4.1.0.6 available for users who prefer not to update their bootloader. Both the 48KB bootloader and special "48KB" v4.1.0.6 firmware are attached to this post.

Attached Files



#4 newbietoo

newbietoo

    New Member

  • Members
  • Pip
  • 4 posts

Posted 18 April 2012 - 05:15 PM

Help, I have been trying to get this board to work on the network, all projects will load other than web projects. I originally received "not supported" from the MFDeploy when trying to check the current level. I have downloaded the v4.1.0.zip and deployed the files. The ER_Flash will finish, but the ER_CONFIG does not seem to finish and the "box" does not go away. If I try to cancel, it will not and I actually have to use task manager to kill it. I have been able to read the configuration after restarting but still also get the "not supported". I am powering this only with the usb cable and no other power, the pwr light doesn't flicker when the network cable is plugged in (doesn't seem to loading it down). I have been able to get into network configuration 1 time to change the configuration and am able to ping the board. I have tried 2 different pc's to see if the there might be a problem, both are running xp with the current updates. Unfortunatily this is the only board I have, so I'm unable to see if it is a board problem or the one sitting at the keyboard. I appreciate any direction to make this work properly

#5 James Abbott

James Abbott

    Member

  • Members
  • PipPip
  • 19 posts
  • LocationYorkshire, UK

Posted 18 April 2012 - 06:48 PM

Help, I have been trying to get this board to work on the network, all projects will load other than web projects. I originally received "not supported" from the MFDeploy when trying to check the current level. I have downloaded the v4.1.0.zip and deployed the files. The ER_Flash will finish, but the ER_CONFIG does not seem to finish and the "box" does not go away. If I try to cancel, it will not and I actually have to use task manager to kill it. I have been able to read the configuration after restarting but still also get the "not supported". I am powering this only with the usb cable and no other power, the pwr light doesn't flicker when the network cable is plugged in (doesn't seem to loading it down). I have been able to get into network configuration 1 time to change the configuration and am able to ping the board. I have tried 2 different pc's to see if the there might be a problem, both are running xp with the current updates. Unfortunatily this is the only board I have, so I'm unable to see if it is a board problem or the one sitting at the keyboard. I appreciate any direction to make this work properly


Hi newbietoo,

Have you tried resetting the board totally? When I was upgrading firmware I had something similar but it was because I forgot to update the TinyBootloader :blink:

http://wiki.netduino...ep-by-step.ashx

Thanks.

#6 newbietoo

newbietoo

    New Member

  • Members
  • Pip
  • 4 posts

Posted 18 April 2012 - 09:48 PM

Hi newbietoo,

Have you tried resetting the board totally? When I was upgrading firmware I had something similar but it was because I forgot to update the TinyBootloader :blink:

http://wiki.netduino...ep-by-step.ashx

Thanks.



#7 newbietoo

newbietoo

    New Member

  • Members
  • Pip
  • 4 posts

Posted 18 April 2012 - 09:54 PM

Thanks for the help, should I be concerned that the atmel chip I have is AT91SAM7X512 AU

#8 Chris Walker

Chris Walker

    Secret Labs Staff

  • Moderators
  • 7767 posts
  • LocationNew York, NY

Posted 18 April 2012 - 10:09 PM

Thanks for the help, should I be concerned that the atmel chip I have is AT91SAM7X512 AU

That's the chip used on Netduino and Netduino Plus, so you should be good to go.

Chris

#9 newbietoo

newbietoo

    New Member

  • Members
  • Pip
  • 4 posts

Posted 18 April 2012 - 10:21 PM

Thanks Chris. I'm only seeing Chk signature signature pass repeated twice and the executing Application with the green progress all the way to the right, should the box go away or should I just cancel?

#10 Chris Walker

Chris Walker

    Secret Labs Staff

  • Moderators
  • 7767 posts
  • LocationNew York, NY

Posted 18 April 2012 - 10:50 PM

Hi newbietoo,

Thanks Chris. I'm only seeing Chk signature signature pass repeated twice and the executing Application with the green progress all the way to the right, should the box go away or should I just cancel?

If you unplug and reattach your Netduino Plus and you're able to deploy to it...you're all good.

If not, erase the board using the gold erase pad and reflash TinyBooterDecompressor...then flash the NETMF firmware (TinyCLR).

Chris

#11 Veldy

Veldy

    New Member

  • Members
  • Pip
  • 1 posts
  • LocationTwin Cities, MN USA

Posted 05 May 2012 - 04:00 PM

Hi newbietoo,

If you unplug and reattach your Netduino Plus and you're able to deploy to it...you're all good.

If not, erase the board using the gold erase pad and reflash TinyBooterDecompressor...then flash the NETMF firmware (TinyCLR).

Chris


I am planning on trying the update to 4.2.0 and downgrade to the stable 4.1 version before doing any work. However, I have not been able to get any SMB-BA flash utility to work on either of my available windows machines (Win7 Pro x64). The problem is that I can't get the Atmel drivers to install instead of the Netduino drivers so that the utility can recognize the chip and flash it. The OS complains that they are are not 64-bit drivers. Any advice on a work around? I am using SMB-BA 2.11 for reference.
Veldy

#12 nakchak

nakchak

    Advanced Member

  • Members
  • PipPipPip
  • 404 posts
  • LocationBristol, UK

Posted 09 May 2012 - 01:11 PM

I am planning on trying the update to 4.2.0 and downgrade to the stable 4.1 version before doing any work. However, I have not been able to get any SMB-BA flash utility to work on either of my available windows machines (Win7 Pro x64). The problem is that I can't get the Atmel drivers to install instead of the Netduino drivers so that the utility can recognize the chip and flash it. The OS complains that they are are not 64-bit drivers. Any advice on a work around? I am using SMB-BA 2.11 for reference.


Have you tried the instruction I posted here solved all the issues I have ever had with SAMBA not opening or detecting connected boards under x64 windows.

Nak.

#13 tknman0700

tknman0700

    Member

  • Members
  • PipPip
  • 26 posts

Posted 31 May 2012 - 03:40 AM

are there updated drivers for running this firmware? Visual Studio crashing all the time when debug.

#14 uyasduh

uyasduh

    New Member

  • Members
  • Pip
  • 2 posts

Posted 18 July 2012 - 12:46 AM

Thanks for the help, should I be concerned that the atmel chip I have is AT91SAM7X512 AU

#15 nakchak

nakchak

    Advanced Member

  • Members
  • PipPipPip
  • 404 posts
  • LocationBristol, UK

Posted 18 July 2012 - 07:53 AM

Thanks for the help, should I be concerned that the atmel chip I have is AT91SAM7X512 AU


No thats a standard part, I think all ND+'s i have ever had my hands on (20 odd) have had that model of chip.

Nak.

#16 Nzc

Nzc

    Member

  • Members
  • PipPip
  • 17 posts
  • LocationNetherlands

Posted 03 October 2012 - 08:38 AM

I'm running SAM-BA 2.12 on Win7-x64, and that works fine. I can do the reset, connect to the Netduino and run the scripts. However, when I flash the bootloader (TinyBooterDecompressor) and then read the file back, there are always differences. Strange thing is, when using the memory spy from the SAM-BA tool, not all errors are visible... I am wondering whether the flash in the Atmel is maybe damaged, or whether there is a problem with the different revisions (EK vs. AU)?

#17 Chris Walker

Chris Walker

    Secret Labs Staff

  • Moderators
  • 7767 posts
  • LocationNew York, NY

Posted 03 October 2012 - 02:22 PM

Hi Nzc,

I'm running SAM-BA 2.12 on Win7-x64, and that works fine. I can do the reset, connect to the Netduino and run the scripts. However, when I flash the bootloader (TinyBooterDecompressor) and then read the file back, there are always differences. Strange thing is, when using the memory spy from the SAM-BA tool, not all errors are visible... I am wondering whether the flash in the Atmel is maybe damaged, or whether there is a problem with the different revisions (EK vs. AU)?

Before doing the compare in SAM-BA, did you add a few zeros to the "size" value? If not, it will only read the first small bit of FLASH and since the size isn't big enough it will give you a verification failure.

Regarding EK vs AU... -EK means "evaluation kit" and is the name of the main development board for AT91SAM7X512-AU. It uses the same chip as Netduino which is why we use its script to flash the Netduino. Since they both use the same chip, they both flash using the same configuration.

Chris

#18 Nzc

Nzc

    Member

  • Members
  • PipPip
  • 17 posts
  • LocationNetherlands

Posted 04 October 2012 - 08:58 PM

Hi Nzc,


Before doing the compare in SAM-BA, did you add a few zeros to the "size" value? If not, it will only read the first small bit of FLASH and since the size isn't big enough it will give you a verification failure.

Regarding EK vs AU... -EK means "evaluation kit" and is the name of the main development board for AT91SAM7X512-AU. It uses the same chip as Netduino which is why we use its script to flash the Netduino. Since they both use the same chip, they both flash using the same configuration.

Chris


Yes, I make sure to read enough bytes to make the comparison. I had a closer look at the data, and it's always the same bit that appears to be 1 when sometimes it should be 0, and only in one memory block. Can it be that the flash memory is corrupt? At least the file I read back is always the same, but different from what I try to write :(

When I reset gold pad - 3.3V, I can always get back to the CDC connection, and scripts and downloads always run fine, I just don't get the right code in the flash. When reconnecting after the flash, the USB gives a low-level error, and I don't see any info, not even the usual vid/pid stuff.




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.