eLua Development

AVR32 Windows compile issues

Classic

List

Threaded

12 messages Options

Davidgrm

AVR32 Windows compile issues

Hi

I am attempting to compile ELUA using AVR32 Studio in Windows. The
problem that I have is that Elua provides a bunch of files in the
Platform->Avr32 folder. Many of these files come from the AVR UC3
Framework but.
appear from an older version of Studio / Toolchain. I am not sure if
Linux users have this same problem? Is there a later release available?
Surely it would be better to use the files provided by the Atmel tools
thus ensuring that they are compatible with the latest versions instead
of providing these files with ELUA?

regards
]
David
_______________________________________________
eLua-dev mailing list
[hidden email]
https://lists.berlios.de/mailman/listinfo/elua-dev

BogdanM

Re: AVR32 Windows compile issues

On Tue, Feb 2, 2010 at 11:41 AM, David <[hidden email]> wrote:

Hi

I am attempting to compile ELUA using AVR32 Studio in Windows. The
problem that I have is that Elua provides a bunch of files in the
Platform->Avr32 folder. Many of these files come from the AVR UC3
Framework but.
appear from an older version of Studio / Toolchain. I am not sure if
Linux users have this same problem? Is there a later release available?

Linux users surely have the same problem, the platform library for Atmel wasn't updated for quite a while now.

Surely it would be better to use the files provided by the Atmel tools
thus ensuring that they are compatible with the latest versions instead
of providing these files with ELUA?

Does the installed toolchain come with pre-compiled CPU support libraries?
What you wrote makes sense if we're using the verbatim copy of Atmel's support package for AVR32. Sometimes, though, we make some changes in the CPU support libraries to suit our needs. Small changes, granted, but still changes. Also, the AVR32 toolchain presents a different model from the regular ARM model that we're using, in that its toolchain comes with all the required libraries; for all our ARM targets we're using a very generic ARM toolchain (not tied to any CPU in particular) and we compile all the platform support files ourselves.
If the toolchain comes with precompiled CPU libraries, and if we're not modifying anyhing in the Atmel libraries (I can't check right now), I can try to change this model to use the libraries already provided by Atmel. If compiling them must still be done by hand, however, this might break our build system. Another solution is to update the CPU support library inside eLua itself.

Best,
Bogdan

_______________________________________________
eLua-dev mailing list
[hidden email]
https://lists.berlios.de/mailman/listinfo/elua-dev

Euripedes Rocha

Re: AVR32 Windows compile issues

I had problems to, when I compiled elua on linux.

--- Em ter, 2/2/10, Bogdan Marinescu <[hidden email]> escreveu:

De: Bogdan Marinescu <[hidden email]>
Assunto: Re: [eLua-dev] AVR32 Windows compile issues
Para: "eLua Users and Development List (www.eluaproject.net)" <[hidden email]>
Data: Terça-feira, 2 de Fevereiro de 2010, 10:23

On Tue, Feb 2, 2010 at 11:41 AM, David <david@...> wrote:
Hi

I am attempting to compile ELUA using AVR32 Studio in Windows. The
problem that I have is that Elua provides a bunch of files in the
Platform->Avr32 folder. Many of these files come from the AVR UC3
Framework but.
appear from an older version of Studio / Toolchain. I am not sure if
Linux users have this same problem? Is there a later release available?

Linux users surely have the same problem, the platform library for Atmel wasn't updated for quite a while now.

Surely it would be better to use the files provided by the Atmel tools
thus ensuring that they are compatible with the latest versions instead
of providing these files with ELUA?

Does the installed toolchain come with pre-compiled CPU support libraries?
What you wrote makes sense if we're using the verbatim copy of Atmel's support package for AVR32. Sometimes, though, we make some changes in the CPU support libraries to suit our needs. Small changes, granted, but still changes. Also, the AVR32 toolchain presents a different model from the regular ARM model that we're using, in that its toolchain comes with all the required libraries; for all our ARM targets we're using a very generic ARM toolchain (not tied to any CPU in particular) and we compile all the platform support files ourselves.
If the toolchain comes with precompiled CPU libraries, and if we're not modifying anyhing in the Atmel libraries (I can't check right now), I can try to change this model to use the libraries already provided by Atmel. If compiling them must still be done by hand, however, this might break our build system. Another solution is to update the CPU support library inside eLua itself.

Best,
Bogdan

-----Anexo incorporado-----

