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

:( Bricked Netduino :(


  • Please log in to reply
6 replies to this topic

#1 ULight.Me

ULight.Me

    Member

  • Members
  • PipPip
  • 12 posts
  • LocationMilton, Ontario

Posted 08 June 2011 - 03:52 PM

I've followed a few other "bricked" threads but no success. Current status: 1. Nothing is attached. 2. When powered up Both LEDs stay on all the time (blue and white) my Windows 7 reports the device as "Unknown" 3. I've held down the SW1 while attaching USB, results in "Unknown Device" This started happening when I connected the reset pad with 3.3V jumper cable, while plugged into USB. I was following the "Firmware Upgrade" wiki article. any ideas?

#2 Dan Morphis

Dan Morphis

    Advanced Member

  • Members
  • PipPipPip
  • 188 posts

Posted 08 June 2011 - 05:16 PM

I've followed a few other "bricked" threads but no success.

Current status:

1. Nothing is attached.
2. When powered up Both LEDs stay on all the time (blue and white) my Windows 7 reports the device as "Unknown"
3. I've held down the SW1 while attaching USB, results in "Unknown Device"

This started happening when I connected the reset pad with 3.3V jumper cable, while plugged into USB. I was following the "Firmware Upgrade" wiki article.

any ideas?


Which wiki article did you follow? Since you mentioned touching the pad with the 3.3v jumper I'm going to presume you followed "Installing the TinyBooterDecompressor step by step."

Have you run the Atmel SAM-BA programmer? You will need to manually specify the COM port (You will have to look in the device manager and find the virtual COM port which corresponds to your Netduino).

After you have the new TinyBooter installed, you can then follow the Flashing new firmware step-by-step article and that should have you back up and running.

-dan

#3 ULight.Me

ULight.Me

    Member

  • Members
  • PipPip
  • 12 posts
  • LocationMilton, Ontario

Posted 08 June 2011 - 07:03 PM

Which wiki article did you follow? Since you mentioned touching the pad with the 3.3v jumper I'm going to presume you followed "Installing the TinyBooterDecompressor step by step."

It was the Tiny Booter Decompressor article.

Have you run the Atmel SAM-BA programmer? You will need to manually specify the COM port (You will have to look in the device manager and find the virtual COM port which corresponds to your Netduino).

I did run the SAM-BA but by that time my Netduino was already gone to "Unknown device" state in DM and has no COM ports associated with it. When I try to install the Netduino driver on the "Unknown device" that my Netduino is in DM I get error code 10 "This device cannot start". I should mention that I'm connecting the device to my usb port by holding down the sw1 switch. I've tried without the switch and I get "Unknown device" and no com ports to choose for the SAM-BA.

After you have the new TinyBooter installed, you can then follow the Flashing new firmware step-by-step article and that should have you back up and running.

-dan


I wish :)

#4 ULight.Me

ULight.Me

    Member

  • Members
  • PipPip
  • 12 posts
  • LocationMilton, Ontario

Posted 08 June 2011 - 07:38 PM

SUCCESS :) I was actually able to UNBRICK my Netduino. It turned out that the issues were being caused by my OS. Atmel doesn't have 64Bit drivers and as soon as I followed the procedure on an windows XP 32bit I was able to connect to the device using SAM-BA and flash the TinyBooterDecompressor.bin to it. After that it was smooth sailing back on my Windows 7 64bit machine where I was able to flash the new Firmware using .NET Micro Framework Deployment Tool :) everyone can rest easy now ;) we are back in business. Thank you Dan.

#5 Dan Morphis

Dan Morphis

    Advanced Member

  • Members
  • PipPipPip
  • 188 posts

Posted 08 June 2011 - 10:16 PM

SUCCESS :)

I was actually able to UNBRICK my Netduino.

It turned out that the issues were being caused by my OS. Atmel doesn't have 64Bit drivers and as soon as I followed the procedure on an windows XP 32bit I was able to connect to the device using SAM-BA and flash the TinyBooterDecompressor.bin to it.

After that it was smooth sailing back on my Windows 7 64bit machine where I was able to flash the new Firmware using .NET Micro Framework Deployment Tool :)

everyone can rest easy now ;) we are back in business.

Thank you Dan.



I and others on here use x64 so I'm not sure why you had issues. I just checked the release notes for 2.10 and they say 64 bit is supported and tested...

I'm glad you got it working again!

-dan

#6 Eric Burdo

Eric Burdo

    Advanced Member

  • Members
  • PipPipPip
  • 130 posts

Posted 08 June 2011 - 10:21 PM

I and others on here use x64 so I'm not sure why you had issues. I just checked the release notes for 2.10 and they say 64 bit is supported and tested...

I'm glad you got it working again!

-dan



I have Win7 x64 - had to use a Win7 x32 machine to make it work. Couldn't get the x64 version of SAM-BA to work (unknown as to why).
~ Eric D. Burdo ~ http://brick-labs.com/

Today LED's, tomorrow, the world!!! Well, OK, maybe servos.

#7 Stefan

Stefan

    Moderator

  • Members
  • PipPipPip
  • 1965 posts
  • LocationBreda, the Netherlands

Posted 08 June 2011 - 11:10 PM

Strange, I did it on Windows 7 x64 earlier today with success. but then again, it's solved. Glad to hear that!
"Fact that I'm a moderator doesn't make me an expert in things." Stefan, the eternal newb!
My .NETMF projects: .NETMF Toolbox / Gadgeteer Light / Some PCB designs




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.