This thread has been locked.
If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.
It builds COFF ok though. I need to use ELF as that what the prebuild Syslink kernel expects.
My build settings:
and the errors:
It looks like it is still trying to build to the COFF format despite having ELF output selected:
"--abi=eabi not supported when producing TI-COFF output files"
Am I missing some settings in the build envirnoment?
Lee Holeva
The RTSC Target field needs to be:
ti.targets.elf.C674
In CCSv5.1, it automatically changes this for you when you flip the output from COFF to ELF to avoid the confusion.
Thanks
ki
Ok, an .out file got made, but there remains an error:
1 gmake: Target `all' not remade because of errors. C:\Program Files\Texas Instruments\ccsv5\utils\gmake\gmake -k all 'Building file: ../Preprocessing_ti81xx.cfg' 'Invoking: XDCtools' making package.mak (because of package.bld) ... generating interfaces for package configPkg (because package/package.xdc.inc is older than package.xdc) ... lnke674 Preprocessing_ti81xx.pe674 ... [W9999] Placing data in a code section (.text) is discouraged. The data may be interpreted as code. This section will not be compressed. b _c_int00 No Assembly Errors, 1 Assembly Warning 'Finished building: ../Preprocessing_ti81xx.cfg' ' ' 'Building target: Preprocessing.out' 'Invoking: C6000 Linker' "C:/Program Files/Texas Instruments/ccsv5/tools/compiler/c6000/bin/cl6x" -mv6740 -g --diag_warning=225 --abi=eabi -z -m"Preprocessing.map" --warn_sections -i"C:/Program Files/Texas Instruments/ccsv5/tools/compiler/c6000/lib" -i"C:/Program Files/Texas Instruments/ccsv5/tools/compiler/c6000/include" --reread_libs --rom_model -o "Preprocessing.out" -l"./configPkg/linker.cmd" "./Preprocessing.obj" -l"libc.a" <Linking> Preprocessing C/C++ Problem
The .cfg file was copied from an EZSDK example.
Lee Holeva
That error may be left over from the previous build failures. I've seen that issue occur occasionally (I think more with 5.0 than 5.1). Looking at the build console, it looks like the build was successful. If you rebuild again, the old error should go away.