mattcro

I've just updated my shiny new Netduino2 Plus to the 4.2.1.2 firmware. I got it erased with STDFU tester OK, but could not get it to flash properly with Dfuse. I tried a couple of times to erase/flash, even unplugging the N2+ in between and double-checking that it was in DFU mode but no joy. I'm using Win7 64bit, and Dfuse/STDFU version is 3.0.1.

 

I ended up doing everything in STDFU. After re-erasing in STDFU just in case, I did this:

• Click "Load DFU file" and select the 4.2.1.2 DFU file. You should see a bunch of data in the Images window.
• Select "Download" radio button and clock "Go" and it does the actual programming cycle. Hopefully you'll get a "success" message.
• Select "Leave DFU mode" radio button and click "Go".
• Unplug Netduino and plug back in, then check firmware version in MFDeploy->Target->Device Capabilities

I've been trying to check my output code size, and cannot see the same sort of size info that stefan quoted above. I don't think I've changed any compile/project options related to build/deploy, and I'm sure I used to see this, at least briefly.

Am I doing this right, or is it likely that I've mistakenly disabled output of assembly and total size info? Or have I already missed it at the output stage shown below?

I now have VS 2010 Express SP1, .NETMF 4.2QFE1 and Netduino+ firmware 4.2RC4. Typical debug window output now looks like this:

Found debugger!

Create TS.

Loading start at 155b88, end 16e8e0

Attaching file.

Attaching file.

Attaching file.

Attaching file.

Attaching file.

Attaching file.

Attaching file.

Attaching file.

Attaching file.

Attaching file.

Attaching file.

Attaching file.

Loading Deployment Assemblies.

Attaching deployed file.

Attaching deployed file.

Attaching deployed file.

Resolving.

The debugging target runtime is loading the application assemblies and starting execution.
Ready.

'Microsoft.SPOT.Debugger.CorDebug.dll' (Managed): Loaded 'C:\Program Files (x86)\Microsoft .NET Micro Framework\v4.2\Assemblies\le\mscorlib.dll', Symbols loaded.
'Microsoft.SPOT.Debugger.CorDebug.dll' (Managed): Loaded 'C:\Program Files (x86)\Microsoft .NET Micro Framework\v4.2\Assemblies\le\Microsoft.SPOT.Native.dll', Symbols loaded.
'Microsoft.SPOT.Debugger.CorDebug.dll' (Managed): Loaded 'C:\Program Files (x86)\Microsoft .NET Micro Framework\v4.2\Assemblies\le\Microsoft.SPOT.Hardware.dll', Symbols loaded.
'Microsoft.SPOT.Debugger.CorDebug.dll' (Managed): Loaded 'C:\Program Files (x86)\Microsoft .NET Micro Framework\v4.2\Assemblies\le\Microsoft.SPOT.Net.dll', Symbols loaded.
'Microsoft.SPOT.Debugger.CorDebug.dll' (Managed): Loaded 'C:\Program Files (x86)\Microsoft .NET Micro Framework\v4.2\Assemblies\le\System.dll', Symbols loaded.
'Microsoft.SPOT.Debugger.CorDebug.dll' (Managed): Loaded 'C:\Program Files (x86)\Microsoft .NET Micro Framework\v4.2\Assemblies\le\Microsoft.SPOT.Hardware.SerialPort.dll', Symbols loaded.
'Microsoft.SPOT.Debugger.CorDebug.dll' (Managed): Loaded 'C:\Program Files (x86)\Microsoft .NET Micro Framework\v4.2\Assemblies\le\Microsoft.SPOT.IO.dll', Symbols loaded.
'Microsoft.SPOT.Debugger.CorDebug.dll' (Managed): Loaded 'C:\Program Files (x86)\Microsoft .NET Micro Framework\v4.2\Assemblies\le\System.IO.dll', Symbols loaded.
'Microsoft.SPOT.Debugger.CorDebug.dll' (Managed): Loaded 'C:\Program Files (x86)\Microsoft .NET Micro Framework\v4.2\Assemblies\le\Microsoft.SPOT.Hardware.PWM.dll', Symbols loaded.
'Microsoft.SPOT.Debugger.CorDebug.dll' (Managed): Loaded 'C:\Program Files (x86)\Microsoft .NET Micro Framework\v4.2\Assemblies\le\Microsoft.SPOT.Hardware.Usb.dll', Symbols loaded.
'Microsoft.SPOT.Debugger.CorDebug.dll' (Managed): Loaded 'C:\Program Files (x86)\Secret Labs\Netduino SDK\Assemblies\v4.2\le\SecretLabs.NETMF.Hardware.dll', Symbols loaded.
'Microsoft.SPOT.Debugger.CorDebug.dll' (Managed): Loaded 'SecretLabs.NETMF.Diagnostics'
'Microsoft.SPOT.Debugger.CorDebug.dll' (Managed): Loaded 'C:\Program Files (x86)\Secret Labs\Netduino SDK\Assemblies\v4.2\le\SecretLabs.NETMF.IO.dll', Symbols loaded.
'Microsoft.SPOT.Debugger.CorDebug.dll' (Managed): Loaded 'C:\Program Files (x86)\Secret Labs\Netduino SDK\Assemblies\v4.2\le\SecretLabs.NETMF.Hardware.NetduinoPlus.dll', Symbols loaded.
'Microsoft.SPOT.Debugger.CorDebug.dll' (Managed): Loaded 'C:\Users\Me\Documents\NetduinoPlus_LEDblink\NetduinoPlus_LEDblink\bin\Debug\le\NetduinoPlus_LEDblink.exe', Symbols loaded.
The thread '<No Name>' (0x2) has exited with code 0 (0x0).

