Varuzhan

Can you confirm the messages below are from using GNUARM 4.1.0 and
not WinARM ? I'm a bit baffled why GCC cannot create the object
files. Its unlikely but could you check these files are not already
present as read-only.

Finally, select 'verbose build output' from the Tools->Options menu
to get GCC to output more info during the build process. Could you
let me know what messages are output with this option selected ?

Regards
Dave

--- In l..., "varuzhandanielyan" wrote:
>
> --- In l..., "pdqlogic" wrote:
> >
> > Hi Varuzhan
> >
> > Could you let me know what error messages you received & what
version
> > of Windows you are using ?
> >
> > I'm not sure why using the external makefile option would cause
ArmEd
> > to close. Could you send me the makefile & project you are using ?
> >
> > Regards
> > Dave
> >
> >
> > --- In l..., "varuzhandanielyan" wrote:
> > >
> > > Does somebody managed to build a project with ArmEb? I tried
> > examples,
> > > received error messages. Then I made a new project - the same
> > result.
> > > When I tried to build with an external makefile, it reported
Ok,
> > but
> > > closed IDE after finishing, and no results.
> > > Varuzhan
> > >
> > I open example hello_wordl project from:
> c:\Program Files\PDQLogic\ArmEd\Examples
> Build Window:
> Making target...
> Compiling hello.c...
> Assembler messages:
> FATAL: can't create .\obj\hello.o
> : Invalid argument
> Compiling printf.c...
> Assembler messages:
> FATAL: can't create .\obj\printf.o
> : Invalid argument
> Compiling bsp.c...
> Assembler messages:
> FATAL: can't create .\obj\bsp.o
> : Invalid argument
> Assembling startup.s...
> Assembler messages:
> Error: use of old and new-style options to set CPU type
> arm-elf-gcc:
> : Invalid argument
> Target build failed (error 1).
>
> I use XP Sp2.
> External Makefile I tried, only after build command failed.
> As an example for it I used WinARM example for LPC2138.
>
> First I tried the GCC from WinARM, then the version, downloaded by
> your link - the same result.
>
> Varuzhan
> Start a New Thread

--- In l..., "pdqlogic" wrote:
>
> Varuzhan
>
> Can you confirm the messages below are from using GNUARM 4.1.0 and
> not WinARM ? I'm a bit baffled why GCC cannot create the object
> files. Its unlikely but could you check these files are not already
> present as read-only.
>
> Finally, select 'verbose build output' from the Tools->Options menu
> to get GCC to output more info during the build process. Could you
> let me know what messages are output with this option selected ?
>
> Regards
> Dave
>
> --- In l..., "varuzhandanielyan" wrote:
> >
> > --- In l..., "pdqlogic" wrote:
> > >
> > > Hi Varuzhan
> > >
> > > Could you let me know what error messages you received & what
> version
> > > of Windows you are using ?
> > >
> > > I'm not sure why using the external makefile option would cause
> ArmEd
> > > to close. Could you send me the makefile & project you are using ?
> > >
> > > Regards
> > > Dave
> > >
> > >
> > > --- In l..., "varuzhandanielyan" wrote:
> > > >
> > > > Does somebody managed to build a project with ArmEb? I tried
> > > examples,
> > > > received error messages. Then I made a new project - the same
> > > result.
> > > > When I tried to build with an external makefile, it reported
> Ok,
> > > but
> > > > closed IDE after finishing, and no results.
> > > > Varuzhan
> > > >
> > >
> >
> > I open example hello_wordl project from:
> > c:\Program Files\PDQLogic\ArmEd\Examples
> > Build Window:
> > Making target...
> > Compiling hello.c...
> > Assembler messages:
> > FATAL: can't create .\obj\hello.o
> > : Invalid argument
> > Compiling printf.c...
> > Assembler messages:
> > FATAL: can't create .\obj\printf.o
> > : Invalid argument
> > Compiling bsp.c...
> > Assembler messages:
> > FATAL: can't create .\obj\bsp.o
> > : Invalid argument
> > Assembling startup.s...
> > Assembler messages:
> > Error: use of old and new-style options to set CPU type
> > arm-elf-gcc:
> > : Invalid argument
> > Target build failed (error 1).
> >
> > I use XP Sp2.
> > External Makefile I tried, only after build command failed.
> > As an example for it I used WinARM example for LPC2138.
> >
> > First I tried the GCC from WinARM, then the version, downloaded by
> > your link - the same result.
> >
> > Varuzhan
>
Hi, Dave

