AVRisp MKII-clone (OLIMEX AVR-ISP-MK2) USB timeouts

[Lyubcho Haralanov]

Hello,

Thank you for your time spent on this e-mail! I couldn't find a related post so I decided to post it here - excuse me if it is not the proper place!

Summary of the issue: OLIMEX AVR-ISP-MK2 can't enter bootloader mode under Windows 8.1

Description of the issue: The programmer works fine with the default firmware for Atmel Studio and also works fine with latest Atmel Studio. I can enter bootloader mode in Windows 7 and Windows XP and I can use Atmel Flip under 7 and XP. However, I can't enter bootloader mode in Windows 8.1 to change the firmware with Atmel Flip. To enter bootloader mode a small button has to be pressed. After pressing the button the following two error messages are returned in "Windows Device Manager" depending on whether I use USB hub or not:

Unknown USB Device (Device Descriptor Request Failed)

Unknown USB Device (Device Failed Enumeration)

I tried different Atmel Flip drivers (including beta drivers) to no avail. 

I am searching for any clue - whether it is more likely a driver issue or Atmel Flip issue or Windows issue or maybe it is a problem with the hardware. If there is a specific variable that might be adjusted in LUFA regarding the USB enumeration time. All suggestions or links to similar problems are welcome.

Thank you for reading,

Lyubcho

[Dean Camera]

Lyubcho,

That sounds like the bootloader on your device is misconfigured -- it's not that you are missing drivers, but the device itself isn't returning the internal descriptors to the host machine correctly. I'm not sure if Olimex swap out the bootloader in their devices with one of my LUFA based ones, but if they do they might not have compiled it with suitable configuration settings for their part and board.

If you have a secondary programmer around, you can use that to replace the bootloader with a correctly compiled version, and then use that and FLIP to load in new AVRISP firmware. You could also just load in the new firmware directly, but it might be handy to have a working bootloader for future upgrades.

Cheers!
- Dean

--
You received this message because you are subscribed to the Google Groups "LUFA Library Support List" group.
To unsubscribe from this group and stop receiving emails from it, send an email to lufa-support...@googlegroups.com.
To post to this group, send email to lufa-s...@googlegroups.com.
Visit this group at http://groups.google.com/group/lufa-support.
For more options, visit https://groups.google.com/d/optout.

[Lyubcho Haralanov]

Hey Dean,

It seems I've forgotten to mentioned that I am an employee of Olimex. Didn't want to bother you on your personal e-mail, that's why I wrote here.

Thank you for pointing me out where the problem might be. It turns our the initial firmware was somehow buggy. We used to upload an elf to the AVR-ISP-MK2 via another programmer (we could've  instead uploaded it via the built-in serial bootloader and Flip). The initial elf we used either had wrong set of fuses enabled/disabled or more probably we misconfigured part of your bootloader code, destroying the original bootloader.

The problem is now fixed.

Thank you for the help,

Lyubcho

[Dean Camera]

No worries Lyubcho - good to hear the root cause is found, even if it's an unfortunate one.

Huge apologies to everyone on this list and who've emailed me these last two weeks - I've been run ragged at work which hasn't left me with any time or energy to answer questions. Will try hard this week to get through my backlog.

Cheers!
- Dean