Is there interest in supporting some 8051 flavours?

[afiglee]

I'm looking at AT89LP51/52 at this point, since AT89S51/52 already there.
Also what about mode "Write Page With AutoErase"?
Any interest?
I'm implementing this in my fork, just wanted to know to keep fork separate or create PR case of success.
Thank you

[stefanrueger]

Thanks for reaching out. AVRDUDE's main focus is programming 8-bit AVR devices, but the project doesn't mind extending coverage within reason. The AT89LP51/2 should be OK since, as you say, the project already covers the AT89S51/2 albeit for a limited number of programmers. And don't expect the disasm command to work for the MCS51 family parts 😄. (Speaking of it, I just realise that AVRDUDE wrongly offers an (AVR-code) disassembly for the AT89S51/2)

So, yes, well-coded PRs that fit into the project are welcome (as evidenced by the 50+ contributors). Advance warning: The team is currently focussing on releasing v8.1 and there are periods of weeks at a time when no-one is available, so any PR might need a bit of patience, but it will eventually be reviewed and considered.

What does a mode "Write Page With AutoErase" mean? Is this an AT89*51/2 thing? I believe AVRDUDE already utilises page erase for parts that offer a page erase programming mode (XMEGA, the modern UPDI AVR parts, ...).

[afiglee]

Thank you. Yes, "Write Page With AutoErase" is a similar to "Write Page" that it may consequently send 1 to 64 bytes with no setting new address - address will be autoincremented. AutoErase does not need previous erase.
There are similar commands for Data User segment, Code segment, fuses etc. Such a block command may be used with AutoErase or without.
This is AT89LPxxx thing (AT89LP51, AT89LP52RD2 etc..)

[stefanrueger]

OK, I see. Write Code Page with Auto-Erase looks like a completely different programming model, and I suspect implementing it for all supported ISP programmers would expand the maintenance surface of AVRDUDE beyond what the team can handle in terms of reviewing and maintenance time. Please consider providing avrdude.conf.in entries for these parts that work and require as little code changes as possible, preferably no code change at all.

This very likely means not implementing/using Write Code Page with Auto-Erase.

[afiglee]

Ok. I completely understand complexity and absolutely fine if you reject that work, it might be too much for the few chips aside.
However, it may be not that difficult like it looks like from the first time.
I'm targeting usbasp at this point and will be back once I have something to show.
Thank you