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 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.
I stand corrected.
"If the path is encapsulated in quotes they will be processed ok."
That should also apply to the windoze command line.
However, in the past, uVision-2 had problems with correctly doing the encapsulation.
I don't know if those problems were ever fixed in uVision-2, nor if uVision-3 has inherited them - I just play it safe and never use spaces in path and/or filenames where the Keil tools are concerned.
Many other toolsets have similar problems (including those that use Cygwin) so my general principle is never use spaces in path and/or filenames. At least that way you know that you're safe!
See this Microsoft article for how to change the 'My Documents' folder name - eg, to something without that stupid space: support.microsoft.com/.../en-us
I have successfully done this on 2 systems now.
But is there a way to similarly rename 'Program Files'...?
See: www.8052.com/.../read.phtml
Hmm. "auditected" must be the most interesting spelling error I have managed in a while. Sounds like it has something to do with audio...
I really can't see how I could have managed to convert "autodetected" to "auditected" :)
A problem here is that some programs do follow the M$ guilelines how to access "My Documents" and some just hard-code "C:\My Documents\".
Since a Win system that has been up for a couple of years and having a lot of programs installed tends to be a bit fragile, it is extra hard to know if that fragility is caused by the system or by individual applications being buggy and making assumptions that they are not allowed to make.
And I didn't even notice it!
Have you been borrowing Erik's kyeborad...?!
;-)
Yes, it is probably contagious :)
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?
Dear Andy,
Even i copied target.ld file into project root directory, i am having the same problem,
startup.o(.text+0xf0):/cygdrive/c/Keil/ARM/GNU/Examples/Blinky/Startup.s:167: undefined reference to '_data'
Please help me
Karuna
"Even i copied target.ld file into project root directory"
It's nothing to do with file location - the message would say something about file location, or file not found, if that were the case.
As previously explained, it's telling you that you have referred to a symbol '_data' but haven't provided any definition for that symbol.
Where do you think that symbol should be defined? Have you checked to see if it is defined?
I would like to express my thanks to all members who has been taken a participation on discussing of this topic. Special thanks to Milos Drutarovsky. Thank you Milos very much for your help. I got the code compiled and linked. I got the hex file and have burned onto target's flash. Unfortunately I couldn’t get the code started on target. I don't know what the reason is? Maybe it has been related to additional options setting for linker? The same project runs while it was compiled by Keil compiler. When I change set the uVision for using of GNU compiler, the code doesn't run on target (LPC2148).
I want to use GNU compiler in Keil uVision3 evaluation version. My target is LPC2468(ARM7TDMI-S). I am facing challenges with the startup file. Can someone please share the startup and linker script files. I didn't get it from "">http://www.keil.com/demo".