Hi, I never used STK600, but from my experience from USBasp this happens when: 1) Clock is set too high. I would give a try to set it via "-B" parameter 2) Low voltage on target. I had some problems with flashing ATtiny13 when running at 3.3V. Changing power supply to 5V helped - this might not be your case, but check it 3) Wrong fuse settings - for example switched to external crystal, but external crystal is not present -> no clock for core -> no reply -> probably not your case 4) Wiring - since you made it work via AVR Studio, it should be OK
Hope it helps Martin po 10. 6. 2019 v 18:09 odesÃlatel Till Sellschopp <[email protected]> napsal: > Hello everyone, > > I have a problem when trying to program the attiny3216 with avrdude using > the stk600 programmer. I could not find any related issues and hope, that > someone in this mailing list might be able to help. > > Firstly: > - The setup (wiring etc.) works with atmel studio. It is possible to read > the device id of the attiny3216. > - I use avrdude from this repository "https://github.com/facchinm/avrdude";. > It is a copy from the main svn. The latest changelog entry is "2018-01-21 > Joerg Wunsch" > - Avrdude compiled without any issues or tailoring. > > I use the following command to connect to the attiny3216 "./avrdude -C > avrdude.conf -c stk600 -p t3216 -v" > > The connection to the stk600 is successful & related information is > printed into the terminal. > It terminates with: > " > avrdude: stk500v2_program_enable(): program enable instruction not defined > for part "ATtiny3216" > avrdude: initialization failed, rc=-1 > Double check connections and try again, or use -F to override > this check. > " > > If -F is used, the following is printed after the stk600 information: > > " > avrdude: stk500v2_program_enable(): program enable instruction not defined > for part "ATtiny3216" > avrdude: initialization failed, rc=-1 > avrdude: AVR device initialized and ready to accept instructions > avrdude: Device signature = 0x1057fe > avrdude: Expected signature for ATtiny3216 is 1E 95 21 > > avrdude done. Thank you. > " > The following observations were made: > > - The device id changes with each call > - The behaviour does not change if the updi line is disconnected > - I could not see any activity on the updi line with a logic analyzer > > I would be very thankful for any hints or ideas. > > Thanks & with best regards, > > Till > _______________________________________________ > AVR-chat mailing list > [email protected] > https://lists.nongnu.org/mailman/listinfo/avr-chat >
_______________________________________________ AVR-chat mailing list [email protected] https://lists.nongnu.org/mailman/listinfo/avr-chat
