How to excute output file .axf on target?

Hi Mohan,

You probably want to follow this blog instead: Building an ARMv8 Linux Hello World with ARM Compiler 6. Since your board has a Cortex-A17 there's a little modification in that you're building a 32-bit application, but for AC6 the process is exactly the same.

However, if you're using ARM Compiler 5, that's completely different. As Pete said we used to support it through armcc->armlink, but no longer do, so you have to manually configure things in a similar way, except rather than just telling the compiler and linker where GCC's programs and libraries are, you have to micromanage the build process with these sorts of flags:

ARM Compiler armcc User Guide : 8.115 --library_interface=lib

ARM Compiler armcc User Guide : 8.6 --apcs=qualifier...qualifier

.. and obviously manually link the Linux libc using GNU binutils rather than armlink, since none of the ARM Compiler 5 tools will magically figure this out for you.  If you are extremely patient you might be able to manually coerce the ARM Linker to generate a Linux application for you, by telling it (along with compiling with the above) not to scan for libraries among myriad other options, but at the very, very least:

ARM Compiler armlink User Guide : 12.124 --scanlib, --no_scanlib

ARM Compiler armlink User Guide : 12.136 --startup=symbol, --no_startup

The use model most people settle on is generating compiled objects in a static library (.a) and linking it as a part of a Linux application that is otherwise built by GCC and GNU binutils in the normal way. This way you can include code built by the ARM Compiler, without it being too complex, and without involving the ARM Linker.

Ta,

Matt

Hi Mohan,

You probably want to follow this blog instead: Building an ARMv8 Linux Hello World with ARM Compiler 6. Since your board has a Cortex-A17 there's a little modification in that you're building a 32-bit application, but for AC6 the process is exactly the same.

However, if you're using ARM Compiler 5, that's completely different. As Pete said we used to support it through armcc->armlink, but no longer do, so you have to manually configure things in a similar way, except rather than just telling the compiler and linker where GCC's programs and libraries are, you have to micromanage the build process with these sorts of flags:

ARM Compiler armcc User Guide : 8.115 --library_interface=lib

ARM Compiler armcc User Guide : 8.6 --apcs=qualifier...qualifier

.. and obviously manually link the Linux libc using GNU binutils rather than armlink, since none of the ARM Compiler 5 tools will magically figure this out for you.  If you are extremely patient you might be able to manually coerce the ARM Linker to generate a Linux application for you, by telling it (along with compiling with the above) not to scan for libraries among myriad other options, but at the very, very least:

ARM Compiler armlink User Guide : 12.124 --scanlib, --no_scanlib

ARM Compiler armlink User Guide : 12.136 --startup=symbol, --no_startup

The use model most people settle on is generating compiled objects in a static library (.a) and linking it as a part of a Linux application that is otherwise built by GCC and GNU binutils in the normal way. This way you can include code built by the ARM Compiler, without it being too complex, and without involving the ARM Linker.

Ta,

Matt