Olimex AVR-ISP-MK2 with BASCOM-AVR IDE

[vloeby]

Once it worked well for programming ATiny series in BASCOM.
Trying to program in C i changed the firmware ( in windows 10.64) (page 16 olimex avr-isp-mk2 manual),with microchip studio 7. For using again the Bascom-avr IDE, i uninstalled microchip studio 7and the driver.
But now in Bascom-avr-ide it funtion no longer, not with the JUNGO driver and not with AVRDUDE.

Does anyone have a solution ?

Thanks

[LubOlimex]

You wrote that you changed the firmware to work with Atmel Studio but never wrote that you revert the firmware back. Did you revert the firmware?

[vloeby]

Befor each driver i loaded, i puted the processor in bootloeder state (page 16 )

[LubOlimex]

I tested it here under Windows 10 x64. I managed to get Bascom working by loading the latest firmware of AVR-ISP-MK2 suitable for Atmel/Microchip Studio and using the LibUSB drivers.

Maybe if the problem re-install the Microchip Studio, maybe uninstalling the studio removed the drivers?

[vloeby]

removed all related apps. Connected programmer > reset button > disconnected programmer > connected again. Driver manager > microchip tools > AVR-ISP-MKII driver 1.2.2.0 > file version1.2.6.0 > driver files c:\windows system32\driver\libusb0 sys. In bascom-ide > options > programmer, non off the selected programmers works. ?

[LubOlimex]

Check here: https://www.olimex.com/forum/index.php?topic=5939.0

[vloeby]

According to your latest info. i treid to install the correct driver (AVRDUDE) for window 10 In BASCOM-IDE nothing happened when i wanted to upload a file. Since i don't have a atmega 16, i changed in the parameter field mega16 by t25.
Maybe the screenshots give more clarity.

Regard

Sorry i don't no how to put the images from my screenshot here

[LubOlimex]

You can post images in free image sharing web-site, I usually use https://imgur.com/ and get sharable links then post links to them here.

[vloeby]

hhttps://imgur.com/81GCpmZttps://imgur.com/ATHbJ0U

Hopefully this worked

regards

[LubOlimex]

It doesn't show all the info needed. You should've showed the properties of the debugger in device manager to see exact driver associated with it.

Look how it looks here in the three pictures, compare with your side:

https://imgur.com/a/PGVUkNV