Hi Experts,
Query regarding compiler upgrade from RVDS 3.1 to Arm compiler 5.05 version in windows machine. earlier we are using RVDS 3.1 in windows 7 machine it's absolutely working fine.but we are facing linker related issues while upgrading ARM compiler version 5.05 in windows 10 machine.
we have compiled the Fastboot folder and created ".AXF" file . after that we are generating an object file(Fastboot.o).
This command is working in windows 7 machine with RVDS 3.1 but it's creating issues in Windows 10 with ARM 5.05 version compilers.
"arm-none-eabi-objcopy.exe -I binary -O elf32-little --set-section-flags .data=alloc,readonly,code ../output/FastBoot.nvm ../output/FastBoot.o"
Here ../output/FastBoot.nvm is created by .Axf file.
we are passing "Fastboot.o" file to linker while building main source foalder. so we are facing below Linker issue.
Linking native: ..\output\mac-release.axf"Fatal error: L6007U: Could not recognize the format of file ..\..\FastBoot\output\FastBoot.o."
Kindly let me know, what could be the issue and please suggest me how to overcome this issue.
Build LOg:************************************************************************************************************************-------------- Build: Release in Release ---------------
Linking native: ..\output\mac-release.axfFatal error: L6007U: Could not recognize the format of file ..\..\FastBoot\output\FastBoot.o.Not enough information to produce a SYMDEFs file.Not enough information to produce a FEEDBACK file.Not enough information to list image symbols.Not enough information to list the image map.Finished: 4 information, 0 warning, 0 error and 1 fatal error messages.Aborting because of the error(s) in the build step (bsTargetBuild), m_LastExitCode = 1Process terminated with status 1 (0 minutes, 3 seconds)0 errors, 0 warnings***************************************************************************************************************************
Thanks in Advance
paramesh
Qualcomm India.
yes Andy.