X-Git-Url: http://git.linex4red.de/pub/USBasp.git/blobdiff_plain/9cca7a594f23f46d56ded6ab806235e3fc62055d..f2740a66bafa876dfcf2cdfa4c6f3e17395e8bf8:/Projects/AVRISP-MKII/AVRISP-MKII.txt?ds=sidebyside

diff --git a/Projects/AVRISP-MKII/AVRISP-MKII.txt b/Projects/AVRISP-MKII/AVRISP-MKII.txt
index 1975f462f..740a56c74 100644
--- a/Projects/AVRISP-MKII/AVRISP-MKII.txt
+++ b/Projects/AVRISP-MKII/AVRISP-MKII.txt
@@ -59,10 +59,14 @@
  *    - <b>Windows:</b> AVRDUDE 6.2, with alternative driver
  *    - <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
  *  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:
  *    - 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
@@ -75,13 +79,6 @@
  *  While this application can be compiled for USB AVRs with as little as 8KB of FLASH, for full functionality 16KB or more
  *  of FLASH is required. On 8KB devices, ISP or PDI/TPI protocol programming support can be disabled to reduce program size.
  *
- *  \section Sec_KnownIssues Known Issues:
- *
- *  \par XMEGA EEPROM programming fails in some cases.
- *  Several users have reported that XMEGA EEPROM programming fails unless the chip is erased first. If a non-blank EEPROM
- *  is present, writing further EEPROM data causes corruption.
- *  <a href="https://github.com/abcminiuser/lufa/issues/25">LUFA issue tracker entry</a>.
- *
  *  \section Sec_Installation Installation
  *  The programmer supports multiple platforms, both Windows and Linux.
  *