The Microchip SNAP programmer/debugging tool is on sale for 50% off, making it by far the cheapest official debugger/programmer for Arduino-class chips.
It does ISP and DW (Atmega328p ATtiny85, etc), UPDI (new Mega0 and xTiny chips, like the ATmega4809), SWD (Atmel ARM chips), and JTAG (other ARM chips), as well as the protocols used for many of the PIC chips (8, 16, and 32bits) that "we" don't use much.
(However, it does not support any High Voltage Programming. At least, not on its own.)
AVRFreaks suggests that the coupon activation may be lagging a weekend behind the press release
"Try again later"
my Mac reports a SNAP as a CMSIS-DAP device (standardized ARM SWD api?), so there is hope.
Hmm. The obvious addition to the avrdude.confg file:
programmer
id = "SNAP_isp";
desc = "Microchip SNAP in AVR ISP mode";
type = "jtagice3_isp";
connection_type = usb;
usbpid = 0x2180;
;
Seems to work. Sometimes, anyway. The SNAP seems to have some problems with error recovery; if you forget to connect it to the AVR, you'll get errors (of course), but it needs power-cycling even after correcting, before it will work right.
The SNAP seems to have some problems with error recovery; if you forget to connect it to the AVR, you'll get errors (of course), but it needs power-cycling even after correcting, before it will work right.
Is this only an issue when used with Avrdude, or does this occurs with other uploading tools such as atbackend?
westfw:
AVRFreaks suggests that the coupon activation may be lagging a weekend behind the press release
"Try again later"
my Mac reports a SNAP as a CMSIS-DAP device (standardized ARM SWD api?), so there is hope.
Hmm. The obvious addition to the avrdude.confg file:
programmer
id = "SNAP_isp";
desc = "Microchip SNAP in AVR ISP mode";
type = "jtagice3_isp";
connection_type = usb;
usbpid = 0x2180;
;
Seems to work. Sometimes, anyway. The SNAP seems to have some problems with error recovery; if you forget to connect it to the AVR, you'll get errors (of course), but it needs power-cycling even after correcting, before it will work right.
Thank goodness I bought a few real AVRISP-MKII programmers while they were still available. THOSE always "just work".
Do they support UPDI and SWD?
Although, I get a warm and fuzzy feeling about programmers like ArduinoAsISP or JTAG2UPDI, where you can go into the code an FIX if it is acting up. At least potentially.
It doesn't help much on the host-side, though. AVRDude has gotten pretty hopelessly complex, isn't very well documented, and seems not to have much active development. pyupdi is better, but not complicated enough, yet.