_______________________________________________
eLua-dev mailing list
eLua-dev@...
https://lists.berlios.de/mailman/listinfo/elua-dev

Veja quais são os assuntos do momento no Yahoo! + Buscados: Top 10 - Celebridades - Música - Esportes
_______________________________________________
eLua-dev mailing list
[hidden email]
https://lists.berlios.de/mailman/listinfo/elua-dev

Dado Sutter

Re: AVR32 Windows compile issues

In reply to this post by BogdanM

Another reason for having to compile Atmel libs is that, I remember, you (Bogdan) have found some bugs and had to fix them for eLua.

Best
Dado

On Tue, Feb 2, 2010 at 08:23, Bogdan Marinescu <[hidden email]> wrote:

On Tue, Feb 2, 2010 at 11:41 AM, David <[hidden email]> wrote:

Hi

I am attempting to compile ELUA using AVR32 Studio in Windows. The
problem that I have is that Elua provides a bunch of files in the
Platform->Avr32 folder. Many of these files come from the AVR UC3
Framework but.
appear from an older version of Studio / Toolchain. I am not sure if
Linux users have this same problem? Is there a later release available?

Linux users surely have the same problem, the platform library for Atmel wasn't updated for quite a while now.

Surely it would be better to use the files provided by the Atmel tools
thus ensuring that they are compatible with the latest versions instead
of providing these files with ELUA?

Does the installed toolchain come with pre-compiled CPU support libraries?
What you wrote makes sense if we're using the verbatim copy of Atmel's support package for AVR32. Sometimes, though, we make some changes in the CPU support libraries to suit our needs. Small changes, granted, but still changes. Also, the AVR32 toolchain presents a different model from the regular ARM model that we're using, in that its toolchain comes with all the required libraries; for all our ARM targets we're using a very generic ARM toolchain (not tied to any CPU in particular) and we compile all the platform support files ourselves.
If the toolchain comes with precompiled CPU libraries, and if we're not modifying anyhing in the Atmel libraries (I can't check right now), I can try to change this model to use the libraries already provided by Atmel. If compiling them must still be done by hand, however, this might break our build system. Another solution is to update the CPU support library inside eLua itself.

Best,
Bogdan

_______________________________________________
eLua-dev mailing list
[hidden email]
https://lists.berlios.de/mailman/listinfo/elua-dev

_______________________________________________
eLua-dev mailing list
[hidden email]
https://lists.berlios.de/mailman/listinfo/elua-dev

BogdanM

Re: AVR32 Windows compile issues

This time, your memory is better than mine :) I don't remember this part.

Best,
Bogdan

On Tue, Feb 2, 2010 at 12:37 PM, Dado Sutter <[hidden email]> wrote:

Another reason for having to compile Atmel libs is that, I remember, you (Bogdan) have found some bugs and had to fix them for eLua.

Best
Dado

On Tue, Feb 2, 2010 at 08:23, Bogdan Marinescu <[hidden email]> wrote:

On Tue, Feb 2, 2010 at 11:41 AM, David <[hidden email]> wrote:

Hi

I am attempting to compile ELUA using AVR32 Studio in Windows. The
problem that I have is that Elua provides a bunch of files in the
Platform->Avr32 folder. Many of these files come from the AVR UC3
Framework but.
appear from an older version of Studio / Toolchain. I am not sure if
Linux users have this same problem? Is there a later release available?

Linux users surely have the same problem, the platform library for Atmel wasn't updated for quite a while now.

Surely it would be better to use the files provided by the Atmel tools
thus ensuring that they are compatible with the latest versions instead
of providing these files with ELUA?

Does the installed toolchain come with pre-compiled CPU support libraries?
What you wrote makes sense if we're using the verbatim copy of Atmel's support package for AVR32. Sometimes, though, we make some changes in the CPU support libraries to suit our needs. Small changes, granted, but still changes. Also, the AVR32 toolchain presents a different model from the regular ARM model that we're using, in that its toolchain comes with all the required libraries; for all our ARM targets we're using a very generic ARM toolchain (not tied to any CPU in particular) and we compile all the platform support files ourselves.
If the toolchain comes with precompiled CPU libraries, and if we're not modifying anyhing in the Atmel libraries (I can't check right now), I can try to change this model to use the libraries already provided by Atmel. If compiling them must still be done by hand, however, this might break our build system. Another solution is to update the CPU support library inside eLua itself.

