Forum Discussion
Altera_Forum
Honored Contributor
7 years agoIn the property of the project, Setting: The target must be identical with C compiler Arm assembler and linker : Cortex-A9.no_neon.no_vfp.
The ARM support wrote: Hi Jerome, One thing to note immediately is that the options "--cpu=Cortex-A9.no_neon.no_vfp --fpu=vfpv3" to the linker directly conflict with each other. You can't build for a CPU with no FPU yet specify an FPU. This may be the cause of some of your issues. Can you give us the compiler (armcc) options used here? The errors can come out via mismatch between the compiler options used to build two source files or even link against the C library itself. It is possible that hello.o was built without a --cpu option, in which case it would have been built for ARMv4 (not even ARMv4T) which would flag the attribute to disallow Thumb instructions from being linked against that compilation unit. The same goes for the FPU -- specifying no FPU or a different FPU type for each file can prove to set the Advanced SIMD flag on one, but not the other. By aligning your compiler and linker arguments you should be able to align the settings and come out with binary objects which do not have conflicting attributes. Ta, Matt