Hi everyone, I have compiled a lot of ARM projects for the SAM7S series
with no problems. However whenever I compile one of the official ATMEL
series of examples from softpack-1.4-at91sam7s-ek-web.zip I get the
following output...


make -k all
make: *** virtual memory exhausted.  Stop.


Ive tried it in console and in YAGARTO IDE.
I am using WINXP
Make ver 3.80
YAGARTO gcc: 4.2.2

Has anyone else had such problems?
Does it compile on anyone else's system?

I have attached one of the ATMEL examples.(I had to 7zip it because a
normal zip was large)


Murray Horn.

Murray Horn wrote:
> Hi everyone, I have compiled a lot of ARM projects for the SAM7S series
> with no problems. However whenever I compile one of the official ATMEL
> series of examples from softpack-1.4-at91sam7s-ek-web.zip I get the
> following output...
>
>
> make -k all
> make: *** virtual memory exhausted.  Stop.
>
>
> Ive tried it in console and in YAGARTO IDE.
> I am using WINXP
> Make ver 3.80
> YAGARTO gcc: 4.2.2
>
> Has anyone else had such problems?
> Does it compile on anyone else's system?
>
> I have attached one of the ATMEL examples.(I had to 7zip it because a
> normal zip was large)

Maybe it's just a problem with make, see make bug #1517. Try with
Version 3.81 (maybe name the file make381.exe and use "make381 all" for
tests). If you want to stay with make 3.80 you may modify the makefile
to avoid EVAL.

I do not have the Yagarto toolchain installed here. So the results of my
tests are additional information which will not really help with your
setup but may provide additional information:

Building with DevkitARM (r23b, gcc 4.3.0, arm-eabi) and Sourcery-G++
2007q3 (gcc 4.2.1 arm-eabi with CS patches) does work using the files
from the package you have attached (just changed "CROSS" in the makefile
to arm-eabi- or arm-none-eabi-). I have used make 3.81 from the
mingw-project and also tested with make that comes with CS-G++
("cs-make", also based on 3.81-sources). No testing with hardware has
been done but the disassembly looks o.k.

If a make-update does not help an the problem is in the toolchain you
may install one of the other packages as a workaround. There should not
be any side-effect with the Yagarto tools since different prefixes are
used and as far as I can see the Atmel-code does not use any "specials".

Hello,

YAGARTO itself comes with no make. But OpenOCD comes
with make 3.81 too. Your make 3.80 must be a make from
an other tool.

Best regards,

Michael

Thanks. That did it. 3 days of work and all I had to do was ask.

What I did.
I downloaded make-3.81.exe from http://gnuwin32.sourceforge.net/

Next I installed it on winxp.

I made a copy of make in "C:\Program Files\GnuWin32\bin" and renamed (in
the same directory) the new copy to "make381.exe"

In the Atmel example's make.bat I changed line
"make.exe -k clean all"
to
"make381.exe -k clean all"

Next I added ";C:\Program Files\GnuWin32\bin" to the path variable.

Path set via   Start..Settings..Control
Panel..System..Advanced..Environment Variables..(System
variables)..Path.

Everything seems to compile in console and YAGARTO.
In Eclipse I had to change the build command from 'use default..make' to
"make381"
via project..properties..build command

No hardware test, I am sure it is ok. Will post a message if the
hardware misbehaves.
Thanks again.
Murray Horn.