I again downloaded GCC 4.1.0 from your link and installed it
automatically in C:\Program Files\GNUARM and selected it in the
TOOL/OPTIONS GCC as well I checked the Verbse Build Output. Below you
can see messages:
Assembler messages:
FATAL: can't create ./obj/hello.o
: Invalid argument
arm-elf-gcc -c -MMD -MF./obj/hello.d -march=armv4t -mapcs-frame
-mapcs-stack-check -Wall -Wcast-align -O0 -g3 -I. hello.c -o
./obj/hello.o
Compiling printf.c...
Assembler messages:
FATAL: can't create ./obj/printf.o
: Invalid argument
arm-elf-gcc -c -MMD -MF./obj/printf.d -march=armv4t -mapcs-frame
-mapcs-stack-check -Wall -Wcast-align -O0 -g3 -I. printf.c -o
./obj/printf.o
Compiling bsp.c...
Assembler messages:
FATAL: can't create ./obj/bsp.o
: Invalid argument
arm-elf-gcc -c -MMD -MF./obj/bsp.d -march=armv4t -mapcs-frame
-mapcs-stack-check -Wall -Wcast-align -O0 -g3 -I. bsp.c -o ./obj/bsp.o
Assembling startup.s...
Assembler messages:
Error: use of old and new-style options to set CPU type
arm-elf-gcc:
: Invalid argument
arm-elf-gcc -c -Xassembler -mapcs-32 -Xassembler --gdwarf2
-Xassembler -marmv4t -I. startup.s -o ./obj/startup.o
Target build failed (error 1).

Varuzhan Start a New Thread

Richard,

> Because I am a very boring person - here are my results (1.3GHz
> Pentium, 1GByte RAM):

Now, now... Here's the results for an Athlon 4800 X2 with 4G RAM. I
pre-loaded each IDE by running it a couple of times before testing.

> + Eclipse - 12 seconds (? Not the first time I had it open today -
> maybe it was still cached?)

The only Eclipse I have is TI's Code Composter (sorry, couldn't resist) and
it takes 6s to load.

> + IAR Embedded Workbench for ARM - 1 minute 8.55 seconds (the 8051
> version opens really quickly though).

Hmm, my EWARM is ready for business in 11s.

> + CrossWorks - 8.3 seconds - includes opening the previous project.

2.5s.

> + Keil uVision - 8 seconds dead, also includes opening previous
> project.
>

3s until the splash screen goes, but the IDE and will accept input before
the splash screen departs. It seems to be ready in about 2s.

> I've never considered how quickly the IDE opens as a selection criteria
> before :o)

Depends how often it crashes... ;-)

--
Paul Curtis, Rowley Associates Ltd http://www.rowley.co.uk
CrossWorks for ARM, MSP430, AVR, MAXQ, and now Cortex-M3 processors Start a New Thread

Varuzhan

Thanks for the info. We've not come across these errors before but
we'll try to identify the problem & get back you ASAP. Sorry for any
inconvenience.

Regards
Dave

