0

After programming Arduino Nano with the DIY Headtracker code, after trying to plug the Arduino to the receiver and some time, the LED stops flashing and now it's not recognized by the computer anymore.

When I plug it, it only lights the power LED.

The worst thing is that I've already tried with another Nano and it bricked also, can't use them any more. Anyone know any fix to this?

This is the error given when trying to upload the blink sketch to the board...

avrdude: stk500_recv(): programmer is not responding
avrdude: stk500_getsync() attempt 1 of 10: not in sync: resp=0xb8
avrdude: stk500_recv(): programmer is not responding
avrdude: stk500_getsync() attempt 2 of 10: not in sync: resp=0xb8
avrdude: stk500_recv(): programmer is not responding
Nick Gammon
  • 38,901
  • 13
  • 69
  • 125
peter97silva
  • 1
  • 1
  • 1

3 Answers3

1

I suggest you visit the page Have I bricked my Arduino Uno? - whilst you have a Nano and not a Uno, it is the same processor and most of the remarks there will apply.

As the Arduino Nano page says:

It has more or less the same functionality of the Arduino Duemilanove, but in a different package.

If you have another Uno or similar lying around you could conduct the "chip detector" test described on that page. You could also perform the loopback test.

It is possible on the FTDI chip (underneath) is damaged in which case there would be alternatives to using that.

Nick Gammon
  • 38,901
  • 13
  • 69
  • 125
0

If you have access to an AVR ICE MKII or an AVRDragon, you could try High Voltage programming. It is, AFAIK, the ultimate way to revive a bricked device. There might be some alternative method to perform HV programming without any of the devices I mentioned (for example with another AVR), but I'm not aware of it, if it exists.

Igor Stoppa
  • 2,125
  • 1
  • 15
  • 20
0

https://www.sparkfun.com/news/1629 Maybe your windows update has installed new drivers for your FTDI chip. You can check that your usb device PID is set to 0x0000

(You probably have the "Gravitech Nano V3.0" (with FTDI chip on the back)? I have, and this worked for me.)

In this case, you should download M_PROG from FTDI And then check for the chip, when found, you set the PID to FTDI default (0x6001). Then simply press program, and it will re-set your device PID.

Also, you should download the "CDM-v2.12.00-WHQL-Certified.zip" drivers. Another source

aaa
  • 2,715
  • 2
  • 25
  • 40