gitbot/qmk_firmware
0
0
Fork 0
mirror of https://github.com/qmk/qmk_firmware.git synced 2025-05-31 13:33:23 +00:00
Code Issues Packages Projects Releases Wiki Activity

Minor documentation improvements.

Browse Source
This commit is contained in:
Dean Camera 2017-04-18 20:34:20 +10:00
parent 4ad929f19d
commit 0b9b632926
1 changed files with 5 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
Projects/AVRISP-MKII/AVRISP-MKII.txt
View File

@ -59,10 +59,14 @@
* - <b>Windows:</b> AVRDUDE 6.2, with alternative driver * - <b>Windows:</b> AVRDUDE 6.2, with alternative driver
* - <b>Linux:</b> AVRDUDE 6.1 * - <b>Linux:</b> AVRDUDE 6.1
* *
* <b>Note that this clone requires an alternative driver under Windows,</b> due to an incompatible change in the official * <b>Note that this clone requires a libUSB based driver under Windows,</b> due to an incompatible change in the official
* Jungo based driver. The alternative driver given here will function with both real and clone AVRISP devices in Atmel * Jungo based driver. The alternative driver given here will function with both real and clone AVRISP devices in Atmel
* Studio 7 onwards under Windows - and as a bonus, also provides AVRDude access to the programmer. * Studio 7 onwards under Windows - and as a bonus, also provides AVRDude access to the programmer.
* *
* As of Atmel Studio version 7.0.1417 the legacy Jungo driver has been deprecated in favor of an official libUSB based
* driver, making the driver packaged here superfluous. Use the driver packaged here only if you are still using an earlier
* Atmel Studio 7 build, otherwise the official Atmel libUSB driver should be used.
*
* Note that this design currently has the following limitations: * Note that this design currently has the following limitations:
* - No reversed/shorted target connector detection and notification * - No reversed/shorted target connector detection and notification
* - A separate header is required for each of the ISP, PDI and TPI programming protocols that the user wishes to use * - A separate header is required for each of the ISP, PDI and TPI programming protocols that the user wishes to use