--- In l..., "varuzhandanielyan" wrote:
>
> --- In l..., "pdqlogic" wrote:
> >
> > Varuzhan
> >
> > Can you confirm the messages below are from using GNUARM 4.1.0
and
> > not WinARM ? I'm a bit baffled why GCC cannot create the object
> > files. Its unlikely but could you check these files are not
already
> > present as read-only.
> >
> > Finally, select 'verbose build output' from the Tools->Options
menu
> > to get GCC to output more info during the build process. Could
you
> > let me know what messages are output with this option selected ?
> >
> > Regards
> > Dave
> >
> > --- In l..., "varuzhandanielyan" wrote:
> > >
> > > --- In l..., "pdqlogic" wrote:
> > > >
> > > > Hi Varuzhan
> > > >
> > > > Could you let me know what error messages you received & what
> > version
> > > > of Windows you are using ?
> > > >
> > > > I'm not sure why using the external makefile option would
cause
> > ArmEd
> > > > to close. Could you send me the makefile & project you are
using ?
> > > >
> > > > Regards
> > > > Dave
> > > >
> > > >
> > > > --- In l..., "varuzhandanielyan"
wrote:
> > > > >
> > > > > Does somebody managed to build a project with ArmEb? I
tried
> > > > examples,
> > > > > received error messages. Then I made a new project - the
same
> > > > result.
> > > > > When I tried to build with an external makefile, it
reported
> > Ok,
> > > > but
> > > > > closed IDE after finishing, and no results.
> > > > > Varuzhan
> > > > >
> > > >
> > >
> > > I open example hello_wordl project from:
> > > c:\Program Files\PDQLogic\ArmEd\Examples
> > > Build Window:
> > > Making target...
> > > Compiling hello.c...
> > > Assembler messages:
> > > FATAL: can't create .\obj\hello.o
> > > : Invalid argument
> > > Compiling printf.c...
> > > Assembler messages:
> > > FATAL: can't create .\obj\printf.o
> > > : Invalid argument
> > > Compiling bsp.c...
> > > Assembler messages:
> > > FATAL: can't create .\obj\bsp.o
> > > : Invalid argument
> > > Assembling startup.s...
> > > Assembler messages:
> > > Error: use of old and new-style options to set CPU type
> > > arm-elf-gcc:
> > > : Invalid argument
> > > Target build failed (error 1).
> > >
> > > I use XP Sp2.
> > > External Makefile I tried, only after build command failed.
> > > As an example for it I used WinARM example for LPC2138.
> > >
> > > First I tried the GCC from WinARM, then the version, downloaded
by
> > > your link - the same result.
> > >
> > > Varuzhan
> > >
> > Hi, Dave
>
> I again downloaded GCC 4.1.0 from your link and installed it
> automatically in C:\Program Files\GNUARM and selected it in the
> TOOL/OPTIONS GCC as well I checked the Verbse Build Output. Below
you
> can see messages:
> Assembler messages:
> FATAL: can't create ./obj/hello.o
> : Invalid argument
> arm-elf-gcc -c -MMD -MF./obj/hello.d -march=armv4t -mapcs-frame
> -mapcs-stack-check -Wall -Wcast-align -O0 -g3 -I. hello.c -o
> ./obj/hello.o
> Compiling printf.c...
> Assembler messages:
> FATAL: can't create ./obj/printf.o
> : Invalid argument
> arm-elf-gcc -c -MMD -MF./obj/printf.d -march=armv4t -mapcs-frame
> -mapcs-stack-check -Wall -Wcast-align -O0 -g3 -I. printf.c -o
> ./obj/printf.o
> Compiling bsp.c...
> Assembler messages:
> FATAL: can't create ./obj/bsp.o
> : Invalid argument
> arm-elf-gcc -c -MMD -MF./obj/bsp.d -march=armv4t -mapcs-frame
> -mapcs-stack-check -Wall -Wcast-align -O0 -g3 -I. bsp.c -o ./obj/
bsp.o
> Assembling startup.s...
> Assembler messages:
> Error: use of old and new-style options to set CPU type
> arm-elf-gcc:
> : Invalid argument
> arm-elf-gcc -c -Xassembler -mapcs-32 -Xassembler --gdwarf2
> -Xassembler -marmv4t -I. startup.s -o ./obj/startup.o
> Target build failed (error 1).
>
> Varuzhan
> Start a New Thread

