Sorry to be following up on this so late; I just joined the list and saw this
thread in the archive:
Joakim Lubeck Tue, 29 Jan 2013 03:48:18 -0800 wrote
> I don't know if this is urgent, but the relatively new ATtiny1634 is starting
> to be quite popular and I guess many would want it supported by avrdude.
I’d like to second that request!
> I attach a config entry for it that have evolved at avrfreaks. Since I don't
> know about all details in the .conf file, I'm not sure it's correct in all
> places.
> I have confirmed that it works when writing FLASH, FUSES, EEPROM over ISP
> (stk500 and usbasp).
Same here.
> I have not tested HVPP.
I’m nearly 100% sure the entry as written is incorrect:
> pp_controlstack =
> 0x0E, 0x1E, 0x0F, 0x1F, 0x2E, 0x3E, 0x2F, 0x3F,
> 0x4E, 0x5E, 0x4F, 0x5F, 0x6E, 0x7E, 0x6F, 0x7F,
> 0x66, 0x76, 0x67, 0x77, 0x6A, 0x7A, 0x6B, 0x7B,
> 0xBE, 0xFD, 0x00, 0x01, 0x00, 0x00, 0x00, 0x00;
As far as I know, no other 20 pin ATtinys have bit 0 in any of their first 24
control stack entries set, so odds are this one won’t, either.
The HVPP documentation, to me, looks indistinguishable from an attiny4313, so
that entry may be a good starting point:
pp_controlstack =
0x0E, 0x1E, 0x0E, 0x1E, 0x2E, 0x3E, 0x2E, 0x3E,
0x4E, 0x5E, 0x4E, 0x5E, 0x6E, 0x7E, 0x6E, 0x7E,
0x26, 0x36, 0x66, 0x76, 0x2A, 0x3A, 0x6A, 0x7A,
0x2E, 0xFD, 0x00, 0x01, 0x00, 0x00, 0x00, 0x00;
I wish I could say that I successfully tested this entry, but I haven’t quite
managed to get it to work. I obtained a device signature that looks
suspiciously like the real thing, but is off in the top 2 or 3 bits. It might
be shoddy wiring on my part, although I’ve successfully done HVPP programming
on ATtinys in DIP packages with a similar setup (This is all on a breadboard,
no hardware programmers involved).
Matthias
_______________________________________________
avrdude-dev mailing list
avrdude-dev@nongnu.org
https://lists.nongnu.org/mailman/listinfo/avrdude-dev