Best,
Bogdan

_______________________________________________
eLua-dev mailing list
[hidden email]
https://lists.berlios.de/mailman/listinfo/elua-dev

_______________________________________________
eLua-dev mailing list
[hidden email]
https://lists.berlios.de/mailman/listinfo/elua-dev

_______________________________________________
eLua-dev mailing list
[hidden email]
https://lists.berlios.de/mailman/listinfo/elua-dev

BogdanM

Re: AVR32 Windows compile issues

In reply to this post by Euripedes Rocha

And how did you fix them?

Best,
Bogdan

On Tue, Feb 2, 2010 at 12:35 PM, Euripedes Rocha <[hidden email]> wrote:

I had problems to, when I compiled elua on linux.

--- Em ter, 2/2/10, Bogdan Marinescu <[hidden email]> escreveu:

De: Bogdan Marinescu <[hidden email]>
Assunto: Re: [eLua-dev] AVR32 Windows compile issues
Para: "eLua Users and Development List (www.eluaproject.net)" <[hidden email]>
Data: Terça-feira, 2 de Fevereiro de 2010, 10:23

On Tue, Feb 2, 2010 at 11:41 AM, David <david@...> wrote:

Hi

I am attempting to compile ELUA using AVR32 Studio in Windows. The
problem that I have is that Elua provides a bunch of files in the
Platform->Avr32 folder. Many of these files come from the AVR UC3
Framework but.
appear from an older version of Studio / Toolchain. I am not sure if
Linux users have this same problem? Is there a later release available?

Linux users surely have the same problem, the platform library for Atmel wasn't updated for quite a while now.

Surely it would be better to use the files provided by the Atmel tools
thus ensuring that they are compatible with the latest versions instead
of providing these files with ELUA?

Does the installed toolchain come with pre-compiled CPU support libraries?
What you wrote makes sense if we're using the verbatim copy of Atmel's support package for AVR32. Sometimes, though, we make some changes in the CPU support libraries to suit our needs. Small changes, granted, but still changes. Also, the AVR32 toolchain presents a different model from the regular ARM model that we're using, in that its toolchain comes with all the required libraries; for all our ARM targets we're using a very generic ARM toolchain (not tied to any CPU in particular) and we compile all the platform support files ourselves.
If the toolchain comes with precompiled CPU libraries, and if we're not modifying anyhing in the Atmel libraries (I can't check right now), I can try to change this model to use the libraries already provided by Atmel. If compiling them must still be done by hand, however, this might break our build system. Another solution is to update the CPU support library inside eLua itself.

Best,
Bogdan

-----Anexo incorporado-----

_______________________________________________
eLua-dev mailing list
eLua-dev@...
https://lists.berlios.de/mailman/listinfo/elua-dev

Veja quais são os assuntos do momento no Yahoo! + Buscados: Top 10 - Celebridades - Música - Esportes
_______________________________________________
eLua-dev mailing list
[hidden email]
https://lists.berlios.de/mailman/listinfo/elua-dev

_______________________________________________
eLua-dev mailing list
[hidden email]
https://lists.berlios.de/mailman/listinfo/elua-dev

Euripedes Rocha

Re: AVR32 Windows compile issues

One of them I posted on the list, the other I can't remember now or I didn't have solved it yet. I just want to point that it's not an in avr32studio for windows problem. Soon i'll back to work with elua and if i solve i'll post it here.

Best

--- Em ter, 2/2/10, Bogdan Marinescu <[hidden email]> escreveu:

De: Bogdan Marinescu <[hidden email]>
Assunto: Re: [eLua-dev] AVR32 Windows compile issues
Para: "eLua Users and Development List (www.eluaproject.net)" <[hidden email]>
Data: Terça-feira, 2 de Fevereiro de 2010, 10:48

And how did you fix them?

Best,
Bogdan

On Tue, Feb 2, 2010 at 12:35 PM, Euripedes Rocha <euripedesrocha@...> wrote:

I had problems to, when I compiled elua on linux.

--- Em ter, 2/2/10, Bogdan Marinescu <bogdan.marinescu@...> escreveu:

De: Bogdan Marinescu <bogdan.marinescu@...>
Assunto: Re: [eLua-dev] AVR32 Windows compile issues
Para: "eLua Users and Development List (www.eluaproject.net)" <elua-dev@...>
Data: Terça-feira, 2 de Fevereiro de 2010, 10:23

