4 replies to this topic

[tr0lle]

Hi there I have some serious problems with my Netduino Plus. I'm running firmware version 4.2.0.1. When I try to debug via VS2010 it just starts to hang with the message "The debugging target is not in an initialized state; rebooting...". I can then detach my Netduino, close VS2010, reattach the Netduino and open VS2010 again, and then it SOMETIMES work - maybe 2/10 times. I've tried to erase the Netduino completely by applying 3V3 to the gold erase pad, and then start from scratch. Same result. I've also tried to downgrade to 4.1.x.x firmware, both the beta version with the OneWire support, but also the official one. It is so buggy, and I'm starting to get really frustrated. I'm using the Netduino for a school project, and I'm actually using more time getting it to work, and actual development. Is the Netduino "bricked"? Or is there someone out there with some tricks up their sleeve? Thanks in advance! Best regards Troels Vest

[Nevyn]

Is the Netduino "bricked"? Or is there someone out there with some tricks up their sleeve?

It's interesting as I am having that problem as well. Hardware setups which previously deployed OK are now failing for me in exactly the manner you describe. I did not have any real problems until I started using the latest builds of the SDK.

Old config:
Netduino PLus and Netduinoi GO!
Cable used is the one I got with the Kindle.
Cable plugged into the laptop through a USB hub.

Now this worked fine for me for a while (i.e. over a year) until the last update I installed - currently 4.2 QFE3 I think.

This morning I have grabbed a new USB cable and plugged it directly into a USB port on the laptop. So far everything I have tried on both the Plus and the GO! works fine.

As an experiment, I have just swapped the Kindle cable for the new one which works on the laptop when connected directly and plugged it into the hub. Deployment on the GO! fails. And as a cross check, I plug the Kindle cable into the laptop directly and deployment works.

Wondering if there might be a driver issue when deploying through a USB hub.


Regards,
Mark

[Chris Walker]

Hi Troels, Mark: Have you tried manually switching the drivers (from WinUSB to MFUSB) when using the latest firmware? http://forums.netdui...-mfusb-drivers/ Chris

[tr0lle]

Hi Troels, Mark:

Have you tried manually switching the drivers (from WinUSB to MFUSB) when using the latest firmware?

http://forums.netdui...-mfusb-drivers/

Chris

Thank you so much Chris! It looks like it worked! I'm now debugging and deploying without any problems, and the problems I had with DHCP also seems to be gone! What a relief. I actually bought a Netduino Plus 2 because I was so desperate, but well - Now I can enjoy two pieces of great hardware.

Looking forward to receiving my Netduino Plus 2

[Teleblaster]

I just bought a netduino plus 2.  The board has 4.2 version of the framework installed, and I'm using 4.2 SDK in visual studio.  I've changed the USB driver to the MFUSB driver.  I'm still getting the '... target is not in initialized state.... message when I use F5 to start debugging. 

 

I tried using MFDeploy to regress the f/w on the board back to NetduinoPlus..fw 4.1.0.6. using these instructions:

I can ping the board in MFDeploy, I get 'Pinging...TinyCLR'   I can browse out and select ER_CONFIG and ER_FLASH, but pressing Deploy brings up a 'Connecting to device' dialog which eventually bangs out to a 'Deployment Status' dialog with this text 'Erasing sector 0x0017e000', and an overlaid dialog saying 'Error:Unable to deploy to device'

 

Do I need to update my bootloader?

 

Thanks in advance

Erich