Samjones, yeah I spotted your info about the network behaviour in your watchdog post http://forums.netdui...vailable-in-42/ but only a while after I posted here. I hadn't tried disabling the internet connection but leaving ethernet connected until yesterday, but it looks like it was a problem before. We have a messy workaround in the form of a timer event that triggers a reset after a period of network inactivity/failures, but it's not nice to be resetting the system every time the network connection drops. Hopefully this will make it into the RC5 fixes. We'll be trying that whenever it's available.

After further investigation, I've discovered another ethernet issue - probably related. If Netduino's internet connection is lost during normal operation but its ethernet connection is still OK, then connection attempts hang but don't seem to cause a total lockup. It does not seem to recover if the internet connection is restored.

I'm connecting the Netduino Plus (firmware 4.2 RC4) to an ethernet switch, and from there to a main router. I can't disconnect the internet/WAN side of the router so I havent tried that. I've tried with DHCP and static IP on the Netduino - same results.

If the Netduino's ethernet cable is plugged in and the switch is connected to the router (ie Netduino has a connection to the internet) then everything is fine.

If Netduino has an ethernet connection to the switch, but no internet access during boot, internet requests time out gracefully after 30 secs. If the internet connection is restored, Netduino discovers the connection after a few seconds and internet activity resumes as expected.

If Netduino has an internet connection at boot, but the internet connection is lost after boot (ie router-switch cable unplugged while application is running), then the next connection attempt does not succeed (obviously) but neither does it time out. It gets stuck at socket.Connect(). The Netduino does not seem to be locked up completely, because my app has a timer event driven LED blink that keeps working.

Unplugging the Netduino ethernet cable in this state immediately triggers a link status update debug message, and the connection attempt immediately fails with an exception. Reconnecting the internet (switch-router cable) and Netduino ethernet cable allows internet connection attempts to succeed.

Aha, this might be the cause of my problems with 4.2RC3 and WinXP. Some time ago I had observed that I could not get ND+ to reliably (if at all) respond. It was fine with 4.1 firmware, and 4.2 worked fine on a Win7/64 machine and a Vista32 laptop. I've since updated the USB drivers on the Win32 PC which helped with other hardware (laggy game controllers) but I never thought to try the ND+... must give it a go again.