Should I "Migrate the current project to component infrastructure" ??

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

Opening an old Atmel Studio v6.2 project in Studio v7:

 

What is "component infrastructure" in this context?

 

Is migrating to "component infrastructure" a good thing?

 

If so, why so?

 

If not, why not?

 

 

Top Tips:

  1. How to properly post source code - see: https://www.avrfreaks.net/comment... - also how to properly include images/pictures
  2. "Garbage" characters on a serial terminal are (almost?) invariably due to wrong baud rate - see: https://learn.sparkfun.com/tutorials/serial-communication
  3. Wrong baud rate is usually due to not running at the speed you thought; check by blinking a LED to see if you get the speed you expected
  4. Difference between a crystal, and a crystal oscillatorhttps://www.avrfreaks.net/comment...
  5. When your question is resolved, mark the solution: https://www.avrfreaks.net/comment...
  6. Beginner's "Getting Started" tips: https://www.avrfreaks.net/comment...
  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Well, I tried both,  and the only difference was in the .atsuo file - which, apparently, "stores settings that only current user uses":

 

https://www.avrfreaks.net/commen...

 

 

Top Tips:

  1. How to properly post source code - see: https://www.avrfreaks.net/comment... - also how to properly include images/pictures
  2. "Garbage" characters on a serial terminal are (almost?) invariably due to wrong baud rate - see: https://learn.sparkfun.com/tutorials/serial-communication
  3. Wrong baud rate is usually due to not running at the speed you thought; check by blinking a LED to see if you get the speed you expected
  4. Difference between a crystal, and a crystal oscillatorhttps://www.avrfreaks.net/comment...
  5. When your question is resolved, mark the solution: https://www.avrfreaks.net/comment...
  6. Beginner's "Getting Started" tips: https://www.avrfreaks.net/comment...
  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

So far, I can't see that it's made any difference at all.

 

Now thinking that, maybe, it has nothing to do with my code or my project or even ASF - just an Atmel/Visual Studio "inner workings" thing ... ?

 

 

Top Tips:

  1. How to properly post source code - see: https://www.avrfreaks.net/comment... - also how to properly include images/pictures
  2. "Garbage" characters on a serial terminal are (almost?) invariably due to wrong baud rate - see: https://learn.sparkfun.com/tutorials/serial-communication
  3. Wrong baud rate is usually due to not running at the speed you thought; check by blinking a LED to see if you get the speed you expected
  4. Difference between a crystal, and a crystal oscillatorhttps://www.avrfreaks.net/comment...
  5. When your question is resolved, mark the solution: https://www.avrfreaks.net/comment...
  6. Beginner's "Getting Started" tips: https://www.avrfreaks.net/comment...
  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

ASF is a self contained project, it means that all the files required for device support is part of the project work-space, it does not have any reference to device support information from the IDE.

There would have been a difference if you have upgraded a Barebone project (Gcc Executable Project) which referred to device support information from the IDE (In Atmel Studio 6.2 it is part of the toolchain distribution) then it will migrate to the component\pack infrastructure(device support) in Atmel Studio 7.0. You can find this by right clicking on the project properties and go to packs, in case of ASF it would be empty.

 

Hope that helps.

 

Regards,

Charles

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

Thanks for the explanation.

 

But why could that have not been explained in the message?

 

And, surely, AS studio must have known this - so what was the point in asking me this irrelevant question??

 

<rolls-eyes>

 

You can find this by right clicking on the project properties and go to packs, in case of ASF it would be empty

If I can find it, then AS could equally have found it!

 

angry

 

Top Tips:

  1. How to properly post source code - see: https://www.avrfreaks.net/comment... - also how to properly include images/pictures
  2. "Garbage" characters on a serial terminal are (almost?) invariably due to wrong baud rate - see: https://learn.sparkfun.com/tutorials/serial-communication
  3. Wrong baud rate is usually due to not running at the speed you thought; check by blinking a LED to see if you get the speed you expected
  4. Difference between a crystal, and a crystal oscillatorhttps://www.avrfreaks.net/comment...
  5. When your question is resolved, mark the solution: https://www.avrfreaks.net/comment...
  6. Beginner's "Getting Started" tips: https://www.avrfreaks.net/comment...
Last Edited: Sat. May 12, 2018 - 03:43 PM
  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Atmel Studio is performing the actions related to project upgrade as mentioned in the message, there is a check-box in the dialog which says Don't show the message again. If that check box is checked Atmel Studio will automatically handle the scenario for you.

 

Regards,

Charles

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

Now I'm confused: you said that the actions are not applicable to an ASF project?

 

Atmel Studio should, then, know that - and not ask the irrelevant question?

Top Tips:

  1. How to properly post source code - see: https://www.avrfreaks.net/comment... - also how to properly include images/pictures
  2. "Garbage" characters on a serial terminal are (almost?) invariably due to wrong baud rate - see: https://learn.sparkfun.com/tutorials/serial-communication
  3. Wrong baud rate is usually due to not running at the speed you thought; check by blinking a LED to see if you get the speed you expected
  4. Difference between a crystal, and a crystal oscillatorhttps://www.avrfreaks.net/comment...
  5. When your question is resolved, mark the solution: https://www.avrfreaks.net/comment...
  6. Beginner's "Getting Started" tips: https://www.avrfreaks.net/comment...
  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Ok may be I was not clear, I will try to rephrase it again. Since you are moving a Atmel Studio 6.2 project to Atmel Studio 7.0 it has to perform actions which are related to project upgrade (updating metadata, backing up of project\solution files etc.) this is still applicable and it will check if there are any device support information which has to be migrated based on the new version of IDE which is not applicable in your project. If you click on Don't show this message again then Atmel Studio will handle it automatically for you in case if you again open a Atmel Studio 6.2 project into Atmel Studio 7.0.

 

Hope that helps.

 

Regards,

Charles