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

#21 Chris Walker

Chris Walker

    Secret Labs Staff

  • Moderators
  • 7767 posts
  • LocationNew York, NY

Posted 10 October 2012 - 12:01 AM

Hi Howie,

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 for letting us know. We have updated the source on the downloads page to 4.2.0.1, including both the PWM and Netduino Mini bugfixes.

Chris

#22 Mike L

Mike L

    Advanced Member

  • Members
  • PipPipPip
  • 48 posts

Posted 25 October 2012 - 04:16 AM

I was wondering if anyone has had any issues flashing the firmware on a PC with Windows 8? I get an error at the end of the process right before the ER_FLASH file is fully deployed. The error is "Unable to deploy to device".

#23 Chris Walker

Chris Walker

    Secret Labs Staff

  • Moderators
  • 7767 posts
  • LocationNew York, NY

Posted 25 October 2012 - 04:59 AM

Hi Mike L, I'm using Windows 8 and haven't had any issues. Can you double-check that you flashed the TinyBooter that matches the ER_FLASH (TinyCLR) you're deploying? If the size expectations don't match up, you'll get a failure like that right before it finishes. Chris

#24 Mike L

Mike L

    Advanced Member

  • Members
  • PipPipPip
  • 48 posts

Posted 26 October 2012 - 03:45 AM

Hi Mike L,

I'm using Windows 8 and haven't had any issues. Can you double-check that you flashed the TinyBooter that matches the ER_FLASH (TinyCLR) you're deploying?

If the size expectations don't match up, you'll get a failure like that right before it finishes.

Chris


Yep that was my problem, I didn't read the instructions very well and forgot to do the TinyBooter first.

Thanks
Mike

#25 Old Hack

Old Hack

    New Member

  • Members
  • Pip
  • 6 posts

Posted 26 October 2012 - 12:52 PM

I cannot get SD cards to work since upgrading. I have seen a number of other posts where users who were successfully using SD cards now cannot since the upgrade. Is this being addressed and corrected?

#26 Chris Walker

Chris Walker

    Secret Labs Staff

  • Moderators
  • 7767 posts
  • LocationNew York, NY

Posted 26 October 2012 - 03:14 PM

Hi Old Hack,

I cannot get SD cards to work since upgrading. I have seen a number of other posts where users who were successfully using SD cards now cannot since the upgrade. Is this being addressed and corrected?

.NET MF 4.2 has updated SD drivers from the NETMF core. We are tweaking them (as we did the original NETMF SD drivers) as we find cards that don't work.

We recommend using SD cards of <=2GB. If your card is bigger and worked before...but doesn't work now...we'll need to tweak the firmware to get it compatible with that card again.

What brand, model, and size of card do you have?

Chris

#27 Leinad

Leinad

    New Member

  • Members
  • Pip
  • 1 posts

Posted 26 October 2012 - 03:53 PM