On Tue, Feb 2, 2010 at 11:41 AM, David <david@...> wrote:

Hi

I am attempting to compile ELUA using AVR32 Studio in Windows. The
problem that I have is that Elua provides a bunch of files in the
Platform->Avr32 folder. Many of these files come from the AVR UC3
Framework but.
appear from an older version of Studio / Toolchain. I am not sure if
Linux users have this same problem? Is there a later release available?

Linux users surely have the same problem, the platform library for Atmel wasn't updated for quite a while now.

Surely it would be better to use the files provided by the Atmel tools
thus ensuring that they are compatible with the latest versions instead
of providing these files with ELUA?

Does the installed toolchain come with pre-compiled CPU support libraries?
What you wrote makes sense if we're using the verbatim copy of Atmel's support package for AVR32. Sometimes, though, we make some changes in the CPU support libraries to suit our needs. Small changes, granted, but still changes. Also, the AVR32 toolchain presents a different model from the regular ARM model that we're using, in that its toolchain comes with all the required libraries; for all our ARM targets we're using a very generic ARM toolchain (not tied to any CPU in particular) and we compile all the platform support files ourselves.
If the toolchain comes with precompiled CPU libraries, and if we're not modifying anyhing in the Atmel libraries (I can't check right now), I can try to change this model to use the libraries already provided by Atmel. If compiling them must still be done by hand, however, this might break our build system. Another solution is to update the CPU support library inside eLua itself.

Best,
Bogdan

-----Anexo incorporado-----

_______________________________________________
eLua-dev mailing list
eLua-dev@...
https://lists.berlios.de/mailman/listinfo/elua-dev

Veja quais são os assuntos do momento no Yahoo! + Buscados: Top 10 - Celebridades - Música - Esportes
_______________________________________________
eLua-dev mailing list
eLua-dev@...
https://lists.berlios.de/mailman/listinfo/elua-dev

-----Anexo incorporado-----

_______________________________________________
eLua-dev mailing list
eLua-dev@...
https://lists.berlios.de/mailman/listinfo/elua-dev

BogdanM

Re: AVR32 Windows compile issues

In reply to this post by BogdanM

I checked the AVR32 download page from Atmel, and they still provide their support libraries as a separate download, so the solution I'd go for at this point is to update eLua with their new libraries. I'll try to do that soon, since I can see quite a bit of interest in eLua for AVR32.

Best,
Bogdan

On Tue, Feb 2, 2010 at 12:23 PM, Bogdan Marinescu <[hidden email]> wrote:

On Tue, Feb 2, 2010 at 11:41 AM, David <[hidden email]> wrote:

Hi

I am attempting to compile ELUA using AVR32 Studio in Windows. The
problem that I have is that Elua provides a bunch of files in the
Platform->Avr32 folder. Many of these files come from the AVR UC3
Framework but.
appear from an older version of Studio / Toolchain. I am not sure if
Linux users have this same problem? Is there a later release available?

Linux users surely have the same problem, the platform library for Atmel wasn't updated for quite a while now.

Surely it would be better to use the files provided by the Atmel tools
thus ensuring that they are compatible with the latest versions instead
of providing these files with ELUA?

Does the installed toolchain come with pre-compiled CPU support libraries?
What you wrote makes sense if we're using the verbatim copy of Atmel's support package for AVR32. Sometimes, though, we make some changes in the CPU support libraries to suit our needs. Small changes, granted, but still changes. Also, the AVR32 toolchain presents a different model from the regular ARM model that we're using, in that its toolchain comes with all the required libraries; for all our ARM targets we're using a very generic ARM toolchain (not tied to any CPU in particular) and we compile all the platform support files ourselves.
If the toolchain comes with precompiled CPU libraries, and if we're not modifying anyhing in the Atmel libraries (I can't check right now), I can try to change this model to use the libraries already provided by Atmel. If compiling them must still be done by hand, however, this might break our build system. Another solution is to update the CPU support library inside eLua itself.

Best,
Bogdan

_______________________________________________
eLua-dev mailing list
[hidden email]
https://lists.berlios.de/mailman/listinfo/elua-dev

BogdanM

Re: AVR32 Windows compile issues

...then again, I just found this:

"The UC3 SW Framework is also included in AVR32 Studio. No separate download is required."

Back on track :)

Best,
Bogdan

On Tue, Feb 2, 2010 at 2:03 PM, Bogdan Marinescu <[hidden email]> wrote:

