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.
Just received my shiny new Netuduino 2 Plus, to replace a Netduino Plus that seems to have died. When I plug the new board in, I get "The USB device you installed has malfunctioned, and Windows does not recognize it." After trying a couple times, Windows 8 showed me it still has a Blue Screen Of Death ("Unexpected kernel trap error").
Okay, try Windows 7. Same error, but no BSOD. MFDeploy saw the board, but wouldn't show Device Capabilities or ping it, so the simplest solution seemed to be erasing and reflashing the firmware. That seemed super easy. MFDeploy now reports the firmware 4.2.2.2, but Visual Studio 2010 reports an error, 'Could not read state file "objDebugTinyCLR_DebugReferences.cache". Object must implement IConvertible.'
Checking again, MFDeploy now reports "Error--no response from device" when I try to ping it.
At this point, I'm not sure what to try next. I'm hoping I just missed something--I had flashed the old Netduino Plus to 4.2, so I have the 4.2.2 SDK and 4.2 .NET Micro Framework installed.
Any ideas? Well, I suppose that should be any ideas other than an RMA?
sjcook779, timovayrynen: what are you typing, exactly, at the command line to compile the firmware? It looks like something is missing in your setup, somehow, somewhere.
mcdonnej: we test every Netduino before it leaves Secret Labs, but it's always possible that it got damaged in transit somehow. The more likely situation, however, is that there's a driver issue of some sort on your computer. Netduino Plus 2 uses the legacy MFUSB drivers instead of the newer WinUSB drivers. Before going too far down this path, would you mind erasing your Netduino Plus 2 and reflashing it with the 4.3 beta 1 firmware--and seeing if you can ping that from MFDeploy?
Chris
I posted on another thread talking about this erase and flash procedure for the N+2, but im gonna put it here too, as this is where the instructions are.
Basically i could no longer deploy to my N+2, so i followed the erase/flash instructions using DFU Tester and DfuSe Demo. The Tester erased just fine, but after Choosing the file for Rewriting the firmware, the upgrade button remains greyed out...
Did i miss something? Or does anyone know how i can flash the firmware?
Flashing with 4.3 beta 1 went smoothly, and the first time I started debugging, the program deployed without incident from Visual C# 2012. (Silly side question--how is the onboard LED now declared? Haven't looked for it since 4.1.)
The second time I deploy, Visual Studio gives "There were deployment errors--continue?" The output window shows "cannot attach debugger engine." After answering, "No," the error list shows "unable to connect to device." Curious, I ran MFDeploy, it says there is "No debugger!" found, and "Cannot find any entrypoint," although the other Device Capabilities info seems to all say 4.3.0.0 (beta 1). The program I initially deployed is identified by name in MFDeploy. The IP address of the device shows as 0.0.0.0 in MFDeploy, if that matters.
I erased and re-flashed with 4.3 beta 1 to verify it wasn't a one-time event. Same results. As I recall, this is the same thing that happened with 4.2--it seemed to work the first time from Visual C# 2010, but didn't after that.
I'm hoping the answer is, "Oh, based on those symptoms, it looks like you forgot to do X," but I'm worried the answer is, "That's not supposed to be possible."
Update- I was able to flash with the DFU file, and execute simple programs. I still have not been able to set the MAC address with the same symptom that I posted in the previous message's screengrab.
Update- I was able to flash with the DFU file, and execute simple programs. I still have not been able to set the MAC address with the same symptom that I posted in the previous message's screengrab.
Any suggestions?
Thanks
Have you ever installed the v4.3 framework ? - Because im getting thet error if im using the tool from 4.3 to set mac adresse on a board with 4.2. Use the tool from 4.2 to set the mac address and it should work
That may be the problem. When I look in the Framework folders, I see the different versions of the frameworks, each with a tools folder, but the only one with the tool present is 4.3. I originally installed 4.3 because I use Visual Studio 2012 Pro and I want to work in VB. The tools documentation for the Netduino 2 Plus say you must use C# Express 2010. If I try to install the Framework 4.2 it refuses as I do not have Visual Studio 2010.
Version 4.3 is rated a "stable" version at codeplex, so I do not understand why I would have to use the tool for 4.2.
When will you release this particular version of the code? The one available for download is 4.2.2.1 which compiles on QFE1, and it's quite old... 4.3 would we way better (so I wouldn't have to deal with VS2010), but I realize you only release stable versions...
Hi Chris. This is still version 4.2. Not sure how to set the MAC via software as it seems read only unless I am using the wrong method.
I did some more testing and it seems to throw the error when any of the Network settings have been altered. If you are using the defaults on the board it allows setting of the MAC via MFDeploy. Once I update the network settings via software they do stick however the MAC seems to be intermittently resetting and not sure what is causing it but if I go in to fix it via MFDeploy you can't change and save it. I have to wipe the board in order to set the MAC.
This firmware also includes the previous updates:
1. Bug fix: SPI clock 'idle high' setting now supported
2. Netduino Plus 1 projects can be upgraded without changing HardwareProvider
3. Now compatible with legacy SecretLabs AnalogInput and PWM classes
4. Bug fix: SPI chip select timing corrected
5. Bug fix: PWM frequency corrected
6. New: more reliable rebooting during deployment
7. Static IP now works (in addition to DHCP default)
8. MAC Addresses are now loaded by TinyCLR
9. Additional I2C bug fix--pins now forced into proper configuration
To find the current version of your Netduino firmware:
1. Go to the Start Menu > Programs > Microsoft .NET Micro Framework 4.2 > Tools
2. Run MFDeploy.exe. Be careful to run MFDeploy.exe and not MFDeploy.exe.config (as file extensions are hidden by default)
3. Plug your Netduino into your PC using a Micro USB cable.
4. In the Device section at top, select USB instead of Serial. Your Netduino should appear in the drop-down; if not, select it.
5. Select the Target menu, Device Capabilities option.
6. In the output box, find the "SolutionReleaseInfo.solutionVersion" value. This is your firmware version.
To flash this firmware:
1. Detach your Netduino
2. Press and hold your Netduino's pushbutton while plugging it in via USB; this will put it in bootloader mode.
3. Erase the firmware on your Netduino using the STDFU Tester v3.0.1 application
> a. Select the "Protocol" tab
> b. Press the "Create from Map" button
> c. Select the "Erase" radio button option
> d. Press the "Go" button
> e. Wait for erase process to complete
4. Flash the attached .DFU file using the ST DfuSe Demonstrator v3.0.2 application (included with STDFU Tester)
> a. Locate the "Upgrade or Verify Action" pane (bottom-right pane)
> b. Press "Choose..." and select the attached DFU file
> c. Check the "Verify after download" option
> d. Press "Upgrade". It will take a few minutes to update your Netduino.
> e. Detach and reattach your Netduino (power cycle) or press "Leave DFU mode"
After flashing, to set your network settings using MFDeploy:
1. Select the Target > Configuration > Networking menu. Re-enter your IP address settings and MAC address.
Enjoy, and please let us know if you run into any troubles.
Chris
trying tp flash my netduino plus 2 but these instructions do not work?
My device does not show in the visual studio device dropdown, so I think I need to flash it?
If your board doesn't appear in Visual Studio, here are the likely causes: 1. Your board is in bootloader mode (blue LED will be on) 2. Drivers are not installed properly 3. Your board is not yet flashed (blue LED will be on) 4. Computer requires reboot (i.e. USB port is temporarily disabled) 5. Netduino is not plugged into computer (just throwing this in for completeness).
What does your board show up as in Device Manager, when you plug it in?
I have had no problems with Win8 or 8.1. Check you driver version, and see how it shows up in Device Manager. Sometimes NETMF devices will show up as something not properly identified. Trying connecting and disconnecting to see if something appears/disappears. Then see how it is identified.
Installng .NET MF 4.1 or 4.2 does not work, says it needs VS2010, I'm using VS2012 PRO?
Currently have MF v4.3 installed?
This whole .NET MF & Netduino seems to be a real mess Still!
I'm a professional developer with 20 years windows dev experience, and been doing .net since it's beta, and I think this is way overcomplicated to get an enviroment set-up...
I have a Windows 7 laptop (VS2013 Pro,), and a Windows 8 laptop (VS2013 Pro, VS2012 Pro)
Netduino Plus 2 Rev.A
What would be the best framework, dev tools, ect. to use?
This firmware also includes the previous updates:
1. Bug fix: SPI clock 'idle high' setting now supported
2. Netduino Plus 1 projects can be upgraded without changing HardwareProvider
3. Now compatible with legacy SecretLabs AnalogInput and PWM classes
4. Bug fix: SPI chip select timing corrected
5. Bug fix: PWM frequency corrected
6. New: more reliable rebooting during deployment
7. Static IP now works (in addition to DHCP default)
8. MAC Addresses are now loaded by TinyCLR
9. Additional I2C bug fix--pins now forced into proper configuration
To find the current version of your Netduino firmware:
1. Go to the Start Menu > Programs > Microsoft .NET Micro Framework 4.2 > Tools
2. Run MFDeploy.exe. Be careful to run MFDeploy.exe and not MFDeploy.exe.config (as file extensions are hidden by default)
3. Plug your Netduino into your PC using a Micro USB cable.
4. In the Device section at top, select USB instead of Serial. Your Netduino should appear in the drop-down; if not, select it.
5. Select the Target menu, Device Capabilities option.
6. In the output box, find the "SolutionReleaseInfo.solutionVersion" value. This is your firmware version.
To flash this firmware:
1. Detach your Netduino
2. Press and hold your Netduino's pushbutton while plugging it in via USB; this will put it in bootloader mode.
3. Erase the firmware on your Netduino using the STDFU Tester v3.0.1 application
> a. Select the "Protocol" tab
> b. Press the "Create from Map" button
> c. Select the "Erase" radio button option
> d. Press the "Go" button
> e. Wait for erase process to complete
4. Flash the attached .DFU file using the ST DfuSe Demonstrator v3.0.2 application (included with STDFU Tester)
> a. Locate the "Upgrade or Verify Action" pane (bottom-right pane)
> b. Press "Choose..." and select the attached DFU file
> c. Check the "Verify after download" option
> d. Press "Upgrade". It will take a few minutes to update your Netduino.
> e. Detach and reattach your Netduino (power cycle) or press "Leave DFU mode"
After flashing, to set your network settings using MFDeploy:
1. Select the Target > Configuration > Networking menu. Re-enter your IP address settings and MAC address.
Enjoy, and please let us know if you run into any troubles.
Chris
I've done everything listed here and the netduino plus 2 still does not work. Both led's are on at all times
Most users create apps using Visual Studio 2010 and the 4.1 SDK.
You can also upgrade to the 4.3 SDK (for use with VS2012...or via VS2013 with the experimental build). That works well for most people--but there are a few debugger bugs that are getting ironed out before it becomes the officially recommended version.