--- In l..., "FreeRTOS.org Info" wrote:
>
> + Eclipse - 12 seconds (? Not the first time I had it open today -
maybe it
> was still cached?)
> + IAR Embedded Workbench for ARM - 1 minute 8.55 seconds (the 8051
version
> opens really quickly though).
> + CrossWorks - 8.3 seconds - includes opening the previous project.
> + Keil uVision - 8 seconds dead, also includes opening previous project.

I'm definitely not a big Java fan (I prefer C#), but I'd like to point
out that your particular version of the Java runtime can have a big
impact on the runtime performance of Java programs. The most recent
versions have just-in-time (JIT) compilation from byte-code to native
code, and that helps a lot.

If you have multiple Java versions on your PC, then the one that's
used will be determined by your system path and/or the classpath
environment variable.

Some Java compiled programs are deployed with their own version of a
JVM, and I find that undesireable because users can't easily upgrade
to get better perfomance.

To update your JVM, go to java.sun.com, click on Java SE on the right,
and select the latest version of the JRE (Java Runtime Environment).
The JRE is basically a Java Virtual Machine (JVM) along with the
standard class libraries.

Kaffe is an open source JVM. It's likely slower than Sun's free
offering. And most of Sun's JRE is open source now, too.

Eric Start a New Thread

> > Can you confirm the messages below are from using GNUARM 4.1.0
and
> > not WinARM ? I'm a bit baffled why GCC cannot create the object
> > files. Its unlikely but could you check these files are not
Hello,

I also tried ArmEd with WinARM, and got the same errors. It failed with the
given examples also.
Here are the messages I am getting.
///////////////////
Assembler messages:
FATAL: can't create ./obj/hello.o
: Invalid argument
arm-elf-gcc -c -MMD -MF./obj/hello.d -march=armv4t -mapcs-frame -mapcs-stack-check
-Wall -Wcast-align -O0 -g3 -I. hello.c -o ./obj/hello.o
Compiling printf.c...
Assembler messages:
FATAL: can't create ./obj/printf.o
////////////////////////

The window gives an error for as.exe
BTW I liked the speed and look.
Is ArmEd going to be remain free forever?
Warm Regards,

Mukund Deshmukh,
Beta Computronics Pvt Ltd.
10/1 IT Park, Parsodi,
Nagpur -440022 India.
Web site - http://betacomp.com

MEET US AT,

K2007, Dusseldorf, Germany, Hall 12, Stall C36-2. Start a New Thread

Hi Varuzhan

I've been able to recreate the behaviour you found with WinARM. The
latest version of WinARM is 4.1.1 and ArmEd has known problems with
this version (we recommed v4.1.0 on our downloads page).

I suspect that after you installed GNUARM v4.1.0 the WinARM entry in
the Windows PATH variable still existed and so ArmEd will have still
used WinARM v4.1.1 rather than GNUARM v4.1.0 and hence caused the
same problems. If you remove the WinARM entry from the PATH variable
you should be up and running. In the meantime we'll have look at the
GCC v4.1.1 / ArmEd incompatibility and update ArmEd.

Regards
Dave