I checked the AVR32 download page from Atmel, and they still provide their support libraries as a separate download, so the solution I'd go for at this point is to update eLua with their new libraries. I'll try to do that soon, since I can see quite a bit of interest in eLua for AVR32.

Best,
Bogdan

On Tue, Feb 2, 2010 at 12:23 PM, Bogdan Marinescu <[hidden email]> wrote:

On Tue, Feb 2, 2010 at 11:41 AM, David <[hidden email]> wrote:
Hi

I am attempting to compile ELUA using AVR32 Studio in Windows. The
problem that I have is that Elua provides a bunch of files in the
Platform->Avr32 folder. Many of these files come from the AVR UC3
Framework but.
appear from an older version of Studio / Toolchain. I am not sure if
Linux users have this same problem? Is there a later release available?

Linux users surely have the same problem, the platform library for Atmel wasn't updated for quite a while now.

Surely it would be better to use the files provided by the Atmel tools
thus ensuring that they are compatible with the latest versions instead
of providing these files with ELUA?

Does the installed toolchain come with pre-compiled CPU support libraries?
What you wrote makes sense if we're using the verbatim copy of Atmel's support package for AVR32. Sometimes, though, we make some changes in the CPU support libraries to suit our needs. Small changes, granted, but still changes. Also, the AVR32 toolchain presents a different model from the regular ARM model that we're using, in that its toolchain comes with all the required libraries; for all our ARM targets we're using a very generic ARM toolchain (not tied to any CPU in particular) and we compile all the platform support files ourselves.
If the toolchain comes with precompiled CPU libraries, and if we're not modifying anyhing in the Atmel libraries (I can't check right now), I can try to change this model to use the libraries already provided by Atmel. If compiling them must still be done by hand, however, this might break our build system. Another solution is to update the CPU support library inside eLua itself.

Best,
Bogdan

_______________________________________________
eLua-dev mailing list
[hidden email]
https://lists.berlios.de/mailman/listinfo/elua-dev

Davidgrm

Re: AVR32 Windows compile issues

HI

Thanks for the assistance. Yes the framework is part of AVR32 studio. You can choose the peripherals you wish to use and they place the required modules into the 'framework' section of your code. I am new to the AVR32 (not to AVR) so it is not clear to me if the framework files provided with ELUA have been modified by the ELUA team or if they have just been changed by Atmel in the new version of the framework. This makes it difficult because ideally it would be nice if one could leave the Atmel files untouched so that when the framework is updated everything still works. (assuming they have not changed any parts of the interface used by ELUA :)

regards

David

BogdanM

Re: AVR32 Windows compile issues

On Tue, Feb 2, 2010 at 3:36 PM, Davidgrm <[hidden email]> wrote:

HI

Thanks for the assistance. Yes the framework is part of AVR32 studio. You
can choose the peripherals you wish to use and they place the required
modules into the 'framework' section of your code.

I'm not sure what the 'framework section' is. Something given to you automatically by the IDE? I never even started that :)

I am new to the AVR32
(not to AVR) so it is not clear to me if the framework files provided with
ELUA have been modified by the ELUA team or if they have just been changed
by Atmel in the new version of the framework. This makes it difficult
because ideally it would be nice if one could leave the Atmel files
untouched so that when the framework is updated everything still works.
(assuming they have not changed any parts of the interface used by ELUA :)

Yes :) We generally try to change the framework to suit our needs, and not the other way around. And even if you keep the framework unchanged, its API might well change between different framework releases (and I remember that I actually saw this happening with Atmel's framework), so you don't really gain that much.
By the way, it's eLua, not ELUA :)

Best,
Bogdan

_______________________________________________
eLua-dev mailing list
[hidden email]
https://lists.berlios.de/mailman/listinfo/elua-dev

Davidgrm

Re: AVR32 Windows compile issues

AVR32 Studio has a 'Framework' option which lets you select check boxes for the peripherals you wish to use.. eg ADC, DRAM etc. It then places the require modules in a folder within you project called Framework. This provides all the 'drivers' required for the options selected. I am think that this feature applies to all the AVR32's including the Uc3. This means that if one changes processor you could just change your framework selection and Atmel provides the code required, making porting code between the various AVR32's fairly simple (I have not tested this theory :)) One hopes that they do not change it too often as it can play havoc on rebuilds after updating AVRstudio :(

D