AVR Studio 5 compatibility with Atmel Studio 6: Project migration

Go To Last Post
7 posts / 0 new
Author
Message
#1
  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

QUESTION: Is there any technical detail that I should take into consideration when developing existing AVR Studio 5 projects on Atmel Studio 6 or can I really just open them with Atmel Studio 6 and continue developing them there?

 

I am trying to migrate many projects from AVR Studio 5.1 to Atmel Studio 6.2 to be able to utilize some features not available on the 5.1. As far as I know, Atmel Studio was mainly developed to add ARM architecture support to AVR Studio, so I would believe that there should be no problem editing existing AVR Studio 5.1 projects on Atmel Studio 6.2 (as long as the same toolchain is used). I opened an existing project with Atmel Studio 6, compiled it and programmed it to my target device and I had no problems. Nevertheless I read the documentation to make sure that I would not find any problems in the future but some of the details are somewhat confusing:

 

  • Reading the RELEASE NOTES: Atmel Studio 6.1 I found that "Atmel Studio 6.1 can be run side by side with Atmel Studio 6.0, AVR Studio® 5.0 and 5.1", meaning that AVR Studio 5 does not need to be uninstalled, but nowhere in the document it's specified that a AVR Studio 5 project can simply be open on Atmel Studio 6. And the phrase side by side could also be understood as "AVR Studio 5 projects should still be programmed on AVR Studio 5" 
  • On the Atmel Web-Documentation for the Atmel Studio 6, a description on how to import projects can be found. Here only AVR Studio 4 and AVR 32 Studio are mentioned, which could be understood as "AVR Studio 5 is already compatible"

 

I have not been able to find a clear answer on this in the documentation nor in the forums and I would really like to make sure that I will not find any unwanted surprises in the future when the projects are further developed.

 

Any hint of explanation would be greatly appreciated!

 

-Ivan

 

 

This topic has a solution.
Last Edited: Tue. Mar 8, 2016 - 03:45 PM
  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Did you somehow miss the memo about V5?

 

I'm astonished anyone has been using that utter bugfest for so long!

 

BTW the latest version of Studio is 7 not 6.2-Service Pack 3.

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0
  • That does not answer my question, clawson. But thanks for the quick response. If you need a project background: I just started working at a company where many 6- and 15-year old projects will be further developed by me. I am the one trying to migrate them into newer versions, which was not done by the previous engineers up until now (don't know why). Plus I have been working with ARM and PIC controllers in the past years and therefore I am not so informed about Atmel tools (so no, I did not get the memo), although I worked with AVR many years ago. Some help/clarification would be very appreciated.
  • I do want to develop them on Studio 7 but I am not even certain about the 5 to 6 compatibility, much less about the 5 to 7.

 

Thanks in advance

 

-Ivan

This reply has been marked as the solution. 
  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

As you have found you should be able to operate the two alongside one another (but beware that later Studio USB drivers are not compatible with older so if you plan to drive USB debuggers/programmers from the IDE then be very cautious). Also be warned that the internal solution/project file formats have been changed. That means you can load an AS5 project into AS6 but during the load it will migrate the file format which may then render the files unreadable by AS5 - so make sure you keep backup copies!

 

The really safe way to do this might be to run one version in a virtual machine where it can have no influence on the other.

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Thanks again for the quick response!

 

  • Thanks for the warning, but I already encountered the issue with the USB-Drivers of my jtagice3 and am trying to solve it ... or I'll just use my jtagice mkII for AVR Studio 5 hereon
  • This is great! So the IDE does the necessary file migration automatically? This should be enough. I don't think we will go back to AVR Studio 5 as soon as we start with Atmel Studio (6 or 7)
  • Our versioning system should take care of separating old versions developed with AS5 and the new ones developed with AS6 or AS7. I will just make sure to document it as good as possible!
  • As you mentioned before, Atmel Studio 7 is the newest version. Can I then also load an AS5 project into AS7? (avoiding the inverse process of course)

 

Cheers!

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

I think the AS5 to AS7 jump is something you will have to test. I don't see why Atmel would have removed the code that revcognises the old XML layout and generates the new so I would expect AS7 to upgrade AS5 files but then again I don't expect Atmel thought there'd be anyone left with enough patience to still be doing battle against the incessant bugs in AS5 at this stage.

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

I think the AS5 to AS7 jump is something you will have to test

That is what I did with the AS5 to AS6 jump, but like I mentioned before I will do this on numerous long ongoing projects with many features each and I cannot test all of them before deciding to work with a new IDE just because Atmel does not document the compatibility properly (at least not for AS6). This might be the reason why the previous engineer did't do the migration and also the reason why so many people still use this "buggy IDE". Specially because we make firmware releases constantly based on new features required from our clients I wanted to find some official documented answer on this respect.

 

The approach you suggested of separating the project files hereon and not trying to go from Atmel Studio backwards makes sense and I will do that, trying to test as many features as possible.

 

Thank you very much for the support and hints!

 

Cheers