--- In l..., "varuzhandanielyan" wrote:
>
> --- In l..., "pdqlogic" wrote:
> >
> > Varuzhan
> >
> > Can you confirm the messages below are from using GNUARM 4.1.0
and
> > not WinARM ? I'm a bit baffled why GCC cannot create the object
> > files. Its unlikely but could you check these files are not
already
> > present as read-only.
> >
> > Finally, select 'verbose build output' from the Tools->Options
menu
> > to get GCC to output more info during the build process. Could
you
> > let me know what messages are output with this option selected ?
> >
> > Regards
> > Dave
> >
> > --- In l..., "varuzhandanielyan" wrote:
> > >
> > > --- In l..., "pdqlogic" wrote:
> > > >
> > > > Hi Varuzhan
> > > >
> > > > Could you let me know what error messages you received & what
> > version
> > > > of Windows you are using ?
> > > >
> > > > I'm not sure why using the external makefile option would
cause
> > ArmEd
> > > > to close. Could you send me the makefile & project you are
using ?
> > > >
> > > > Regards
> > > > Dave
> > > >
> > > >
> > > > --- In l..., "varuzhandanielyan"
wrote:
> > > > >
> > > > > Does somebody managed to build a project with ArmEb? I
tried
> > > > examples,
> > > > > received error messages. Then I made a new project - the
same
> > > > result.
> > > > > When I tried to build with an external makefile, it
reported
> > Ok,
> > > > but
> > > > > closed IDE after finishing, and no results.
> > > > > Varuzhan
> > > > >
> > > >
> > >
> > > I open example hello_wordl project from:
> > > c:\Program Files\PDQLogic\ArmEd\Examples
> > > Build Window:
> > > Making target...
> > > Compiling hello.c...
> > > Assembler messages:
> > > FATAL: can't create .\obj\hello.o
> > > : Invalid argument
> > > Compiling printf.c...
> > > Assembler messages:
> > > FATAL: can't create .\obj\printf.o
> > > : Invalid argument
> > > Compiling bsp.c...
> > > Assembler messages:
> > > FATAL: can't create .\obj\bsp.o
> > > : Invalid argument
> > > Assembling startup.s...
> > > Assembler messages:
> > > Error: use of old and new-style options to set CPU type
> > > arm-elf-gcc:
> > > : Invalid argument
> > > Target build failed (error 1).
> > >
> > > I use XP Sp2.
> > > External Makefile I tried, only after build command failed.
> > > As an example for it I used WinARM example for LPC2138.
> > >
> > > First I tried the GCC from WinARM, then the version, downloaded
by
> > > your link - the same result.
> > >
> > > Varuzhan
> > >
> > Hi, Dave
>
> I again downloaded GCC 4.1.0 from your link and installed it
> automatically in C:\Program Files\GNUARM and selected it in the
> TOOL/OPTIONS GCC as well I checked the Verbse Build Output. Below
you
> can see messages:
> Assembler messages:
> FATAL: can't create ./obj/hello.o
> : Invalid argument
> arm-elf-gcc -c -MMD -MF./obj/hello.d -march=armv4t -mapcs-frame
> -mapcs-stack-check -Wall -Wcast-align -O0 -g3 -I. hello.c -o
> ./obj/hello.o
> Compiling printf.c...
> Assembler messages:
> FATAL: can't create ./obj/printf.o
> : Invalid argument
> arm-elf-gcc -c -MMD -MF./obj/printf.d -march=armv4t -mapcs-frame
> -mapcs-stack-check -Wall -Wcast-align -O0 -g3 -I. printf.c -o
> ./obj/printf.o
> Compiling bsp.c...
> Assembler messages:
> FATAL: can't create ./obj/bsp.o
> : Invalid argument
> arm-elf-gcc -c -MMD -MF./obj/bsp.d -march=armv4t -mapcs-frame
> -mapcs-stack-check -Wall -Wcast-align -O0 -g3 -I. bsp.c -o ./obj/
bsp.o
> Assembling startup.s...
> Assembler messages:
> Error: use of old and new-style options to set CPU type
> arm-elf-gcc:
> : Invalid argument
> arm-elf-gcc -c -Xassembler -mapcs-32 -Xassembler --gdwarf2
> -Xassembler -marmv4t -I. startup.s -o ./obj/startup.o
> Target build failed (error 1).
>
> Varuzhan
> Start a New Thread

Hi Mukund,

