Why .ELF and not .AXF

If you download the evaluation software, or buy the processional edition, you will not get any gcc compiler. It has to be installed separately.

An example configured for the RealView compiler will manage to compile and link, and you will get a *.axf file.

An example configured for gcc will fail to compile and link, since there are no assembler, compiler and linker available on the machine.

Keil previously also sent out the CARM compiler previously. An example that specifies the CARM compiler will also fail to build with a new installation.

Have you verified that the project is configured to build with a compiler that you have?

When I link (I'm using the RealView compiler, not gcc) I get a file *.lnp that contains all parameters for the linking. This data can be used to manually link the project (specifying --via <name>.lnp to armlink).

I see that you are using gcc. Do you have all gcc tools installed? What is the command to link your project? What printout do you get from the link step? Can you manually try to link from the command line? What happens?

If you download the evaluation software, or buy the processional edition, you will not get any gcc compiler. It has to be installed separately.

An example configured for the RealView compiler will manage to compile and link, and you will get a *.axf file.

An example configured for gcc will fail to compile and link, since there are no assembler, compiler and linker available on the machine.

Keil previously also sent out the CARM compiler previously. An example that specifies the CARM compiler will also fail to build with a new installation.

Have you verified that the project is configured to build with a compiler that you have?

When I link (I'm using the RealView compiler, not gcc) I get a file *.lnp that contains all parameters for the linking. This data can be used to manually link the project (specifying --via <name>.lnp to armlink).

I see that you are using gcc. Do you have all gcc tools installed? What is the command to link your project? What printout do you get from the link step? Can you manually try to link from the command line? What happens?

Hello Per,

I installed a seperate gcc compiler (GNUARM) the project i am trying to build is made with this compiler so it should work.
(See the website i gave last time.)

i think it does not work correct with uVision at this time because i just found a *.lnp file.

can you telll me moere about the manual linking of the project. I am kind of new to this.

I am still finding answers to all your questions.

what i do is this:
I build my project and then i press the load button in uVision.

I am kind of new to uVision and completly new to GNUARM.
So thanks for all your information and patient.

I build my project and then i press the load button in uVision.

Try to find out if the project builds successfully in the first place, by looking at the log/list/map files.

I am kind of new to uVision and completly new to GNUARM.

Did you try building a small app using uVision, its default toolchain (RealView?) and downloading it to the target device? Check the project settings so see which toolchain (compiler, assembler, linker) is used.

Manual linking should not be necessary, it would only give a clue what's going wrong during the build. But this should also be part of any build logging when using uVision.

--
J

Yes, I agree.

Trying a manual link is something to do _if_ the IDE does not produce a reasonable message.

Start by looking at all messages you get during the build process. If you don't understand them - cut and paste to this thread.

Try to find out if the project builds successfully in the first place, by looking at the log/list/map files

I find a few list files, some have errors so i have to do something about that. Later i will give some examples. and ask how to solve those.

Did you try building a small app using uVision, its default toolchain (RealView?) and downloading it to the target device?

No i did not and I have no idea how i have to do this.

Check the project settings so see which toolchain (compiler, assembler, linker) is used.

I looked at options for target1 (i think this is what you mean with project settings.
Under the tab linker i can do a lot of things but i do not know how to see wich toolchain i use.

It's strange that the linker/uVision tells you that an ELF file was created when the compiler did not even build everything

I found that to but i have no idea about the reason why!

We don't have any background info on your experience with embedded software development so it's difficult to tailor my responses.

I am in the last stage of my education. than i am finished with school. so i do not have a lot of experience with embedded software development.
The reason why i am so keen on the speech project is because this is my final school project. I have to do a study about this project and see if it is usable for further use.

did you try building it with RealView? The .zip file even contains pre-built .axf files.

yes i tried Realview but i do not have a valid license so that doesn't work.
Thanks for pointing out that there are already pre-built .axf files in the zip file.
unfortunately these are to big to fit in the memory of the board.

i know almost for sure that the problem lies with GNUARM and the link to uvision. So i am going to try Cygwin because that should work with uVision.
When installed i will try something really simple.