Re: AVR32 Windows compile issues
Posted by
BogdanM on
URL: http://elua-development.15.s1.nabble.com/AVR32-Windows-compile-issues-tp4499909p4500417.html
...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,
BogdanOn Tue, Feb 2, 2010 at 12:23 PM, Bogdan Marinescu
<[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