AVR Freaks

Puhhh, and again the whole suite. I have 100MBit link but my workmate uses an expensive satellite link. He will love it :-)
"compiler.targets" was overwritten (of course) and my project ran out of bounds. Everybody who changed that should keep an eye on it.
Maybe I will try to write-protect it?!

in fact!
some of my friends even still work using studio 6.
(I love testing latests version ;-) )

What was all the microchip stuff that got downloaded thought?(something mplab related)

I have installed it on a Win7-32 Laptop.   Hoping that I would be able to use my JTAGICE-mkII again.

Result.   The Dragon no longer works.   The JTAGICE-mkII remains dead.

I will wait until we hear from a Win10-64 user before having two inoperable AS7 PCs.

David.

I unzipped and copied the directory to:

C:\Program Files\Atmel\Studio\Drivers\inf\winusb\atmel_winusb-8.0.13

and pointed to this directory which contains the INF and DLL and CAT files.

I just get: "Windows was unable to Upgrade my Unknown Device"

-rw-m   28012 06.02.2017 08:34:30 C:\Program Files\Atmel\Studio\Drivers\inf\libusb0\atmel_usb_dfu\atmel_usb_dfu.inf
-rw-m    8790 06.02.2017 08:34:30 C:\Program Files\Atmel\Studio\Drivers\inf\ports\atmel_debuggers_cdc\atmel_debuggers_cdc.inf
-rw-m   16698 06.02.2017 08:34:30 C:\Program Files\Atmel\Studio\Drivers\inf\ports\atmel_devices_cdc\atmel_devices_cdc.inf
-rw-m    9380 06.02.2017 08:34:30 C:\Program Files\Atmel\Studio\Drivers\inf\winusb\atmel_winusb\atmel_winusb.inf
-rw-m    9380 06.02.2017 07:34:30 C:\Program Files\Atmel\Studio\Drivers\inf\winusb\atmel_winusb-8.0.13\atmel_winusb.inf
-rw-m    2440 13.10.2015 08:27:02 C:\Program Files\Atmel\Studio\Drivers\Jungo\usb32\atmelwindrvr_driver.inf
-rw-m    2344 12.08.2015 10:18:00 C:\Program Files\Atmel\Studio\Drivers\Jungo\usb32\windrvr1200.inf
-rw-m    2394 28.01.2014 06:59:44 C:\Program Files\Atmel\Studio\Drivers\Jungo\usb32\windrvr6.inf
-rw-m    2440 13.10.2015 08:30:40 C:\Program Files\Atmel\Studio\Drivers\Jungo\usb64\atmelwindrvr_driver.inf
-rw-m    2344 12.08.2015 08:50:42 C:\Program Files\Atmel\Studio\Drivers\Jungo\usb64\windrvr1200.inf
-rw-m    2394 28.01.2014 06:59:44 C:\Program Files\Atmel\Studio\Drivers\Jungo\usb64\windrvr6.inf
-rw-m    5941 08.01.2015 15:06:24 C:\Program Files\Atmel\Studio\Drivers\Segger\CDC\JLinkCDC.inf
-rw-m    2234 08.01.2015 15:06:24 C:\Program Files\Atmel\Studio\Drivers\Segger\x64\JLinkx64.inf
-rw-m    2163 08.01.2015 15:06:24 C:\Program Files\Atmel\Studio\Drivers\Segger\x86\JLink.inf

My Win7-32 LapTop started with an empty SSD.   It has only ever had AS7.0 installed since the Win7-32 OS was installed last year.

David.

the 1416 release works great for me and I do not see any reason to apply this upgrade.
As I understand there are no changes at all except the driver-fixes for 32-bit windows if Jungo-drivers were used before.
64 bit WIN here and everything fine.

My JTAGICE3 also works after a firmware-upgrade.
 

So, I have a new WIN10 64 bit machine. Just tried the webinstaller on the Atmel site 1188, but it seemed to take forever. All the bars were complete, so I cancelled not knowing what was stuck or what.

No useful info on the install screen, just spinning circles  and I don't know where the install log went - can't find it now having closed it.

The install log showed many attempts at accessing the files on amazon servers failed so I downloaded the offline installer.

Checked here before launching it and see the 1417 build.

Here we go .. with 1417

Installed .. 1417

Load existing AVR project

Get message - This project is referring to a pack that is not installed  Missing Version 1.0.106

... ATmega_DPF  ( Installing pack, please wait )

... Downloading... Error occured while downloading

The remote server returned an error (403) Forbidden

Please advise.

( What is a DPF anyway ??) 

Thanks

OK. Thanks.

Gone into DPF manager and installed everything relevant.

Project loads now.

I don't recall ever having to do anything with these DPFs before in my old Win 7 Studio 7 machine. From memory it just worked  - but that was a while ago .. may have forgot.

Hi,

I'm running the 1417 under Windows 7. Installation worked, it compiles, but my GUI stucks about every 5 seconds for about 1-2 seconds. This is very annoying, a continuous workflow is nearly impossible (the complete Atmel Studio is affected). Did anyone else encountered this problem so far? The last Atmel Studio (1188 for me) worked fine.

