Started by ylun, November 07, 2018, 05:12:20 pm
Using the manual AVR-ISP-MK2.pdf. References for section numbers are for the manual. In each step that I tried to read the target device, I tried all clock speeds.i. TARGET jumpers on ARV-ISP-MKII for 5V, OFF.ii. Repaired Atmel Studio 7.0 so that all Atmel drivers are installed.1. Log every step in detail. Note that many steps have been tried before.2. Followed the 2.3 Quick setup steps 1 to 4. 2.1 Downloaded and extracted the drivers for AVR-ISP-MK2. These can be downloaded from the following location: https://www.olimex.com/Products/AVR/Programmers/AVR-ISP-MK2/resources/DRIVER-MK2-AS-6-7-W10.zip2.2 Plug AVR-ISP-MK2 to my laptop via a suitable USB cable (printer USB cable). 2.3 Open Device Manager. In my case in Device Manager I see "Atmel -> AVRISP mkII, double clicking AVRISP mkII and going to Driver I see Driver Provider: Atmel Norway AS Driver Date: 2017-03-31 Driver Version: 184.108.40.206 Digital Signer: Atmel Norway2.4 See 2.3, already under Atmel -> AVRISP mkII.3. Try to read the programmer with Atmel.4. Fails, same error message as before: Failed to enter programming mode. ispEnterProgMode: Error status received: Got 0xc0, expected 0x00 (Command has failed to execute on the tool) Unable to enter programming mode. Verify device selection, interface settings, target power, security bit, and connections to the target device. ^Details Timestamp: 2018-11-07 13:41:44.142 Severity: ERROR ComponentId: 20100 StatusCode: 1 ModuleName: TCF (TCF command: Device:startSession failed.) Failed to enter programming mode. ispEnterProgMode: Error status received: Got 0xc0, expected 0x00 (Command has failed to execute on the tool)5. Reboot laptopt. Programmer still connected to laptop.6. Try to read the programmer with Atmel.7. Fails again, same error message as before (4.). Decouple programmer cable from target device.8. Try the manual driver installation mentioned in Section 2.3, Step 4. I double click the AVRISP mkII -> Driver -> Update Driver -> Browse my computer for driver software -> Let me pick from a list ... -> AVRISP mkII (top choice of two, bottom choice follows next).9. Try to read the programmer with Atmel.10. Fails again, same error message as before (4.). Decouple programmer cable from target device.11. Now select the second (bottom) choice of 8. After this the driver now shows up under libusb-win32 devices -> AVRISP mkII in Device Manager. Double clicking AVRISP mkII and going to the tab Driver I see Driver Provider: libusb-win32 Driver Date: 2016-01-27 Driver Version: 220.127.116.11 Digital Signer: Hannes Jochriem Elektronische Bausaetze 12. Try to read the programmer with Atmel.13. Fails again, same error message as before (4.). Decouple programmer cable from target device.14. Updated driver with the choice in step 8.15. Continue to build up frustration.16. Go to Section 5.2 Upgrade firmware button.17. 5.2.1. After pressing the Upgrade pin on the programmer, the programmer shows up in Device Manager as libusb-win32 devices -> AT90USB162. Go to Properties -> Driver shows: Driver Provider: Atmel Corporation Driver Date: 2013-01-05 Driver Version: 18.104.22.168 Digital Signer: Atmel Norway DO NOT DECOUPLE THE USB CABLE!!!! 5.2.2. Atmel already installed previously. 5.2.3. Right click on AT90USB162 -> Update driver -> Browse my computer ... -> ...\Flip 3.4.7\usb -> Include subfolders -> Next Windows already installed best driver in my case. Other laptops could be different (having another driver loaded). Device still recognized under -> as: libusb-win32 devices -> AT90USB162. 5.2.4. Start Atmel FLIP, click "Select a target device" -> choose AT90USB162. 5.2.5. "Select a communication medium" -> "USB". 5.2.6. From "File" -> "Load hex file" and choose "AVR456-studio-AVRISP-MKII.hex". In the "Operations flow" section click "Run" button. 5.2.7. Disconnect de programmer from the cable and reconnect. In Device Manager -> Driver tab shows as: Driver Provider: Atmel Norway AS Driver Date: 2017-03-31 Driver Version: 22.214.171.124 Digital Signer: Atmel Norway18. Go to Atmel, connect programmer to target device and try to read target device.19. Same error as before.20. Try not to lose it.