Netduino home hardware projects downloads community

Jump to content


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.
Photo

USB Device Not Recognized


  • Please log in to reply
14 replies to this topic

#1 ninoq

ninoq

    Member

  • Members
  • PipPip
  • 15 posts

Posted 09 July 2011 - 03:00 AM

I've tried unsuccessfully to install firmware version 4.1.0.6. I've followed the steps posted 14 August 2010 - 12:37 AM by Jason Smith at: http://forums.netdui...b-and-com1com2/ to the letter apart from using later versions of the firmware(4.1.0.6) and Netduino_TinyBooterDecompressor(4.1.0.6). Installing the bootloader with SAM-BA (2.10) seems to be without incident. However when I try to install the firmware with MFDeploy (4.1.2821.0) it hangs - see attached screenshot. When I disconnect and reconnect the Netduino I get "USB Device Not Recognized". Any comments/advice appreciated. PS. I have NETMF 4.1 and Netduino SDK 4.1 installed and OS is Windows XP Home Edition SP3.

Attached Files



#2 Chris Walker

Chris Walker

    Secret Labs Staff

  • Moderators
  • 7767 posts
  • LocationNew York, NY

Posted 09 July 2011 - 03:03 AM

Hi ninoq, Welcome to the Netduino community. Sorry you're having troubles. Let's see if we can get you back up and running. If you hold down the pushbutton on your Netduino while plugging it its USB connection, does it then appear in MFDeploy? Can you immediately ping it? And then redeploy the firmware? Chris

#3 ninoq

ninoq

    Member

  • Members
  • PipPip
  • 15 posts

Posted 09 July 2011 - 03:54 AM

Hi Chris, I did as you suggested. MFDeploy recognzed the Netduino and pinging gave the following message: "Pinging..... TinyBooter BootLoader build info: Netduino by Secret Labs LLC" However when I tried deploying the firmware I got the same result as previously - just 2 signature passes, MFDeploy hanging with a dialog box "Executing Application" and "USB Device Not Recognized" when reconnecting the Netduino.

#4 Chris Walker

Chris Walker

    Secret Labs Staff

  • Moderators
  • 7767 posts
  • LocationNew York, NY

Posted 09 July 2011 - 04:04 AM

Hmm. It looks like the runtime is struggling. You are deploying BOTH ER_ files, correct (including ER_CONFIG)? Can you erase your Netduino completely one more time and try again? What version of firmware did you have before? Chris

#5 ninoq

ninoq

    Member

  • Members
  • PipPip
  • 15 posts

Posted 09 July 2011 - 07:43 AM

Hi Chris, In response to your questions. Yes - I'm deploying both ER_ files. I've erased my Netduino and tried to deploy the firmware again but with no avail. I don't know what version of the firmware I had originally. I purchased my Netduino from SparkFun and it was shipped on or about 24/9/2010.

#6 ninoq

ninoq

    Member

  • Members
  • PipPip
  • 15 posts

Posted 09 July 2011 - 08:23 AM

Hi Chris, Sorry but I forgot that I purchased 2 Netduinos from SF at the time one of which was for a colleague whom I've contacted and who has sent the firmware version of his board. See attached file containing the firmware version and other information.

Attached Files



#7 Chris Walker

Chris Walker

    Secret Labs Staff

  • Moderators
  • 7767 posts
  • LocationNew York, NY

Posted 09 July 2011 - 08:33 AM

Hi ninoq, Okay, could you try one last thing for me? Do you have another computer that you could try the MFDeploy part of the deployment procedure from? Perhaps a Windows Vista or Windows 7 machine? The only reason I can think of that you'd be getting this problem, apart from an OS/driver issue, is if a flash block has gone bad on the Atmel MCU (either exceeded 10,000 rewrites, or defective). Chris

#8 ninoq

ninoq

    Member

  • Members
  • PipPip
  • 15 posts

Posted 09 July 2011 - 12:00 PM

Hi Chris, I may be able to get access to a Vista machine which has no NMF development tools. What is the minimum I'll need to install?

#9 ninoq

ninoq

    Member

  • Members
  • PipPip
  • 15 posts

Posted 10 July 2011 - 03:35 AM

Chris, I've tried on a Windows 7 Pro machine and unfortunately got the same result. I assuming therefore that there is a hardware problem with the MCU. Are there any utilities which can diagnose the problem or at least indicate the nature of it?

#10 Chris Walker

Chris Walker

    Secret Labs Staff

  • Moderators
  • 7767 posts
  • LocationNew York, NY

Posted 10 July 2011 - 03:40 AM

Hi ninoq,

Chris,
Are there any utilities which can diagnose the problem or at least indicate the nature of it?

The best tool to use is SAM-BA. Did you erase the flash on your Netduino before flashing the bootloader?

Where are you located?

Chris

#11 ninoq

ninoq

    Member

  • Members
  • PipPip
  • 15 posts

Posted 10 July 2011 - 06:12 AM

Hi Chris, Before flashing the bootloader, I connected the 3.3V supply to the the small circular conductive pad close to pin 0 for at least 5 seconds which should have erased the flash on my Netduino. I'm located in suburban Sydney NSW Australia.

#12 Chris Walker

Chris Walker

    Secret Labs Staff

  • Moderators
  • 7767 posts
  • LocationNew York, NY

Posted 10 July 2011 - 06:48 AM

ninoq...I just sent you a PM.

#13 chromedome45

chromedome45

    Member

  • Members
  • PipPip
  • 21 posts

Posted 19 March 2013 - 11:42 PM

Having same issue! please help or do I have a bricked Netduino??



#14 Chris Walker

Chris Walker

    Secret Labs Staff

  • Moderators
  • 7767 posts
  • LocationNew York, NY

Posted 20 March 2013 - 12:08 PM

Hi chromedome45, Can you share a bit more info about what you're experiencing? What did you try to do? What step of the reflashing process didn't work for you? Also...were you trying to reflash your Netduino because it was having troubles? Chris

#15 chromedome45

chromedome45

    Member

  • Members
  • PipPip
  • 21 posts

Posted 20 March 2013 - 01:39 PM

Hi Chris,

 

I guess I pushed the wrong button on the SAM-BA app! Then every thing went crazy could not get windows 7 to load the driver. 7 kept saying that the best driver was installed even though it wasn't working at all after a bootloader update failed. I was afraid I bricked it!

 

After the failed attempt to update the bootloader I tried again to get it going. So I reset the Netduino and I tried the Camera driver? which loaded up ok. After which point I was able to get the SAM-BA to recognize it. I then managed to get the bootloader installed. Then exited and was able to get it recognized as a netduino by MFDeploy.exe with the new loader at 4.2.0.0. 

 

I then proceeded to flash the new firmware and it's working like a charm now. BTW mine is an original Netduino 1 with the ARM-7 MCU. 

 

Reason for reflash was errors dealing with mscorlib . The .NET framework was at 4.2 and the netduino was at 4.128 or thereabouts. I now

learned if you update the .NET framework you also need to update firmware. Sometime I'm a little slow to catch on. ;)






0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users

home    hardware    projects    downloads    community    where to buy    contact Copyright © 2016 Wilderness Labs Inc.  |  Legal   |   CC BY-SA
This webpage is licensed under a Creative Commons Attribution-ShareAlike License.