Netduino home hardware projects downloads community

Jump to content


The Netduino forums have been replaced by new forums at community.wildernesslabs.co. This site has been preserved for archival purposes only and the ability to make new accounts or posts has been turned off.
Photo

Netduino Firmware v4.2.0 RC5 (Netduino + Netduino Plus)


  • Please log in to reply
138 replies to this topic

#1 Chris Walker

Chris Walker

    Secret Labs Staff

  • Moderators
  • 7767 posts
  • LocationNew York, NY

Posted 10 May 2012 - 09:57 PM

Version: 4.2.0 RELEASE CANDIDATE (version 4.2.0.0 RC5)

This firmware has been replaced by the 4.2.0.0 RTM firmware.
  • seraphletter likes this

#2 Chris Walker

Chris Walker

    Secret Labs Staff

  • Moderators
  • 7767 posts
  • LocationNew York, NY

Posted 10 May 2012 - 10:01 PM

If you experience bugs with the .NET MF 4.2 RC5 firmware, please post about it in this thread.

#3 emg

emg

    Advanced Member

  • Members
  • PipPipPip
  • 129 posts

Posted 10 May 2012 - 10:05 PM

Multicast support?

#4 JerseyTechGuy

JerseyTechGuy

    Advanced Member

  • Members
  • PipPipPip
  • 870 posts

Posted 10 May 2012 - 10:18 PM


6. StringBuilder support
7. Regular Expressions
10. Early support for some 4GB+ MicroSD cards (courtesy of community member KodeDaemon)
16. Bugfixes: SerialPort.DataReceived event should now fire properly
17. Bugfixes: SerialPort.Read() timeout now implemented properly
18. Bugfix: SD card support no longer interferes with digital pin 2


I'll try to spend some time testing the above as I have experienced issues with Pandora's Box related to these items.

#5 Herbrandson

Herbrandson

    New Member

  • Members
  • Pip
  • 2 posts

Posted 11 May 2012 - 04:13 AM

One small note on step #6 above. There are 2 "Browse..." buttons in MFDeploy. You want the 2nd one (the one just to the left of the "Deploy" button).

#6 PeterB

PeterB

    Member

  • Members
  • PipPip
  • 17 posts
  • LocationSydney, Australia

Posted 11 May 2012 - 03:20 PM

I have tried doing the upgrade but it failed during the Depolying ER_FLASH.hex with the error
Error: Unable to deploy to device.

I went back to 4.1.06 and that deployed okay (erase between deployment). However, after I changed teh Network and then deployed my previously working solution the program crashes. I changed the NETMF to 4.1 in VC

I have tried going back 4.2rc5 again following the exact steps including erase. I must be doing something wrong but for the life of me I can work it out, Yeah 01:17 in the morning but I'm sure I'm following the steps.

I notice that it is trying to erase again before deploying ER_FLASH. here is the info from MF_DEPLOY

Chk signature 
Signature PASS
Not Supported
Connecting to NetduinoPlus_NetduinoPlus...Connected
Not Supported
Pinging... TinyBooter
Bootloader build info: Netduino Plus by Secret Labs LLC
Not Supported
DeviceInfo is not valid!


#7 Chris Walker

Chris Walker

    Secret Labs Staff

  • Moderators
  • 7767 posts
  • LocationNew York, NY

Posted 11 May 2012 - 03:23 PM

Hi Peter, Can you provide a bit more info on what's happening when you try to upgrade? As long as you erase the board before flashing the new firmware, you should be fine. Let's see if we can get to the bottom of this for you :) Chris

#8 Laurelle

Laurelle

    Member

  • Members
  • PipPip
  • 16 posts
  • LocationFrance

Posted 11 May 2012 - 04:01 PM

Hello, I have a problem deploying this version of the framework. I just bought a new Netduino Plus board. Installed Framework was4.1.0.6 I've followed all the steps to deploy it but almost at the end of the ER_FLASH.hex deployment, I get an error: Error: Unable do deploy do device. Note also that I have another board with a 4.2.0 version on it and when I did the deployement it worked perfectly. I don't want to test the deployment on the other board because I'm using it in production to pilot my sprinklers… So any advice on what to test? Thanks
Doing dev is like doing sport. It's healthy :-)