Hi, I'm a new user and got my netduino pro this week. I was trying to use a RHT03 sensor starting from the DhtSensorApp which someone posted on the forums, and then I hit some stability problems and learned about the 'slow clock' So I tried to upgrade the firmware. I think that I upgraded the Bootloader successfully (it says Bootloader Info: Netduino Plus (v4.2.0.1) by Secret Labs LLC). And apparently the new Firmware also got deployed correctly, as a Device Capabilities dump states: ChkHalSystemInfo.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 [...] Now, here's the problem: When I try to modify the Network Configuration (to set the MAC), something gets corrupted. I don't know what, but it *feels* like some location gets overwritten which shouldn't get to. I think that the issue is related to an IP or Subnet which I'm trying to configure. I'm attempting to set the IP to an address in the 10.x.x.x range, and the subnet to 255.0.0.0. With the out-of-the-box config of the Netduino (it was a 4.1.x) I didn't have the problem, and was able to set the IP statically to my preferred value. Now I can't do that anymore. I when pressing update I get a message "Unable to erase configuration sector memory". I believe that this is only after attemtping to change the IP or the subnet. And it takes a while for this message to appear. Like a minute or so. From then on, occascionally when attemting to read the Network Configuration, I get a message of bad or old configuration, also the Target/Device Capabilities resist to show any info, and Debug/Show Device Info says wrong firmware or something. If I flash the new Firmware and only update the MAC, and set DHCP to on (which I don't really want to do), then "all" works fine. Except that I can't use the network since it won't use the DHCP provided values, and the 'slow clock' issue still persists. Kind regards, Daniel

#28 Ellen

Ellen

    Advanced Member

  • Members
  • PipPipPip
  • 65 posts
  • LocationRotterdam, Netherlands

Posted 04 November 2012 - 10:48 AM

Hello Chris may I have your attention. We have notice that the Netduino Plus hangs when the socket.Connect is called when the internet connection is down after the N+ starts up. The only option was a reset. I have placed a full working example here: http://forums.netdui...es/page__st__20 You can run the code and on the same time stop the internet connection in your router. Then you see the error. My question, can you confirm this "bug" and do you have a workaround for it because writing to the Internet is het core of my program. Sometimes the internet connection is down here for a few minutes. I did a attempt with 4.3 beta but deploying to the N+ was without any succes.

#29 Chris Walker

Chris Walker

    Secret Labs Staff

  • Moderators
  • 7767 posts
  • LocationNew York, NY

Posted 04 November 2012 - 04:21 PM

Hi Ellen,

My question, can you confirm this "bug" and do you have a workaround for it because writing to the Internet is het core of my program. Sometimes the internet connection is down here for a few minutes. I did a attempt with 4.3 beta but deploying to the N+ was without any succes.

The best option is to use the new NETMF 4.3 release. You can use the beta SDK--but it won't change the firmware on your board. The first NETMF 4.3 beta firmware should be available this month.

Chris

#30 logicalstep

logicalstep

    Member

  • Members
  • PipPip
  • 21 posts

Posted 04 November 2012 - 06:33 PM

Hi Chris, I've just got back to my Netduino after a little while and though I'd update the firmware to the latest version. I've downloaded the new 4.2 firmware and Flashed the new TinyBooterDecompressor.bin & TinyCLR and the 4.2 firmware, however when I ping right after flashing the TinyBooterDecompressor.bin, I get a response, but as soon as I flash the two image files I get nothing. The board shows up in the MFDeploy software, but I can't ping it or deploy to it. I've tried the new win and old Mf driver, but no change. Any ideas? Many thanks Trevor

#31 Ellen

Ellen

    Advanced Member

  • Members
  • PipPipPip
  • 65 posts
  • LocationRotterdam, Netherlands

Posted 05 November 2012 - 08:55 AM

Hi Ellen,


The best option is to use the new NETMF 4.3 release. You can use the beta SDK--but it won't change the firmware on your board. The first NETMF 4.3 beta firmware should be available this month.

Chris

Thank you Chris, we are waiting for the 4.3 beta this month. We hope the internet glitch is than solved.

@Travor, you did not install (correct) the Netduino driver, please read all the steps to install at the begin.

#32 logicalstep

logicalstep

    Member

  • Members
  • PipPip
  • 21 posts

Posted 05 November 2012 - 11:16 AM

Thank you Chris, we are waiting for the 4.3 beta this month. We hope the internet glitch is than solved.

@Travor, you did not install (correct) the Netduino driver, please read all the steps to install at the begin.


Hi Ellen,

Thanks for the response, I have tried starting from scratch and installed both of the drivers one by one and I definitely have the correct firmware and Bootloader installed, so I'm a bit lost really.

Many thanks

Trevor

#33 Chris Walker

Chris Walker

    Secret Labs Staff

  • Moderators
  • 7767 posts
  • LocationNew York, NY

Posted 05 November 2012 - 03:14 PM

Hi Trevor,

Thanks for the response, I have tried starting from scratch and installed both of the drivers one by one and I definitely have the correct firmware and Bootloader installed, so I'm a bit lost really.

If you flash the original 4.1 TinyBooter and TinyCLR onto the board...does it work for you?

If so, let's walk through the versions of everything you have. There may be an incompatibility between the NETMF 4.2 SDK and your PC or there may be a version conflict somewhere.

Chris

#34 lvw

lvw

    Member

  • Members
  • PipPip
  • 11 posts
  • LocationZuid Holland, The Netherlands

Posted 10 November 2012 - 09:44 PM

So I tried to upgrade the firmware. I think that I upgraded the Bootloader successfully (it says Bootloader Info: Netduino Plus (v4.2.0.1) by Secret Labs LLC). And apparently the new Firmware also got deployed correctly, as a Device Capabilities dump states:

**** more stuff here ****

When I try to modify the Network Configuration (to set the MAC), something gets corrupted. I don't know what, but it *feels* like some location gets overwritten which shouldn't get to.

I think that the issue is related to an IP or Subnet which I'm trying to configure. I'm attempting to set the IP to an address in the 10.x.x.x range, and the subnet to 255.0.0.0.

With the out-of-the-box config of the Netduino (it was a 4.1.x) I didn't have the problem, and was able to set the IP statically to my preferred value. Now I can't do that anymore.

I when pressing update I get a message "Unable to erase configuration sector memory". I believe that this is only after attemtping to change the IP or the subnet. And it takes a while for this message to appear. Like a minute or so.

From then on, occascionally when attemting to read the Network Configuration, I get a message of bad or old configuration, also the Target/Device Capabilities resist to show any info, and Debug/Show Device Info says wrong firmware or something.

If I flash the new Firmware and only update the MAC, and set DHCP to on (which I don't really want to do), then "all" works fine. Except that I can't use the network since it won't use the DHCP provided values, and the 'slow clock' issue still persists.

Kind regards,
Daniel



Same here.

I'm positive I'm using the correct Bootloader with the correct firmware (4.2.0.1), it's packed in the same ZIP file thats in the attachment in the firmware post.

After installing the bootloader (and unplugging + plugging back in), MFDeploy Ping responds with;
Pinging... TinyBooter
Bootloader build info: Netduino Plus (v4.2.0.1) by Secret Labs LLC


After installing the firmware (both ER_FLASH and ER_CONFIG)
Chk signature
Signature PASS

(unplugging + plugging back in)

Pinging... TinyCLR


Then, when I go into Target > Configuration > Network;
The blue (user led) goes on, after a while off, then it hangs a minute or two, shows;
Device has old or unsupported configuration


When I retry to deploy the firmware again it states; 'Error: Unable to deploy to device' in a error box. The console shows
*** nXIP Program found at 0x0010 after a few seconds.



When I'm able to access the network configuration (yes, sometimes it lets me after doing all of the above) saving the settings hangs and stops with an error. After that, Ping results back into:

Pinging... TinyBooter
Bootloader build info: Netduino Plus (v4.2.0.1) by Secret Labs LLC

(As if the firmware is removed again).


Does anyone have any suggestions? I'm suspecting a bad firmware or bad reference to memory somewhere (or maybe even corrupted memory?)

For now i'm left with a non working Netduino Plus :-( (don't want to downgrade to 4.1.*)

#35 Chris Walker

Chris Walker

    Secret Labs Staff

  • Moderators
  • 7767 posts
  • LocationNew York, NY

Posted 10 November 2012 - 09:46 PM

Hi lvw, The procedure to set the network settings on Netduino Plus changed with .NET MF 4.2 QFE2. This is due to the WinUSB drivers. After you flash your board, please put it in TinyBooter mode before setting the network configuration. If you try to change it from the fully-booted (TinyCLR) mode, NETMF may get stuck in TinyBooter mode and require reflashing the board. Chris

#36 lvw

lvw

    Member

  • Members
  • PipPip
  • 11 posts
  • LocationZuid Holland, The Netherlands

Posted 10 November 2012 - 10:02 PM

Hi lvw,

The procedure to set the network settings on Netduino Plus changed with .NET MF 4.2 QFE2. This is due to the WinUSB drivers.

After you flash your board, please put it in TinyBooter mode before setting the network configuration. If you try to change it from the fully-booted (TinyCLR) mode, NETMF may get stuck in TinyBooter mode and require reflashing the board.

Chris




Hi Chris,

Thanks, I tried that and it seems to work.

I feel stupid for not reading that part at the end of the topic start :-(

#37 thratchen

thratchen

    New Member

  • Members
  • Pip
  • 5 posts

Posted 11 November 2012 - 03:32 PM

Chris, I had a Netduino Plus board with earlier firmware and so I had to follow the TinyBooter update process: So, I followed your process: 1. Erase your Netduino by applying 3V3 power to the gold ERASE pad a. Detach and reattach your Netduino (power cycle) 2. Flash TinyBooterDecompressor.bin using SAM-BA v2.12+ And for 2, I used the video () for additional help since I've never had to flash the TinyBooter before. I followed the process carefully, but the board doesn't respond to MFDeploy pings after the update. I detached from power the board once it was flashed and I have the most current MF and Netduino drivers that are linked on your original post. Any ideas of what I could have messed up? How do I figure out what's up with the board and if I bricked it? Thanks, Geoffrey

#38 Chris Walker

Chris Walker

    Secret Labs Staff

  • Moderators
  • 7767 posts
  • LocationNew York, NY

Posted 11 November 2012 - 05:31 PM

Hi Geoffrey,

I followed the process carefully, but the board doesn't respond to MFDeploy pings after the update. I detached from power the board once it was flashed and I have the most current MF and Netduino drivers that are linked on your original post.

Any ideas of what I could have messed up? How do I figure out what's up with the board and if I bricked it?

Very interesting. Just to confirm: you can see the device listed in MFDeploy but when you press Ping, you just get a timeout?

Could you try manually switching the drivers from WinUSB to MFUSB really quick?
http://forums.netdui...-mfusb-drivers/

I've heard a few isolated cases where WinUSB drivers weren't happy with a particular machine...

If the device is showing up in MFDeploy, it's very unlikely that the device is bricked. Also you can always try to load the older firmware on the board and see if that works; the latest SDK works with earlier firmware as well.

Chris

#39 DanielSan

DanielSan

    New Member

  • Members
  • Pip
  • 2 posts

Posted 18 November 2012 - 12:48 AM

Hello I've got Netduino + with 4.1.0.6 When i flashed to 4.2.0.1 and put appliaction with Net socket all all the time blue led was light. And driver USB was hang I returned to 4.1.0.6. Application without socket work normally. But i can put appliaction with net socket its not working. Do you know where is problem?

#40 Chris Walker

Chris Walker

    Secret Labs Staff

  • Moderators
  • 7767 posts
  • LocationNew York, NY

Posted 18 November 2012 - 05:33 PM

Hi DanielSan,

Do you know where is problem?

Did you convert your .NET MF app from a NETMF 4.1 app to a NETMF 4.2 app (by changing the target framework option in Project Properties)?

Chris




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.