Hi to all,
Can somebody answer please how can I use GNU compiler in Keil uVision3 evaluation version? Just I need for it because of code limitation. As I am aware to get a compiled unlimited code is possible by configuring the Keil uVision for GNU compiler. Also I'll need for using of GNU libs. Tell me please who knows how to do it. Thanks.
Dear Andy,
I think this issue could be discussed in Keil forum more comprehencive than in GNU forum because this issue is related to Keil's IDE configurations to use the GNU compiler. OK, let me ask anoder one question: below I give two configurations for Keil IDE for the same project:
1. GNU-Tool-Prefix: arm-uclibc- Cygnus Folder: C:\Cygnus
2. GNU-Tool-Prefix: arm-elf- Cygnus Folder: C:\Program Files\GNUARM\
For the 1-st configuration compilation and linking passes OK, no warnings.
For the 2-nd configuration I see in Keils IDE output window the following error messages:
/cygdrive/c/Program Files/GNUARM/Bin/../lib/gcc/arm-elf/4.2.0/../../../../arm-elf/bin/ld: ERROR: startup.o uses hardware FP, whereas LCD_GNU.elf uses software FP
/cygdrive/c/Program Files/GNUARM/Bin/../lib/gcc/arm-elf/4.2.0/../../../../arm-elf/bin/ld: failed to merge target specific data of file startup.o
Could anybody give me please a clarification on this matter? Thanks.
"2. GNU-Tool-Prefix: arm-elf- Cygnus Folder: C:\Program Files\GNUARM\"
Cygnus cannot work with spaces in folder names!
Remember: Cygnus is basically unix for windows - and unix doesn't support spaces in filenames
"I think this issue could be discussed in Keil forum more comprehencive than in GNU forum because this issue is related to Keil's IDE configurations to use the GNU compiler."
There are two issues here:
(1). Configuring the GCC compiler;
(2). Applying those configurations via the Keil IDE (uVision).
Clearly, before you can think about (2), you have to thoroughly understand (1) - and this is where you need to go to a GCC forum!
Once you know what you're trying to achieve with the GCC compiler (independent of Keil), then (and only then), can you start thinking about how to implement that in uVision - and that's where you need this forum!
I personally use CodeSourcery GNU toolchain that is very well maintained. It uses no Gygwin envronment taht is also a big advantage. As I already mention, there are some problems with integration into uVision. Here you can find one of possible solutions:
http://www.keil.com/forum/docs/thread8537.asp
Dear Milos,
Thank you for your given link. I downloaded the glue tools and tried. Although I couldn't see the object files ( *.o ) as a compiler results for source files *.C ( C code ) and *.S ( assempler code, f.e. Startup.S ). I didn't see any errors or warnings ! As a result of build I saw two new files lcd_gnu.__i.gnu and startup._ia.gnu What the files these are? As these files had small sizes ( 129 bytes and 115 bytes ) I don't have any idea about these files.
Anyway here are the compilation results I have got:
Build target 'LPC2148' compiling lcd_gnu.c... assembling Startup.s... linking... "LCD_GNU.elf" - 0 Error(s), 0 Warning(s).
But.. While I tried to configure to create a hex file too, it gives the following messages:
Build target 'LPC2148' compiling lcd_gnu.c... assembling Startup.s... linking... creating hex file... --- Error: failed to execute 'arm-glue-objcopy' "LCD_GNU.elf" - 1 Error(s), 0 Warning(s).
Thanks.
unix doesn't support spaces in filenames
On the contrary. Unix has supported blanks in filenames about a decade before Microsoft did.
The real problem is elsewhere: spaces in filenames wreak havoc to command line tokenization. Unix shells and tools have had the necessary quoting mechanisms to deal with that issue for ages --- the Microsoft shells had it added as a late afterthought, and it still shows.
The problems with blanks usually appear elsewhere. GUI applications that can't handle blanks in paths to external tools are just about the textbook example. So if there's a problem here, it's more likely in uVision than in Cygwin.
Arthur,
I have checked my version of "glue" package. It is newer than one downloaded from internet. Note that the package was written by my student and put on the web page by him.
Let me know your email address and I will send you the latest package. This should solve your problem.
Thank you for your reply. Sorry for delaid response ( there are 3 hour time difference between Armenia and Central Europe ). My email is: Arthur.Khachatryan@epygiarm.am
P.S. Anybody in forum can send me emails related to ARM processors (at this moment I am working on LPC2148).
Anybody in forum can send me emails related to ARM processors (at this moment I am working on LPC2148).
There are more information available about ARM processors than your mailbox can handle. Most information is available on web sites and are better transmitted as links, so why a wild-card request for mail responses?