Invalid Signature on ATTINY2313a-PU

Hello- Im new to everythign arduino so bear with me. I bought an arduino from ebay that didnt come with a bootloader, and so I got a usbtinyisp programmer- which gave me "device initialation failed" and got as far as installing avrdude to check it, which bypassing with -f gives me a device signature of 0x000000.

The chip on the usbtiny is an ATTINY2313a-PU, which the closest known part seems to be a ATTINY2313a- but I cant get past the invalid device signature. I dont know how to bypass this check in the arduino IDE, and maybe I shouldnt- I dont suppose theres another issue Im not seeing?

A signature with only 0's or F's means that you have a connection problem. The chip is incorrectly connected to your programmer.

// Per.

I find that hard to believe considering this is a factory made programmer :confused:

This is the unit I bought

From what I'm seeing in the arduino IDE and avrdude, it supports attiny2313, but this is an attiny2313A-PU so maybe theres some different settings or something? I know nothing about all the internal fuses and oscillations etc, Im only starting to see these things popping up as potential reasdons why I might be getting this "signature" error. The device itself does initialize though, so doeskin that mean its working but not "trusted"?

Wait, are you trying to program the 2313, or use it to program something else?

I bought an Arduino UNO R3 (not the real one, so no bootloader on it) and i bought the USBTinyISP to program it, but the programmer itself is giving me that device signature error -.- I honestly have no idea what the issue is, the chip on it is again, an ATTINY2313A-PU which isnt in the list for avrdude, so Im trying to get any information I can on it. I cant even get the chip to read out any information- how do you first see what the problem even is so you can fix it :o

You are NOT programming the 2313 you are programming the arduino chip (usually an atmega328p). The invalid signature is for the chip connected to the usbtiny programmer cable, NOT the chip ON the programmer. Connect the cable to the 6 pin ISP/ICSP header on the arduino board.

If you can run avrdude from the command line the following should read the chip signature.

avrdude -cusbtiny -Pusb -pm328p

If you are on windows usb may need to be USB.

I must have been confused as to how this works then- When I plugged in the programmer to the arduino, and went to burn bootloader in the arduino IDE i got a "usb not recognized" After manually installing tinyusb drivers, I got as far as the "failed to initialize" error. and checking the tinyusb with the part on the programmer (with only the tinyusb plugged in) then I get the wrong signature.

Whats confusing is that every video tutorial out there shows plugging in the programmer into the arduino and just clicking "burn bootloader" and magically it works. But mine doesnt- How then can I tell if its the programmer or the arduino? And where do I go from there? There isnt much instructions on how to trouble shoot this without extensive knowledge in AVRdude, programming fuses, setting oscillators etc

Whats the next step o-O

I typed in that command you said, still nothing. I printed out with verbose- maybe theres something obvious here? The cables are connected properly

A lot of what im reading today is saying that the fuses/ osciallators might be set wrong. How can I check/ program these fuses properly?

When connected to the usbtiny. Is the Arduino powered up, is the power led lit?

There is usually a jumper on the usbtiny to select power to the arduino. Is it in place? DO NOT get confused and power the arduino from two sources, this can end badly.

The red stripe on the cable should be on the same side of the ISP header as pin one. Pin one is usually marked on the board, it may be just a dot. Pin one on the cable end may be marked by a small triangle. Pin one on the cable end is to the left of the key, if the plug has a key.

With the usbtiny disconnected does the arduino power up when connected to the computer with a USB cable? It's possible that the board is defective.

The jumper from the programmer is removed- The arduino is powered through USB only and the LED's are all on

The header is tested (continuity on all 6 cables) and connected correctly

The arduino itself is recognized on com port 4 in arduino IDE and the LED's are all on

Ive tried both having the programmer plugged in and the arduino not plugged in to USB (powered through jumper) AND with the programmer jumper out and both unit plugged in through USB

In every scenario the green led on the programmer (bottom of header) is lit, the red "On" and green "L" led's are lit solid on the Arduino.

As soon as I type in this command: "avrdude -c usbtiny -P usb -p m328p" I see the green "L" LED on the arduino blink off once, and the red led on the bottom of the programmer header blinks on once at the same time. With -F and high verbosity I get this read out- again, from what I'm reading its possible a fuse is set to use internal/external oscillator? I dont know how to read this or what other error might be obvious, but heres a link to the readout from avrdude:

Try adding -B100 to the command line. If no joy consider a new AVR or a new board, with a bootloader.
If you want more guesswork post a link to the board you have.

Still no luck with any of those settings- It still says signature = 0x000000

The listings for the units I bought are gone, but I took a photo of both of them connected. The programmer is an attiny2313a-pu and the arduino is a regular 328p

Heres a picture, all the component values should be visible Screenshot - 40ff01f4543ac3c3090b88542fd46a32 - Gyazo

What am I looking for? Fuse settings? Crystal/Oscillator settings? I posted a AVRDUDE readout in an earlier post but I have no idea what all that information even means :\

In addition, the -v spits out that "programmer operation is not supported" but I have the correct drivers... Not sure where to go from here -.-

Im ordering a new set of arduinos and programmers- From what I've read, it should be working following the steps Ive done so far, hopefully that will at least help me know if its just a defective board or not. Thanks for your input guys!