Take a look at my recent post (http://tech.groups.yahoo.com/group/
lpc2000/message/25640). This should hopefully explain the behaviour
you are seeing.

You'll need to download & install v4.1.0 of the GCC toolchain. We
recommend the GNUARM installation, see www.gnuarm.com, as we've used
this extensively (nothing against WinARM though). Remove the
reference to WinARM from your Windows PATH variable, restart ArmEd
and the project should then build.

Yes, ArmEd will remain free. We're working on an integrated debugger
and ARM/THUMB simulator for ArmEd which will be available as a DLL
plug-in for a small cost.

Regards
Dave

--- In l..., "Mukund Deshmukh"
wrote:
>
> > > Can you confirm the messages below are from using GNUARM 4.1.0
> and
> > > not WinARM ? I'm a bit baffled why GCC cannot create the object
> > > files. Its unlikely but could you check these files are not
> Hello,
>
> I also tried ArmEd with WinARM, and got the same errors. It failed
with the
> given examples also.
> Here are the messages I am getting.
> ///////////////////
> Assembler messages:
> FATAL: can't create ./obj/hello.o
> : Invalid argument
> arm-elf-gcc -c -MMD -MF./obj/hello.d -march=armv4t -mapcs-frame -
mapcs-stack-check
> -Wall -Wcast-align -O0 -g3 -I. hello.c -o ./obj/hello.o
> Compiling printf.c...
> Assembler messages:
> FATAL: can't create ./obj/printf.o
> ////////////////////////
>
> The window gives an error for as.exe
> BTW I liked the speed and look.
> Is ArmEd going to be remain free forever?
> Warm Regards,
>
> Mukund Deshmukh,
> Beta Computronics Pvt Ltd.
> 10/1 IT Park, Parsodi,
> Nagpur -440022 India.
> Web site - http://betacomp.com
>
> MEET US AT,
>
> K2007, Dusseldorf, Germany, Hall 12, Stall C36-2.
> Start a New Thread

>You'll need to download & install v4.1.0 of the GCC toolchain. We
>recommend the GNUARM installation, see www.gnuarm.com, as we've used
>this extensively (nothing against WinARM though).

OK, I will give a try. Some how I started liking ArmEd very much, Its
simple, fast, and easy. Keep it up

>Yes, ArmEd will remain free. We're working on an integrated debugger
>and ARM/THUMB simulator for ArmEd which will be available as a DLL
>plug-in for a small cost.

That's Great!!
In fact I am using Programmer Note pad, but its very basic, and the latest
version keeps crashing every 5 min.
A debugger and simulator is welcome, but I rarely use any of them.

Warm Regards,

Mukund Deshmukh,
Beta Computronics Pvt Ltd.
10/1 IT Park, Parsodi,
Nagpur -440022 India.
Web site - http://betacomp.com

MEET US AT,

K2007, Dusseldorf, Germany, Hall 12, Stall C36-2. Start a New Thread

Hi Dave,

Thank you very much. I coorrected PATH setting and tried
again to build your hello_world example. Now it works!
I will continue now to test the ArmEd with my current work
and report in case of new problems.
You are doing a great work. I wish you success.
Best regards,
Varuzhan
--- In l..., "pdqlogic" wrote:
>
> Hi Varuzhan
>
> I've been able to recreate the behaviour you found with WinARM. The
> latest version of WinARM is 4.1.1 and ArmEd has known problems with
> this version (we recommed v4.1.0 on our downloads page).
>
> I suspect that after you installed GNUARM v4.1.0 the WinARM entry in
> the Windows PATH variable still existed and so ArmEd will have still
> used WinARM v4.1.1 rather than GNUARM v4.1.0 and hence caused the
> same problems. If you remove the WinARM entry from the PATH variable
> you should be up and running. In the meantime we'll have look at the
> GCC v4.1.1 / ArmEd incompatibility and update ArmEd.
>
> Regards
> Dave
> Start a New Thread