Regards

Good point, unfortunately not. During my problem analysis I disabled/closed all unnecessary windows processes. The Task-Manager doesn't give me helpful hints.

Regards

Where there's a will there's a way. I had the will, so I found the way.

Nonetheless, the release notes for the latest version should specify the disappearance of Percepio Trace.

7.0.1417 is official, it's just that updating the web site is a task that (obviously) takes some time. Not everything is running smooth after the merger. 

@acab, try to delete the content in Atmel\Studio\7.0\atbackend\codeCache\ and start Studio again. If not even the simulator is showing in the tools list there is nothing wrong with your tools, it's the backend that is having issues.

Hello,

I'm using win10 creators update (attached file), Atmel studio 7 build 1417, Atmega324P MCU and JTAGICE3/Atmel ICE. I can use JTAGICE3 or Atmel ICE to flash the code to board successfully. But can not debugging due to "Debugger command Prog Mode Leave failed" error, then the FUSES were reset (JTAGEN changed from checked to unchecked).

Do you have any idea to resolve this issue? Thank you.

Hi,

i installed AS 7.0.1417 on a Windows 10 64bit OS.

I have a AVR ISP MK2 Programmer.

In AS the Tools list stay empty, no Programmer, no Simulator.

Target is a ATtiny2313A.

The USB Device seems ok, and the programmer work with AVRDUDE.

Any Ideas?

Could anyone share the note "How to downgrade to use older Jungo drivers." referenced in the release notes for 1417?

The Server behind the embedded link http://atmel.force.com/support/articles/en_US/FAQ/Downgrading-tools-to-use-older-Jungo-driver seem to be down and Atmel sales support is not answering my mail...

Thanks

Holger

@Morten can (and will) probably correct me if I'm wrong, but packs installed when installing Atmel Studio will be updated/replaced with newer versions when you install a new Atmel Studio version. Packs you have manually installed will be left untouched. Your project was created before you updated Studio, and the Studio update upgraded the part pack.

All part packs are available at packs.download.atmel.com, so you can get any version you want.

Perhaps using my AVRISP MkII on Atmel Studio 7.0.1645 running under Windows 10 did not cause the degree of trouble for others that it did for me, but in case it did, here is how I fixed it. Firstly, the PROBLEM.  Simply, after installation of Studio 7.0 my AVRISP MkII would no longer connect to the TARGET. The AVRISP MkII would not even show up in 'Selected debugger/programmer' window (entered by clicking on the hammer tool on the toolbar at the top). The only choices were "Simulator" or "Custom".

I was aware that Atmel Studio 7.0 changed from using the Jungo driver (used for previous versions) to the winUSB driver so I set about troubleshooting that particular aspect. 

I uninstalled Atmel Studio 7.0 and reinstalled using the Web Connected method (there are two methods available for downloading: One is called on-line and the other is called off-line). Results were still the same. 

I then viewed a video from the Indian Youtube page "KnowledgeShelf" for which I am eternally grateful. It was a walkthrough of the 'off-line' method and it was during this that I saw that the Jungo driver had to be replaced. 

I then set about changing the USB driver and that was no easy feat. Anything automatic always came back to installing the Jungo driver with exactly the same symptoms as mentioned above no matter whether the Jungo driver was uninstalled first or whatever. The results were always the same. I tried manually searching for the correct winUSB driver but kept coming up with something that was rejected by the Installer software. I even attempted to get the driver from Microchip but was offered instead a discount voucher for an ATTiny for the inconvenience of arriving at a 404 Web message. "Great, I thought, I could have a room full of them and nothing to program them with" ... but I digress,  

Once more I set about uninstalling Atmel 7.0 with the intention of installing it using the method of KnowledgeShelf, and I had just committed to the uninstall action when I noticed some folders in the uninstall window which looked suspiciously like they contained driver packages. Tracking these back to their source I found that they were under Windows > Program Files (x86) > Atmel > Studio. Yes. That's right, unlike Atmel Studio 6.0 or Atmel Studio 6.2 which are both marked with the full name, for what ever reason, this automatic installation has named the folder simply 'Studio'.  

Under Studio,  there is a folder marked 7.0 and another marked Drivers.  If you look in Drivers > inf you will find winUSB and under winUSB you will find another folder with the elusive 'atmel_winusb'.

When I returned to Device Manager to manually configure the driver, I just gave the path-name to that Drivers folder. (Excitement and expectation was now building to a feverish pitch). 

Anyhow, the upshot is that once that was in place, everything worked. I plugged the AVRISP into the computer USB port and good old Plug and Play found the Device, made a new look entry  (see below) in the Device Manager table which I quickly examined in detail. Going through right click on AVRISP mkII and looking through the detail tabs of the information presented, I could see that I was now referencing winusb.sys of the system32 drivers. 

And there you have it. Hope this helps somebody else.