Open sowbug opened 12 years ago
Would the programmer auto-identify the part it's flashing? This could be a killer feature. When people say they've bricked their chip, experts will start answering "get one of those avr-programmers.' We probably need a more distinctive name for this thing.
Yes, it would. Every AVR chip type unique signature, so it would safely flash the right bootloader to the given chip. There is a little leeway in "set fuses appropriately," but the one-touch option would be to return to factory settings, which is always fairly safe.
The only kind of rescue flashing we'd be missing would be high-voltage programming. It requires 12V and many pins. I don't think it's worth it.
In 5 years of dorking around with Atmel parts, and screwing up their fuses, I may have resorted to high-voltage programming once, on an old SAMsomething automotive market part. And I'm not even sure I needed to do that. So yes.
On Thu, Apr 19, 2012 at 3:55 PM, Mike Tsao < reply@reply.github.com
wrote:
Yes, it would. Every AVR chip type unique signature, so it would safely flash the right bootloader to the given chip. There is a little leeway in "set fuses appropriately," but the one-touch option would be to return to factory settings, which is always fairly safe.
The only kind of rescue flashing we'd be missing would be high-voltage programming. It requires 12V and many pins. I don't think it's worth it.
Reply to this email directly or view it on GitHub: https://github.com/sowbug/avr-programmer/issues/10#issuecomment-5234471
This would be menu-driven. Burn the bootloader for the 328p and 32u4, which are likely to be the most common AVR flavors among hobbyists these days. Set fuses appropriately, too. Can we do something cool and clever with compression so they don't take up much flash space?