This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

ARM Compiler Upgrade issues in windows 10 operating system.

This query is regarding the compiler upgrade from RVDS 3.1 to RVDS 5.1 version (Arm compiler 5.05) in windows 10 machine.

Earlier we used  RVDS 3.1 in windows 7 machine it's absolutely working fine.

but we are facing some issues while upgrading to ARM compiler version 5.05 in windows 10 machine.

we have installed ARM version 5.05 in windows 10 and compiled all source files and created ".AXF" file. 

After that,by using AXF file we are generating "NVM" file and generating object file (.o) by .Nvm file by using below command.

"arm-none-eabi-objcopy.exe -I binary -O elf32-little --set-section-flags .data=alloc,readonly,code ../output/FastBoot.nvm ../output/FastBoot.o"

above 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.

we are able to see below issue while Linking.

Linking native: ..\output\mac-release.axf
"Fatal error: L6007U: Could not recognize the format of file ..\..\FastBoot\output\FastBoot.o."

It would be really great if you could direct me in the right direction to resolve this issue.


Build LOg:
************************************************************************************************************************
-------------- Build: Release in Release ---------------

Linking native: ..\output\mac-release.axf
Fatal 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 = 1
Process terminated with status 1 (0 minutes, 3 seconds)
0 errors, 0 warnings
***************************************************************************************************************************

Thanks in Advance