device signature

[tiloldar]

An unusual problem that has me baffled. I'm playing with "das blinken lights" using a Usbtiny
from one of your kits. While I have had little problem changing code and uploading from within
Arduino using "upload using programmer and a EMSL target board. The problem starts when I
burn fuses from within avrdude. I use fuses from the Engbedded Avr fuse calculator
website. This is the third time this has happened with both Tiny 2313s and Mega 8s.
The most recent was a Mega 8 chip using the fuses -U lfuse:w:0xe1:m -U hfuse:w:0xd9:m.
After I did this I get the error "avrdude: Expected signature for ATMEGA8 is 1E 93 07
Double check chip, or use -F to override this check."
I'm on a Win7 Home premium x64 laptop, have current drivers.
Any help would be great.
Thanks,
Tilo

[adafruit_support_rick]

Low 0xe1, High 0xd9, are the default fuse values for the mega8, so there's nothing wrong with them.
If you're certain that you actually were trying to program a mega8, then the problem is in the connection to the chip. I.e.,

wiring from chip to usbtiny
usbtiny itself
usbtiny to computer

If you have some other known-working board, you can try to narrow down this list of candidates. I'd start with a simple reboot of the computer.

Did you install the 'optional' resistors in the usbtiny (R4,R7)? The assembly tutorial recommends them for use with the SpokePOV, but they can help with noise issues in general.

[tiloldar]

And this is why support is so great. The "optional resistors" would
have been the very last thought I would have had. Yes, they are
the resistors and not the jumpers.
Could that be a problem, maybe I should jumper them?
The board I'm using is the only board I have atm to fit
the M8. I would call it a known working board. I used it many times
to change/update code, checking each time to verify it was
doing what I wanted. The problem happened only/immediately after setting
the fuses.
Also, maybe it helps, I was having problems with "initialization error, rc1"
which was easily solved by unplugging and plugging in the cable.
I'll reboot, install a 168 and program it, I was just not wanting to
lose another chip. Currently have 2 - 2313's and now a M8 bricked.
Thanks for the advice,
Tilo

[adafruit_support_rick]

Jumpering the resistors can't hurt. Try it.

[tiloldar]

I jumped the resistors and it didn't make a difference.
If it helps avrdude is returning the signature as
0x000000. I didn't have any problems burning a
bootloader onto my 168.
Tilo

[adafruit_support_rick]

Are you running 64-bit Win 7? The USBTinyISP tutorial has a link to an alternate 64 bit windows driver:

If you are using 64 bit windows Vista or 7 (or you're just plain having annoying problems with the driver above), try the Windows 7 x64 bit driver. You'll still need to click the button that says "install anyways" when it complains its not verified.

[tiloldar]

Yes it is Win7 64 bit. I installed the correct version using the tutorial.
To make sure I had the correct driver I read the post where I believe it
was first posted by "mightyohm". Then I used "update
driver" to install that driver.

[adafruit]

Can you read the -exact- text on the top of the chip you are programming now, and the -exact- command line you are running? you need to make sure they match up!

[tiloldar]

Atmega8-16PU
avrdude -c usbtiny –p m8 –P usb -U lfuse:w:0xe1:m -U hfuse:w:0xd9:m
is what I used that caused the problem. It has been a couple of weeks
and I'm unwilling at this point to burn any more fuses as I only has
two chips in working order.
I don't think I was clear. I mentioned I was using the EMSL target board,
but I don't have an Arduino board.
I have been using Arduino to load using the "upload using programmer".
I do keep getting a lot of -rc1 connection problems which are corrected
by unplugging and plugging in the usb, both on the board and on the
laptop.
Here is something I hadn't thought of. I have been powering the board
using usb. Since it is way past my bedtime, I'll try some things tomorrow,
including a battery box, and maybe throw together a 12 volt supply and
try to reset some of these using my '168.
G'night and thanks so much for the time,
Tilo

[tiloldar]

O.K.
As my brother loves to say..."and the hits keep coming".
Now I am unable to do anything with my '168.
I tried burning an already compiled program (.hex)
to see if I could breadboard a HVPP to reset the bricked
chips. Now all I get are endless "initialization failed -rc1"
Could that be from the arduino boot-loader?
I'm starting to think I'm not being careful enough with
the chips and frying then with static electricity. I keep
them in the sponge they came with; but install them
bare handed. Maybe it is time to get a chip extractor/installer.
Oh well, I'm done till I can order more chips.
Thanks u2 very much for the help. I appreciate it.
Tilo

[tiloldar]

I'm sorry , I wasn't able to click on, or fill in the fields for an e-mail.
I'm ready to place an order and, due to me messing with the programmer
so much, I was wondering if there was something we could do.
Please contact me.

[tysonedriscoll]

I'm sorry , I wasn't able to click on, or fill in the fields for an e-mail.
I'm ready to place an order and, due to me messing with the programmer
so much, I was wondering if there was something we could do.
Please contact me.

So have you filed a report?

[adafruit_support_rick]

@tiloldar - What are you trying to order? Are you having a problem with the ordering process?

[tiloldar]

No I am not having problems ordering. I was in contact with support
by e-mail, some time ago. I wanted to pick up where we were at ;
but I can't fill in the blanks through the contact us link.
I'll see if I can find the old e-mail and try to reply that way.

[adafruit_support_rick]

Try emailing support@adafruit.com