Netduino Firmware v4.2.0 RC5 (Netduino + Netduino Plus)
#1
Posted 10 May 2012 - 09:57 PM
This firmware has been replaced by the 4.2.0.0 RTM firmware.
- seraphletter likes this
#2
Posted 10 May 2012 - 10:01 PM
#3
Posted 10 May 2012 - 10:05 PM
#4
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
Posted 11 May 2012 - 04:13 AM
#6
Posted 11 May 2012 - 03:20 PM
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
Posted 11 May 2012 - 03:23 PM
#8
Posted 11 May 2012 - 04:01 PM
#9
Posted 11 May 2012 - 04:23 PM
#10
Posted 11 May 2012 - 05:08 PM
#11
Posted 11 May 2012 - 07:44 PM
#12
Posted 11 May 2012 - 08:28 PM
#13
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
Posted 12 May 2012 - 02:01 AM
Hi Chris,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
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
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
Posted 12 May 2012 - 04:32 AM
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
Posted 12 May 2012 - 10:10 AM
#18
Posted 12 May 2012 - 10:22 AM
#19
Posted 12 May 2012 - 10:47 AM
Dang, I was hoping that the networking bugfixed in NETMF 4.2 QFE1 would fix that for you.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/
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
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