I tried compiling using GNUARM toolchain in keil(evaluation). In the output window it shows that it has succesfully created the exe. But when I goto the path where exe is supposed to be placed, I dont find any exe there. what could be the problem?
The linker will not create a file with the extention .exe, because that would indicate an executable file for a PC. Look for files with the extention .bin, or no extension at all. You might also be able to specify the actual output file name in the linker options.
What i meant by exe is that its generating a object file. So, as I am using GNUARM toolchain, its generating object file called <file>.elf But I dont see any such file generated at the location specified by the path.
So why did you call it "exe" when it's not "exe" - it's "elf"?! "But I dont see any such file generated at the location specified by the path." Have you tried a search - can you find it anywhere else?
Even if its extension is elf, its still an executable. I searched also. Its not there.
"Even if its extension is elf, its still an executable" That's true. But you didn't say "executable", did you? - you specifically said "exe" Anyhow, have you checked for the other possibilities like Christoph suggexted; eg, "bin" or no extension at all?
No executable at all. Here is what output window shows when compiled: Build target 'AT91M40800' assembling Startup.s... compiling Syscalls.c... compiling Serial.c... compiling Hello.c... linking... ".\Obj\Hello.elf" - 0 Error(s), 0 Warning(s). When tried to debug, I am getting the following message: Error: Could not load C:\Keil\ARM\GNU\Examples\Hello\Obj\Hello.elf Debugger aborted!
Note This message was edited to correct formatting.
".\Obj\Hello.elf" - 0 Error(s), 0 Warning(s). Hm. Could it be that there's something wrong with the base directory ? Did you search the harddrive for a file named Hello.elf ? Maybe the linker just put it in a place where the rest of the IDE doesn't expect it.
I have searched the entire disk. Its nowhere.
That's true. But you didn't say "executable", did you? - you specifically said "exe" Anyhow, have you checked for the other possibilities like Christoph suggexted; eg, "bin" or no extension at all? Well, well, well. Someone who reads this forum could observe that communication skills of some contributors are less than ideal for a given context of seeking problem resolution. However, I think berating someone for the use of "exe" versus "executable" will not improve their command of English. Raise above it, will you, please? Why do you notice the splinter in your brother's eye, but do not perceive the wooden beam in your own eye?[Matthew 7:3] Nevertheless, I too have encountered the same problem (in the latest release v3.0, but not in the earlier version of RVMDK): Build target 'Simulator' assembling Startup.s... compiling Serial.c... compiling Blinky.c... linking... ".\Flash\Blinky.elf" - 0 Error(s), 0 Warning(s). and I've searched my drive, but blinky.elf is nowhere. Actualy with listing enabled, there is no listing being generated, either. Is there a possibility that this compiler's message is bogus? If blinky.elf is without an "elf" extention (as you had suggested), what the debugger could do if it expects to be there? One could expect the example supplied with the compiler to be working. But it is not, in this case. BTW, the preview button on message posting generates a blank screen (using Firefox 1.5.0.3) so I am submitting this message "as is".
"Is there a possibility that this compiler's message is bogus?" It is possible that the specific messages you've listed aren't generated by the compiler or linker at all, but by the build tool. In this case, it would be possible that the messages are not quite a true reflection of what's actually happened...
View all questions in Keil forum