Did I kill it? AVRDude, SmartieParts, Death! -- RESOLVED

Cant get your radio to work? General Hardware issues?
Post Reply
drivintin
Posts: 3
Joined: Wed May 30, 2012 3:49 am
Country: -

Did I kill it? AVRDude, SmartieParts, Death! -- RESOLVED

Post by drivintin »

Ok guys, I think it is dead, but would love some ideas.

FlySky v2 board. SmartieParts v2.1

I have had this around 6-8months. Honestly it has been in the garage unused for a couple of months. Anyways I break it out and do an upgrade, then reupload the data and realize the formatting has changed some, so flash it again and let it just format. Well I keep getting the verification failure, try like 5 different roms, and get one to take. Then I change again and it never comes back up. Of course I read now that you shouldn't flash that often, that fast. It reads the fuses ok, then I try to modify them and bang, it never comes back. Now I just get:

Code: Select all

=================================================================================
Started AVRDUDE
/usr/local/bin/avrdude -c usbasp -p m64 -P usb -u -U lfuse:w:0x0E:m -U hfuse:w:0x89:m -U efuse:w:0xFF:m
=================================================================================

avrdude: error: programm enable: target doesn't answer. 1 
avrdude: AVR device initialized and ready to accept instructions

Reading | ################################################## | 100% 0.01s

avrdude: Device signature = 0x000000
avrdude: Yikes!  Invalid device signature.
         Double check connections and try again, or use -F to override
         this check.


avrdude done.  Thank you.


=================================================================================
AVRDUDE done - exit code 1
So now I can't reset the fuses, or upload firmware or anything. So side note, incase it makes a difference. The SmartieParts board has never powered my radio enough to do the flash. I have always had to have a battery in, and turned it on to get it to flash. So now the screen is blank and never comes back up. I used this pic Image, and I have power at all the points (with battery).

Any ideas? I am thinking of ordering an Oscillator and see if I can flash with that. Only thing I can think of.
Last edited by drivintin on Mon Jun 04, 2012 5:39 pm, edited 1 time in total.

User avatar
MikeB
9x Developer
Posts: 17993
Joined: Tue Dec 27, 2011 1:24 pm
Country: -
Location: Poole, Dorset, UK

Re: Did I kill it? AVRDude, SmartieParts, Death! :)

Post by MikeB »

If using the Smartieparts board, and it has been in the garage for some time, it might be worth removing the SP board, cleaning all the connection pads and then replaceing the SP board.

Mike.
erskyTx/er9x developer
The difficult we do immediately,
The impossible takes a little longer!
drivintin
Posts: 3
Joined: Wed May 30, 2012 3:49 am
Country: -

Re: Did I kill it? AVRDude, SmartieParts, Death! :)

Post by drivintin »

Sorry, looking back at the post, I didn't make things very clear.

The board and contact points were cleaned.

The fuses were reset based off a post I found, and sadly I didn't keep those numbers, so thinking maybe they were wrong. Now basically waiting for an oscillator to come in the mail. Anyone know the range on the oscillator that you can use? I ordered the 1mhz, and sadly the lowest I could find around the house was 14mhz, was thinking it needed to be 8mhz or below.

Thanks guys
drivintin
Posts: 3
Joined: Wed May 30, 2012 3:49 am
Country: -

Re: Did I kill it? AVRDude, SmartieParts, Death! :)

Post by drivintin »

TADA!

Haha, I can't believe it, but I was actually able to bring it back to life with the oscillator!

I sodered the clock lead in (which was EXTREMELY small) with my horrible sodering skills. Then I actually sodered the power leads to the smartieparts board since it had nice fat places I could soder.

The first reset failed and said it couldn't find the device again. Tried another machine through a powered hub and the fuse reset still failed. Then I did a firmware flash with the force and -B 100 to slow it down. It actually wrote the firmware and verfied correctly much to my surprise. But the screen didn't come on, so I was scared more was wrong with the unit. So I tried the fuse reset one more time:

Code: Select all

=================================================================================
Started AVRDUDE
C:/Program Files (x86)/eePe/avrdude.exe -c usbasp -p m64 -F -B 100 -P usb -u -U lfuse:w:0x0E:m -U hfuse:w:0x89:m -U efuse:w:0xFF:m
=================================================================================

avrdude.exe: set SCK frequency to 8000 Hz
avrdude.exe: AVR device initialized and ready to accept instructions

Reading | ################################################## | 100% 0.02s

avrdude.exe: Device signature = 0x1e9602
avrdude.exe: reading input file "0x0E"
avrdude.exe: writing lfuse (1 bytes):

Writing | ################################################## | 100% 0.02s

avrdude.exe: 1 bytes of lfuse written
avrdude.exe: verifying lfuse memory against 0x0E:
avrdude.exe: load data lfuse data from input file 0x0E:
avrdude.exe: input file 0x0E contains 1 bytes
avrdude.exe: reading on-chip lfuse data:

Reading | ################################################## | 100% 0.00s

avrdude.exe: verifying ...
avrdude.exe: 1 bytes of lfuse verified
avrdude.exe: reading input file "0x89"
avrdude.exe: writing hfuse (1 bytes):

Writing | ################################################## | 100% 0.02s

avrdude.exe: 1 bytes of hfuse written
avrdude.exe: verifying hfuse memory against 0x89:
avrdude.exe: load data hfuse data from input file 0x89:
avrdude.exe: input file 0x89 contains 1 bytes
avrdude.exe: reading on-chip hfuse data:

Reading | ################################################## | 100% 0.00s

avrdude.exe: verifying ...
avrdude.exe: 1 bytes of hfuse verified
avrdude.exe: reading input file "0xFF"
avrdude.exe: writing efuse (1 bytes):

Writing | ################################################## | 100% 0.02s

avrdude.exe: 1 bytes of efuse written
avrdude.exe: verifying efuse memory against 0xFF:
avrdude.exe: load data efuse data from input file 0xFF:
avrdude.exe: input file 0xFF contains 1 bytes
avrdude.exe: reading on-chip efuse data:

Reading | ################################################## | 100% 0.01s

avrdude.exe: verifying ...
avrdude.exe: 1 bytes of efuse verified

avrdude.exe done.  Thank you.


=================================================================================
AVRDUDE done - SUCCESSFUL
=================================================================================
Obviously I was thrilled!

I will say I actually wrote the firmware with the oscillator still attached. Mostly because I was under the impression that it was either wired wrong, or else it wasn't working at all.

I want to really thank the guys who found this stuff out, and made the fuse brick pdf. The $5 spent on getting the oscillator saved me from having to buy another radio!

Post Reply

Return to “Hardware”