#9 JerseyTechGuy

JerseyTechGuy

    Advanced Member

  • Members
  • PipPipPip
  • 870 posts

Posted 11 May 2012 - 04:23 PM

I just upgraded 3 boards and they all worked fine. Took less than 10 minutes for all 3. Erased all 3 with no issues. Used SAM-BA to install Boot Loader for 4.2RC5. Then installed CONFIG and FLASH. Took about 3 minutes per board total. One of the boards was brand new with 4.1 on it. The other two were 4.2.

#10 Chris Walker

Chris Walker

    Secret Labs Staff

  • Moderators
  • 7767 posts
  • LocationNew York, NY

Posted 11 May 2012 - 05:08 PM

Hi Laurelle, Did you erase your board completely (applying 3V3 to the gold ERASE pad) before reflashing? The flash layout has changed with this latest beta release (to allow more code space) so that's a necessary step. Chris

#11 Firegun

Firegun

    Member

  • Members
  • PipPip
  • 24 posts

Posted 11 May 2012 - 07:44 PM

I´m using a netduino plus and I´m having a problem related to network. The upgrade proccess ran with no problems, but after I configure the network settings (I´m using a fixed IP, just other subnet then the default 192.168.5.0/16). I got "Destination host unreachable" when I ping the board, I can see the act led blink on the ping requests. But... if I go to visual studio, deploy and application and start a new debug session, the network start to respond to pings and on the port I use on the program. When I restart (taking power out) the netduino I can´t access the network again. I´ve tried to start it with and without the network cable pluged in. I´ve tested with 4.2RC3, 4.2RC4 and 4.2RC5, they all give me similars results. With 4.1.1.0b1 it works as expected. On all firmwares my program runs well if started from VS, on 4.1 it works anyways. The program size is 14788 bytes. Any ideas? PS: But the problems related to blue screens when the USB cable was removed in the middle of a debug session, the "auto-reset feature", seems to be resolved! I´m using a 64-bit env :)

#12 Chris Walker

Chris Walker

    Secret Labs Staff

  • Moderators
  • 7767 posts
  • LocationNew York, NY

Posted 11 May 2012 - 08:28 PM

Hi Firegun, Quick question: did you set the MAC address (through MFDeploy) to match the sticker on the back of your Netduino Plus? If so, do you have a copy of Wireshark? That's probably the best place to start to diagnose the issue... Chris

#13 Firegun

Firegun

    Member

  • Members
  • PipPip
  • 24 posts

Posted 11 May 2012 - 08:37 PM

Hi Firegun,

Quick question: did you set the MAC address (through MFDeploy) to match the sticker on the back of your Netduino Plus?

If so, do you have a copy of Wireshark? That's probably the best place to start to diagnose the issue...

Chris


No I hadn´t done that, just did and the problem persists (on 4.2RC5). But I hadn´t done that on the 4.1.x and it worked fine with the default (00-00-00-00-00-01). I do have wireshark around, I´ll check if I can find the issue later, tnks for the quick reply, I´ll post any findings.

#14 PeterB

PeterB

    Member

  • Members
  • PipPip
  • 17 posts
  • LocationSydney, Australia

Posted 12 May 2012 - 02:01 AM

Hi Peter,

Can you provide a bit more info on what's happening when you try to upgrade? As long as you erase the board before flashing the new firmware, you should be fine.

Let's see if we can get to the bottom of this for you :)

Chris

Hi Chris,

When I did the erase I was using the ERASE in MF_DEPLOY. Reading later post in this thread I discovered I needed to do the full erase "Short 3.3v to GOLD ERASE PAD - near DIO 0". Also I found I needed to get AMTEL SAM-BA to install the boot-loader.

After reading DaveV's post, your post to Laurelle and the Wiki article http://wiki.netduino...ep-by-step.ashx I was able to finally get 4.2rc5 installed.

