Attiny Baremetal AVRdude Problems

Hello,
I'm currently trying to get the ATtiny85 running baremetal.

I don't have a ISP programmer so I use the Arduino UNO R3 for that, with a reset to ground capacitor.
I uploaded the Arduino ISP example and put the programmer to Arduino ans ISP(not Arduino an ISP(Atmega32U4)).
So I use AVRdude for controlling my ATtiny85 I firstly upload the check if everything works.

avrdude -c stk500v1 -p t85 -P /dev/ttyACM0 -b 19200

The error I'm getting is.

avrdude -c stk500v1 -p t85 -P /dev/ttyACM0 -b 19200
Device signature = 00 00 00 (retrying)
Device signature = 00 00 00 (retrying)
Device signature = 00 00 00
Error: invalid device signature
Error: expected signature for ATtiny85 is 1E 93 0B
  - double check connections and try again, or use -F to carry on regardless

Avrdude done.  Thank you.

~

Using -F like in the error suggests to use doesn't work either.
When I'm asking AI it says I should check my wiring, but everything was connected correctly.
My wiring is.

Arduino Pins ATtiny85 Pins
Pin 13 7
Pin 12 6
Pin 11 5
Pin 10 1 (RESET)

My knowledge fore baremetal Programming comes mostly from the Mitch david attiny/baremetal programming videos.
https://www.youtube.com/@MitchDavis2/videos#
and if it helps anyone I'm using Linux.

Thanks for every helping person.

Linux here as well. Loaded ArduinoISP sketch. Wiring as shown:

Results:

me@home:~/Documents/projects/ATtiny85 $ avrdude -Cavrdude.conf -c stk500v1 -p t85 -P /dev/ttyACM0 -b 19200

avrdude: AVR device initialized and ready to accept instructions

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

avrdude: Device signature = 0x1e930b (probably t85)

avrdude: safemode: Fuses OK (E:FF, H:D7, L:E2)

avrdude done.  Thank you.

me@home:~/Documents/projects/ATtiny85 $ 

Conclusion: hate to say it, but check your wiring.

I will try to do it like in the picture.(mine was a bit messy).
I am using a 100uf capacitor does that also work, or is a 10uf capacitor the best to work with?

I don't know if it makes any difference, but when AVRDudess calls AVRDude to read the fuses of an ATTiny85, it uses "arduino_as_isp" instead of "stk500v1" as the programmer.

The typical reset capacitor is 10uF, but I don't know if it matters if a greater value is used.

I redid the wiring and when I uploaded the command It only sais
"AVRdude done. Thank you."

❯ avrdude -c arduino_as_isp -p t85 -P /dev/ttyACM0 -b 19200

Avrdude done.  Thank you.

~

What does that mean, is it an error?

Hi @SchrankHund. The "Avrdude done. Thank you." message is not an error. This is only the message that AVRUDE displays to indicate the process has ended.

Unfortunately this message is displayed even when something goes wrong (even though it gives me the impression of a positive outcome), so its presence is not an indication of success. However, the absence of any error message does indicate that no error occurred. Congratulations!

You can get more feedback on what AVRDUDE is doing by adding the --verbose flag to the command:

https://avrdudes.github.io/avrdude/8.1/avrdude_4.html#Option-Descriptions:~:text=bootloader%20to%20work.-,-v,---verbose

-v
--verbose

Enable verbose output. More -v options increase verbosity level.

I guess you are already aware, and are only running this command as a basic check on AVRDUDE's ability to communicate with the target:

However, just to be sure I'll mention that the command you shared doesn't actually perform an upload. You will need to add the appropriate --memory flag (AKA -U) to the command to do that:

https://avrdudes.github.io/avrdude/8.1/avrdude_4.html#Option-Descriptions:~:text=U%20memory%20operations.-,-U,-memory%3Aop

@ptillisch, as far as AVRdude is concerned, is stk500v1 the same as arduino_as_isp for the specified programmer?

Edit: Probably answering my own question, Perplexity says:

Both implement the STK500 v1 protocol, so they often work interchangeably for basic tasks like reading device signatures—Arduino as ISP emulates STK500 v1 behavior. However, avrdude treats them as separate types with tailored command handling (e.g., "arduino_as_isp" avoids raw SPI commands that bootloaders may not fully support).

For me both works fine.