[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [avr-libc-dev] newbie question - attiny88 on Ubuntu
From: |
Allan Macdonald |
Subject: |
Re: [avr-libc-dev] newbie question - attiny88 on Ubuntu |
Date: |
Sun, 29 Mar 2009 12:56:02 -0300 |
Ruud,
Your script works! I successfully built the toolchain, and when I
compiled my project, the target hex object file is identical to one I
had already created using WinAVR-20081205 and the same project
sources. I specified the install directory $HOME/local/avr and, as
such, did not have to run as root.
I tried Bingo's scripts too (I also redefined PREFIX=$HOME/local/avr)
and, although the toolchain built successfully and I can compile and
link my project without errors, the resulting hex image is not
identical. Is the difference GCC-4.2.2 vs. GCC-4.3.3?
Many thanks to all who helped.
Allan
On Fri, Mar 27, 2009 at 12:38 PM, Allan Macdonald
<address@hidden> wrote:
> Ruud,
>
> OK, thanks! I'll give it a try! Wish me luck!
>
> Cheers,
> Allan
>
> On Fri, Mar 27, 2009 at 12:32 PM, Ruud Vlaming <address@hidden> wrote:
>> On Friday 27 March 2009 16:03, you wrote:
>>
>>> Does the toolchain support ATtiny88? I didn't see so on the web site
>> The fact that ATtiny88 is not on my website is because i have not yet
>> ported the Femto OS to that hardware. As far as i am aware however,
>> the gcc made by the toolchain should compile programs for the ATtiny88
>> allright. However, i have not tested this myself. You can let the
>> toolchainbuilder install the toolchain where-ever you like, it is
>> independent of the Femto OS itself.
>>
>>> and latest patch-newdevices patches are for binutils-2.18 and
>>> gcc-4.2.2. Am I mistaken on this?
>> You are mistaken. Make sure you download the latest Femto OS
>> package. (0.88). The bintutils version is 2.19 and so are the
>> downloaded patches. There are wgetted from
>> http://winavr.cvs.sourceforge.net/viewvc/winavr/patches/binutils/2.19/
>>
>> Further the gcc that is build is gcc-4.3.3, but with patches 4.3.2 since
>> at the time of writing (and even now) there was no seperate patches
>> directory available for 4.3.3.
>>
>> I think this is still the most up-to-date toolchain builder around. It could
>> have been a little more complete though. Maybe next release.
>>
>> Ruud
>>
>>
>