I had an issue were my Win7x64 machine would reboot if I pulled the USB to the Netduino+ out. This occurred even after reflashing the N+ with MF_DEPLOY. I noticed that during the install of AMTEL SAM-BA 2.11 that Win7 popped up a warning message about the driver that was going to be installed. I subsequently UN-installed AMTEL SAM-BA 2.11 and restarted the PC. The reboot PC problem is no longer present. Must be the SAM-BA driver.
EDIT: the REBOOT PC problem still exists if I pull the USB plug out during a DEPLOY hang.

I had to change the REFERENCES in my project. I used the suggested references from the template project now that I'm on 4.2.

Love the fact there is more RAM. I was running low, so now I can boost the size of my buffers for servicing HTTP request. Now I'm on 4.2 I will look at using later WebServers suggested/linked on the forums, as I'm currently using Fred's from 2010.

Thanks for your assistance.

#15 Cabadam

Cabadam

    Advanced Member

  • Members
  • PipPipPip
  • 90 posts

Posted 12 May 2012 - 04:30 AM

I had an issue were my Win7x64 machine would reboot if I pulled the USB to the Netduino+ out. This occurred even after reflashing the N+ with MF_DEPLOY. I noticed that during the install of AMTEL SAM-BA 2.11 that Win7 popped up a warning message about the driver that was going to be installed. I subsequently UN-installed AMTEL SAM-BA 2.11 and restarted the PC. The reboot PC problem is no longer present. Must be the SAM-BA driver.
EDIT: the REBOOT PC problem still exists if I pull the USB plug out during a DEPLOY hang.


If you are not already, try using the 4.2 drivers available here: http://forums.netdui...-for-net-mf-42/

#16 Cabadam

Cabadam

    Advanced Member

  • Members
  • PipPipPip
  • 90 posts

Posted 12 May 2012 - 04:32 AM

Chris,

Unfortunately the same bug network bug I found previously still exists in RC5. The same steps in the first post still recreate the problem.

http://forums.netdui...ted-on-boot-up/

#17 Laurelle

Laurelle

    Member

  • Members
  • PipPip
  • 16 posts
  • LocationFrance

Posted 12 May 2012 - 10:10 AM

I've installed SAM-BA 2.11 from the site, installed drivers as explained in the wiki (win7 x64, actually I'm on Win8 but same driver model). The driver install correctly and the board is recognize. I launch the SAM-BA sofware, the serial port is seen and I select "AT91SAM7x512-ex" but when I click on connect, it gives me an error message… So I don't know what to do now… And idea? Thanks
Doing dev is like doing sport. It's healthy :-)

#18 Laurelle

Laurelle

    Member

  • Members
  • PipPip
  • 16 posts
  • LocationFrance

Posted 12 May 2012 - 10:22 AM

OK, finally it worked :) I rebooted, changed USB port and redo the steps. The connection went well with the SAM-BA tool, flashing the bootloader also. And the rest went perfectly. Cool!
Doing dev is like doing sport. It's healthy :-)

#19 Chris Walker

Chris Walker

    Secret Labs Staff

  • Moderators
  • 7767 posts
  • LocationNew York, NY

Posted 12 May 2012 - 10:47 AM

Hi Cabadam,

Unfortunately the same bug network bug I found previously still exists in RC5. The same steps in the first post still recreate the problem.

http://forums.netdui...ted-on-boot-up/

Dang, I was hoping that the networking bugfixed in NETMF 4.2 QFE1 would fix that for you.

Can you post a bug report for this on netmf.codeplex.com? And title it "Ethernet never works if not connected on bott up with SAM7X"? We can work with Microsoft to address the issue from there...

Chris

#20 PeterB

PeterB

    Member

  • Members
  • PipPip
  • 17 posts
  • LocationSydney, Australia

Posted 12 May 2012 - 11:42 AM

If you are not already, try using the 4.2 drivers available here: http://forums.netdui...-for-net-mf-42/


I downlaoded all of the suggested (required) files listed http://forums.netdui...?showtopic=2768 I also tried the driver files you suggested, but still crash PC by pulling USB during a hung deployment.

I have also noticed that code that worked before in 4.1 now throws exceptions. Unfortunately I was not using any versioning of files so I can't go back. I have to work my way through these new issues.




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.