In the makefile, you can set the pins used for VTARGET detection and target RESET. If you wish to try out the rest of the LUFA stack, please download it from the official project page instead.įirst, you need to download the attached package, and edit the makefile to suit your chosen USB AVR target. This package contains an in-development version of my LUFA stack, which is NOT FIT FOR USE outside of this project. If used on an AVR with no ADC subsystem, VTARGET detection is disabled and the device will always report 5V. In theory, it can program with a SCK frequency of up to 4MHz for a USB AVR running at 8MHz, or 8MHz for a USB AVR running at 16MHz.Īs mentioned above, currently there's no short circuit or reversed target detection, so be careful when hooking it up.

would obviously add to the cost of the unit.Ĭurrently, programming modes below 125KHz aren't supported, since I'm using the hardware SPI unit at this time.

The simplest form would be something like the $20 Teensy, AVROpendous or Bumble-B boards, with no extra circuitry. Since you build it yourself, you make it as cheap as you like. Adventurous programmers could also hack the firmware themselves to add features that they desire. In the future, new firmware updates will give added functionality to the device. This gives their initial purpose some extra value outside its use as a general development board. Many people also are starting out with cheap ~$20 USB AVR boards, and want to try out other AVRs later. Free if you've already got a USB AVR board around and want to re-use it as a second programmer. Unfortunately, neither of these are currently in the firmware, but I'll add them in the future.Ĭheaper, if you go for the bare-bones approach or build it entirely yourself. The AVRISP-MKII protocol is slightly better than the original's in that it requires less packet massaging and has more features like short-circuit and reversed-connector warnings. USB-to-Serial, USB-to-SPI/I2C converter, bitbanger). With later extensions, the native USB will allow for even better features than the real AVRISP-MKII, such as alternate modes of operation (e.g. The AVRISP-MKII uses native USB drivers, and since I've written the code for my LUFA USB stack, it seemed like the logical thing to do. Using the official AVRISP-MKII protocol means the programmer will integrate with AVRStudio seamlessly and exposes more features than the simpler AVR910 or similar counterparts. Why AVRISP-MKII over AVR910 or other protocols? Actually, it's a clone, but using entirely open source firmware rather than just ripping of Atmel's binaries from a real AVRISP-MKII. That's right, native USB!Īn AVRISP-MKII, obviously. It's taken me a week and a half to do it, but I've developed the firmware to turn any Atmel USB AVR into an AVRISP-MKII. My latest and greatest side-project is now complete - that is, it's now usable.

Lufa avrisp mkii clone driver