Netduino Firmware v4.2.0 RC5 (Netduino + Netduino Plus)
#41
Posted 14 May 2012 - 11:24 PM
#42
Posted 20 May 2012 - 06:23 PM
#43
Posted 21 May 2012 - 06:21 AM
I've upgrated to this RC and I ve lots of problems with Sockets. I've implemented a web server and I get random erros on sockets.
The web server is running ok for couple of minutes and then raise Socket erros. I can'ts really test with previous versions but I can reinstall a previous version is needed.
so it looks like there is a problem there. Looking at previous posts, it weems I'm not the only one with this problem. I can send the code if needed.
OK, so I'm replying to myself... Yes, there are problems which seems to be random. And I found a solution in this thread http://forums.netdui...h__1#entry28943
Basically, using a try and catch and ignoring the error solve the problem.
#44
Posted 23 May 2012 - 04:23 PM
#45
Posted 23 May 2012 - 05:29 PM
My .NETMF projects: .NETMF Toolbox / Gadgeteer Light / Some PCB designs
#46
Posted 28 May 2012 - 12:57 PM
'AnalogInput' is an ambiguous reference between 'Microsoft.SPOT.Hardware.AnalogInput' and 'SecretLabs.NETMF.Hardware.AnalogInput'
#47
Posted 28 May 2012 - 05:29 PM
Chris, I've attached a small sample project which I have replicated the problem on.
--snipped--
Chris,
I just wanted to follow up on this to see if you have had any success in recreating this, or if there is anything else I can try to reproduce.
Thanks!
#48
Posted 28 May 2012 - 10:33 PM
This is the code and trace.
using System; using System.Net; using System.Net.Sockets; using System.Threading; using Microsoft.SPOT; using Microsoft.SPOT.Hardware; using SecretLabs.NETMF.Hardware; using SecretLabs.NETMF.Hardware.NetduinoPlus; namespace ReproDnsBug { public class Program { static Timer __timer; public static void Main() { DnsTest(null); __timer = new Timer(DnsTest, null, 10000, 10000); Thread.Sleep(Timeout.Infinite); } static void DnsTest(object state) { try { Debug.Print(Dns.GetHostEntry("whitehouse.podzone.net").AddressList[0].ToString()); } catch (Exception) { Debug.Print("Fail"); } } } } Found debugger! Create TS. Loading start at 155dd8, end 16ebfc Assembly: mscorlib (4.2.0.0)Assembly: Microsoft.SPOT.Native (4.2.0.0)Assembly: Microsoft.SPOT.Hardware (4.2.0.0) Assembly: Microsoft.SPOT.Net (4.2.0.0)Assembly: System (4.2.0.0)Assembly: Microsoft.SPOT.Hardware.SerialPort (4.2.0.0) Assembly: Microsoft.SPOT.IO (4.2.0.0)Assembly: System.IO (4.2.0.0)Assembly: Microsoft.SPOT.Hardware.PWM (4.2.0.1) Assembly: Microsoft.SPOT.Hardware.Usb (4.2.0.0)Assembly: SecretLabs.NETMF.Hardware (4.2.0.0) Assembly: SecretLabs.NETMF.Diagnostics (4.2.0.0)Loading Deployment Assemblies. Attaching deployed file. Assembly: SecretLabs.NETMF.Hardware.NetduinoPlus (4.2.0.0)Attaching deployed file. Assembly: ReproDnsBug (1.0.0.0)Resolving. The debugging target runtime is loading the application assemblies and starting execution. Ready. 121.222.61.97 121.222.61.97 121.222.61.97 121.222.61.97 121.222.61.97 121.222.61.97 121.222.61.97 A first chance exception of type 'System.Net.Sockets.SocketException' occurred in Microsoft.SPOT.Net.dll Fail A first chance exception of type 'System.Net.Sockets.SocketException' occurred in Microsoft.SPOT.Net.dll Fail A first chance exception of type 'System.Net.Sockets.SocketException' occurred in Microsoft.SPOT.Net.dll Fail A first chance exception of type 'System.Net.Sockets.SocketException' occurred in Microsoft.SPOT.Net.dll Fail A first chance exception of type 'System.Net.Sockets.SocketException' occurred in Microsoft.SPOT.Net.dll Fail A first chance exception of type 'System.Net.Sockets.SocketException' occurred in Microsoft.SPOT.Net.dll Fail The program '[20] Micro Framework application: Managed' has exited with code 0 (0x0).
#49
Posted 29 May 2012 - 08:51 PM
Before deploying the attached firmware, you should erase your board completely and flash the v4.2 RC5 bootloader (included in the attached ZIP file).
Can you tell me how I might go about that? It isnt in your details unless I am missing it.
#50
Posted 29 May 2012 - 08:59 PM
There is a comment here:
Before deploying the attached firmware, you should erase your board completely and flash the v4.2 RC5 bootloader (included in the attached ZIP file).
Can you tell me how I might go about that? It isnt in your details unless I am missing it.
Hi,
Hopefully these instructions will work for you:
http://wiki.netduino...ep-by-step.ashx
- Cabadam likes this
My .NETMF projects: .NETMF Toolbox / Gadgeteer Light / Some PCB designs
#51
Posted 30 May 2012 - 07:29 AM
#52
Posted 30 May 2012 - 08:09 AM
#53
Posted 30 May 2012 - 03:17 PM
Is there any chance that you could take a quick WireShark log in both circumstances (both when DNS is working for you and when DNS is not working for you)?
Please find attached Wireshark capture. I filtered for host 192.168.0.100 which is the address statically configured on the N+
DNS is provided by a Netgear domestic router with the address 192.168.0.1
I ran the test app until it faulted. It was interesting to observe that only one ARP call occurred, right at the start.
Attached Files
#54
Posted 31 May 2012 - 02:25 AM
Dns.GetHostEntry(name) works perfectly if I call it early but when it's called a couple of minutes later it hangs. Anyone seen similar behaviour? It seems to take about 70 sec to fail.
I am not able to reproduce this on 4.2 RC3. It returned the correct IP in excess of 30 times. When I get a moment, I'll look at the wireshark file.
-Valkyrie-MT
P.S. I use 4.2 RC3 because I am still waiting for a firmware build with 1-wire...
#55
Posted 31 May 2012 - 02:35 AM
Please find attached Wireshark capture.
That Wireshark file has 4 irrelevant messages in it. I should see the 7 DNS requests and 7 responses before it starts to fail. Then comes the interesting part... Does Netduino continue to send the requests with no response? Does Netduino send a malformed response? Did an IP or MAC address change? That's what we are looking for...
Also, I tried this code with the Emulator and that worked fine as well. You should try it too and see what happens because the TCP/IP stack is different on the Emulator. If it works in the Emulator, it probably vindicates your network and points the finger at Netduino... maybe...
-Valkyrie-MT
#56
Posted 31 May 2012 - 06:59 AM
That Wireshark file has 4 irrelevant messages in it. I should see the 7 DNS requests and 7 responses before it starts to fail. Then comes the interesting part... Does Netduino continue to send the requests with no response? Does Netduino send a malformed response? Did an IP or MAC address change? That's what we are looking for...
Also, I tried this code with the Emulator and that worked fine as well. You should try it too and see what happens because the TCP/IP stack is different on the Emulator. If it works in the Emulator, it probably vindicates your network and points the finger at Netduino... maybe...
-Valkyrie-MT
This could also indicate incompetent use of Wireshark. I downloaded and installed it for the occasion, never having used it before. There was a surprising amount happening on our home network at 1am so after trawling the doco I added filter "host 192.168.0.100" started a capture and ran the app on the N+ but I am hardly expert in the use of it. I didn't have this network issue on this specific harware with 4.1.0.6, but I can tell you that the N+ didn't like my other router one little bit even with 4.1
It crosses my mind that the N+ has never been especially tolerant of busy networks and it is possible that I have actually run afoul of my stepson's enthusiasm for, ahem, torrents. I think that this evening I shall arrange for a quiet network and retry. If you have any instruction for me in the application of Wireshark to this problem, I should be grateful.
#57
Posted 31 May 2012 - 08:46 AM
Which genius didn't bother to check whether any other devices on his network had 192.168.0.100? Hmmmmm, that would be me.
On the bright side, now we all know that when DNS requests work for about 70 sec and then fail, it's probably an address collision.
Having resolved the address collision everything is now hunky dory.
On another note, Chris, you are a marvel, another 8K makes an unbelievable difference to my little logger.
#58
Posted 04 June 2012 - 03:56 PM
#59
Posted 04 June 2012 - 08:20 PM
#60
Posted 06 June 2012 - 04:54 AM
I followed the instructions but I get the following errors:
I already rebooted three times, plug and unplugged the netduino several times as well.
Here is the information about the MFDeploy I am using. I am able to ping the device though:
Please advise.
0 user(s) are reading this topic
0 members, 0 guests, 0 anonymous users