If I compile the standard Blink.ino in within Arduino IDE, then I can in AtmelStudio (6.1.2730 service pack 2) use Tools|Device programming to program the resulting hex file via AVRISP mkII to the arduino board.  That works.

But naturally I want to compile the same Blink.ino within AtmelStudio, and it should automatically upload via the AVRISP mkII after compiling (F5).
This does not work.  The menu item "Upload using programmer" is ticked and "Programmers" is set to "AVRISP mkII".  Pressing F5 produces:

Compiling 'Blink' for 'Arduino Nano w/ ATmega168'
Binary sketch size: 2952 bytes (used 21% of a 14336 byte maximum) (0.20 secs)
Uploading to I/O board using 'avrispmkii'
avrdude: usbdev_open(): did not find any USB device "usb"

One thing to check. Now that you have restarted your pc does this problems still happen?

I'm setting up an avrisp mkII on a new computer to try to replicate the problem.

I haven't installed the usb driver yet so both Visual Micro and the Arduino Ide report.

1)

Can you please report the name, manufacturer and date of the usb driver that you see in "Windows Control Panel\Device Manager" for the avrispmkii so that I can use the same and also which area of device manager does the avrispmkii appear. 

2)
Please confirm that in the Arduino ide you are clicking File>Upload using programmer"


Thanks

Quote:

Good yes this makes more sense now. The Atmel install certainly causes these problems in both Arduino and Visual Micro.

I can tell you that Atmel Studio uses different usb drivers to Arduino and that Arduino uses avrdude.exe to perform the upload and that Visual Micro does the same.

The missing usb driver details I posted appear in the Arduino Ide when clicking "File>Upload using programmer" and the same appears in Visual Micro is "Always use programmer" is ticked. 

The Jungo driver doesn't work with avrisp mkII in Arduino mode. If you can't find the correct usb driver for Arduino let me know and I will try to find you an example.

Good questions. Well first of all please bear in mind that I have to work with whatever Arduino and Atmel produce so don't shoot me

Yes it is a problem. Atmel Studio usb drivers break Arduino programmers and renders the Arduino ide useless for MKII programmer uploads. Obviously currently Visual Micro is 100% Arduino compatible which includes the bad bits!

As my relationship with Atmel grows stronger it is becoming easier to discuss these things with them. This has been a problem for many years but this thread has reminded me of these issues.

I have today written to Atmel to ask for guidance on replicating their programmer upload process. I expect they will provide the info over the next month or two and as soon as I have it we will offer a more intelligent programmer upload feature that can switch between Arduino and Atmel mode.

One thing to keep in mind is that Atmel and Arduino are not currently compatible "out of the box". Visual Micro is a bridge that was implemented in Atmel Studio earlier this year. Stage 1 was the implementation and now we are moving to stage 2 which should see much closer ties and the gaps closed.

Aaah, I was under the impression that Visual micro was an Atmel project!  But you are independent of Atmel?  Many thanks for your work!!

I hope you'll be able to find a good solution in future, but meanwhile, if possible, can you offer any help on how to repair avrdude | visual micro for my current installation?

Thanks. Marius suggests installing the Arduino ide again using the windows installer options. Please try that.

I installed my mkII last night with Jungo, so I will give it a try later today. Otherwise I have another way to do it.

">If required you can run the Atmel Studio 6.1 Jungo driver install again and revert to Atmel Studio drivers with the avrispmkII."

How can this be done exactly?  I've re-run the Atmel Studio installer, selected repair mode (the only other option was de-install, there was no option for installing only drivers) but that did not fix it.  

The reason I ask is this: the Visual Micro programming via AVRISP mkII now works fine, but it seems to work only for chips that have previously been programmed: on a new empty AVR the programming appears to work, but the AVR runs extremely slow afterwards (*).  Tried another empty AVR, but same result.  On 2 other chips that have already been used before all still works fine.   So I'm guessing some fuse bits may be wrong in the empty chips?   And for setting those I need the Jungo driver so the "Device Programming" toolbar button can be used, is this not correct?   Any insights into this problem would be appreciated...

(*) Judging by LED blink rate, it seems to be about 10x slower.  Also the 16MHz xtal has no signal, I guess an internal oscillator is used instead.   
All 4 chips mentioned are ATmega328P.

I also tried the procedure at http://support.atmel.com/bin/customer.exe?=&action=viewKbEntry&id=1343

It produced: C:\Program Files (x86)\Atmel\AVR Jungo USB\usb64>wdreg.exe -log atmelusb.log -inf windrvr6.inf install
WDREG utility v11.00. Build Feb 27 2012 14:45:04

Processing HWID *WINDRVR6
Installing a signed driver package for *WINDRVR6
LOG ok: 1, ENTER:  DriverPackageInstallA
LOG ok: 1, ENTER:  DriverPackageInstallW
LOG ok: 1, Looking for Model Section [DeviceList.NTamd64]...
LOG ok: 1, Installing INF file 'C:\Program Files (x86)\Atmel\AVR Jungo USB\usb64\windrvr6.inf' (Plug and Play).
LOG ok: 1, Looking for Model Section [DeviceList.NTamd64]...
LOG ok: 1, Installing devices with Id "*WINDRVR6" using INF "C:\Windows\System32\DriverStore\FileRepository\windrvr6.inf
_amd64_neutral_c8d97cf517cd4518\windrvr6.inf".
LOG ok: 1, ENTER UpdateDriverForPlugAndPlayDevices...
LOG ok: 0, RETURN UpdateDriverForPlugAndPlayDevices.
LOG ok: 1, Installation was successful.
LOG ok: 0, Install completed
LOG ok: 1, RETURN: DriverPackageInstallW  (0x0)
LOG ok: 1, RETURN: DriverPackageInstallA  (0x0)
difx_install_preinstall_inf: err 0, last event 0, last error 0. SUCCESS
install: completed successfully

But still (even after re-boot of PC) pressing "Apply" in the "Device Programming" window of AtmelStudio produces:

"Unable to connect to tool AVRISP mkII"
details:
Timestamp:      2014-01-07 12:38:16.047
Severity:            ERROR
ComponentId:      20100
StatusCode:      1
ModuleName:      TCF (TCF command: Tool:connect failed.)

In the windows Device Manager the Jungo WinDriver also reports "This device is working properly".

Meanwhile F5 still works fine: 
"Uploading to I/O board using 'avrispmkii'
Done uploading"

The only AVRISmkII I can find there is below "libusb-win32 devices".   I'm reluctant to uninstall that since it will break my Visual Micro uploading, and Arduino IDE uploading (both via AVRISmkII) again, right? 

Could you please confirm that I need to access the fuse bits when programming a new empty chip? 

If yes: can you recommend any way to accomplish this that is compatible with a working (via AVRISmkII) Visual Micro installation?  

UPDATE:  I just discovered a very simple solution!  Just programming a bootloader using the Arduino IDE (this never worked in the past but now it does, since the AVRISmkII is working) does the trick.  It has the welcome side effect of setting the correct fuse bits!    And indeed the processor speed is OK now!    

This only leaves me wondering why the fuse bits are not set during normal programming....

Tim@Visual Micro wrote on Jan 8^th, 2014 at 4:12pm:


I understand.  
I hope future versions of Visual Micro will be able to use the same driver as the rest of AtmelStudio.
Or even better: it would be great if the software could switch drivers by itself, without user intervention.

BTW: fuse bits are defined in boards.txt, not programmers.txt