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.
Hello Paramesh,There are a number of variables here... does it only fail with 5.05 on a Windows 10 machine? Whatabout other hosts?Could the issue be with the (non-Arm tool) objcopy running on a Win10 machine?To help isolate the issue, could you try to link the exact FastBoot.o you used with 3.1 with the 5.05 build?Are you able to share the FastBoot.o files (generated on both Win7 and Win10) so that we can compare them?If files are confidential in nature, use the above Support -> Open a support case link to create an officially tracked thread with the technical support team.
Regards,
Ronan
No, didn't verify in other Hosts. but could see in windows10 with 5.05.
I 've got following information by clicking the "Arm Development Studio" link and I have some questions:-
for that corresponding error ARM has mentioned blow way.
" L6007U: The linker can recognize object files in ELF format and library files in AR format. The specified file is either corrupt or is in a file format that the linker cannot recognize."
The Fastboot.o format is ELF only because I can verify it with the "Readelf" command but have doubts about the compilation. is ARM 5.05 tool (armcc.exe) compatible with windows 10?
We tried to use the 3.1 fastboot.o file in build 5.05 but there was no improvement and our target CPU was "ARM1156 T2-S". But tried all the objcopy files available on the ARM site. All Cortex Family tried with Objcopy Tools because ARM11 wasn't even specified in Arm portal.
Yes, files are confidential in nature. So I can't share those files.
Thanks,
paramesh.