what have I done to my USBtiny

[fm2f90x]

Hi there,
I assembled my USBtiny kit and after I didn't get the correct LEDs I discovered I had the 2313 chip backwards. Turned it around and got the green light. I have all the drivers in, and XP sees it with no problems there.
Using AVRdude on an atmega328p I get the rc=-1 error that people seem to get alot, but after the first try, and every try after that I get:

usbtiny errors.jpg (269.63 KiB) Viewed 2823 times

Also, before I hit enter in AVRdude I have the green light, but when AVRdude does its thing the green light goes out for good and the red light comes on steady. I have to unplug the USB cable to get it back to normal.
I've never had my USBtiny working. Do you think I've ruined the 2313?
Here's the pics of my assembled USBtiny:

usbtiny solder.jpg (573.35 KiB) Viewed 2823 times

usbtiny components.jpg (598.09 KiB) Viewed 2823 times

Thanks for your time,
Tom

[mitpatterson]

have you tried any other functions? such as trying to read a chip back? and have you tried programing any other chips?

[fm2f90x]

All I tried to do was read the chip. I haven't tried to write anything yet. It was a 328p with the Arduino bootloader, and the Hello World sketch. (An extra chip. Not mounted on an Arduino, it was on a breadboard.) I then tried hooking up to the 6 pin header on an Arduino board and tried reading that 328p as well (one of my own sketches on that one) but I get the same sort of thing.
I did notice that when I connected to the Arduino board that I lose the outputs and the board seems to go dead, but when I unplug the USBtiny from the Arduino everything works again. Is that normal??
I have some attiny2313s and some attiny85s that I can also try tomorrow. I was thinking of trying the 2313 as I can then follow along exactly with the examples on Adafruit and on the Evil Mad Scientist site.

Tom

[mitpatterson]

yah all the outputs should go dead, its somethat atmel its self says in its own application note: http://www.atmel.com/dyn/resources/prod_documents/doc0943.pdf that all the pins except the SCK, MOSI, MISO, Reset, VCC and gound lines should be set go down, that way nothing interrupts the programming, In addition i found that i had some trouble programming the arudino with it receiving power from the USBTINY, so i connected a 9 volt to the arudino and disconnected the jumper to power the target on the tiny, and it works better for me at least.

[fm2f90x]

So should the Arduino go dead as soon as the USBtiny is plugged in and not operate until it's unplugged, or should it only go dead when it's actually getting programmed (when you hit enter in AVRdude). Mine dies for the whole time the USBtiny is plugged in.

Tom

[adafruit]

dont plug in anything to the usbtiny, then try running avrdude. do you still get USB errors? try going thru a hub OR try not going thru a hub if you are

[fm2f90x]

I plugged into my laptop and installed the drivers and all that good stuff. I tried reading fuses and got the same results. I then tried reading the sketch on the chip (I'm using my Arduino board as the dev. board, and the sketch that's on that chip). Well, it read the sketch and made the .hex file, but then it said the low fuse changed and do I want to change it back to FF. I said yes, then it just sat there and did nothing. The red light stayed on steady so I don't know if it was still "thinkin' about it" but it was taking forever so I unplugged the USB cable. I put it back together and was able to write the low fuse as FF, but then nothing happened with the chip when the sketch should've run. I tried writing the hex file back to the chip, and it started going but when it went back to verify it found an error in the program. I tried to get everything back but it's really hit or miss if the computer talked to the USBtiny or if the USBtiny talked to the chip. It's really inconsistent in the things that it does and I seem to have to unplug the USB cable and the 6 pin header from the board every time I try a new operation.
I'm guessing the 2313 chip that came with the kit is operating correctly? Would you guys say that's the case?? That's the most important thing for me right now as I'm really hoping I didn't screw the 2313 when I put it in backwards. I can work on any other problems from here on without having buy a replacement chip and wait for it to get here to Canada.
I'll try things again on a breadboard and see if I can read sketches and see if I can fix that 328p.

Thanks everyone,
Tom

[fm2f90x]

I'm still getting nowhere. I've tried a Win7 laptop. No matter where I try I can't seem to get anything useful done. Sometimes I can get the rc=-1 error but mostly I get the USB sending control message failed:

Untitled.jpg (154.58 KiB) Viewed 2760 times

This is driving me nuts now. Ideas? Anyone?

Tom

[adafruit]

hmm. well we havent seen this problem before its hard to know if the chip may have been damaged. unfortunately the problem has been evidence of a problem with the USB interface lines. it may be a bad chip

we would suggest seeing if you can try it on another computer just in case
if not, try getting a new chip :/

[fm2f90x]

I've tried it on 3 different computers with the same results. I'm glad you confirmed a possible bad chip. That's progress and I can now stop pulling my hair out trying things out. I'll get a new chip and take it from there.

Thanks for your time,
Tom

[adafruit]

we hope that'll fix it!

[fm2f90x]

Was able to burn your firmware and fuse bits onto a new 2313, replaced the 2313 in the USBtinyisp and tried loading the test_leds.hex onto another 2313. Before I could get my eyes from the computer screen to the red led on the usbtiny it was all over. I don't know how something can be exciting yet anti-climactic at the same time but it worked beautifully. I'm now looking at the sequence of leds lighting up from the test_led program.
Thanks everyone!!

Everybody have a great day!!!
Tom