Differences

This shows you the differences between two versions of the page.

--- microcontrollers:linux_microcontroller_development_options [2012/01/15 16:00] – [Atmel AVR] mithat
+++ microcontrollers:linux_microcontroller_development_options [2012/01/15 19:21] – [Programmer hardware] mithat
@@ Line 67: / Line 67: @@
 ==== Programmer hardware ====
-There are several commercial and DIY implementations of AVR programmers available. However, I see little reason not to use the official USB-based [[http://www.atmel.com/dyn/products/tools_card.asp?tool_id=3808|AVRISP mkII programmer]]---at least as a starting point. It's inexpensive and is [[http://www.nongnu.org/avrdude/user-manual/avrdude_1.html|supported by avrdude]].
+There are several commercial and DIY implementations of AVR programmers available. However, I see little reason not to use the official USB-based [[http://www.atmel.com/dyn/products/tools_card.asp?tool_id=3808|AVRISP mkII programmer]]---at least as a starting point. It's inexpensive and is [[http://www.nongnu.org/avrdude/user-manual/avrdude_1.html|supported by avrdude]]. Another AVR-sourced alternative to consider is the AVR Dragon---which appears to be both a programmer and an ICE interface for debugging.
 To maximize the FOSS spirit, you may prefer an open-hardware design. The [[http://dicks.home.xs4all.nl/avr/usbtiny/|USBtinyISP]] is one such alternative, and Lady Ada packages a [[http://www.ladyada.net/make/usbtinyisp/|promising kit]] based on this design with some modifications. My biggest concerns with using a third-party programmer are that it introduces a layer of uncertainty in the development process ("Does it not work because my code is foobared or because the programmer isn't working?") and compatibility for new target devices will be less likely than with the official AVRISP mkII programmer.