AM3358: Profinet Slave build error

Koichiro Tashiro

Mastermind 22945 points

Part Number: AM3358
Other Parts Discussed in Thread: SYSBIOS

Hi,

Customer is trying to convert their ISDK1.x environment to ISDK2.x for their product.

(Target is AM335x)

While they try to build the code, below error is generated.

==========================================

arm-none-eabi-gcc.exe: error: unrecognized command line option '-@ccsLinker.

opt'

arm-none-eabi-gcc.exe: fatal error: no input files

==========================================

According to similar issue on E2E below, it seems the build option -@ccsLinker.opt is option for TI compiler, so it needs to be change for GCC.

https://e2e.ti.com/support/development_tools/code_composer_studio/f/81/p/392709/1386902#1386902

http://e2e.ti.com/support/development_tools/code_composer_studio/f/81/t/314265

But the makefile is auto-generated file, so customer does not know how to avoid it.

Could you tell me how to avoid the error ?

This needs to be fixed for their certification test planned on June26th.

Below is full error log:

===============================================

**** Build of configuration am335x_debug for project profinet_slave_RT_MRP

****

"C:\\ti\\ccsv6\\utils\\bin\\gmake" -k all 'Building target: profinet_slave_RT_MRP.out'

'Invoking: GNU Linker'

'Flags: -mfloat-abi=hard -Dam3359 -DAM335X_FAMILY_BUILD -DMEM_BARRIER_DISABLE -DTWO_PORT_CFG -DESYSE_PROFIDRIVE_SDK -ffunction-sections -fdata-sections -g -gdwarf-2 -gstrict-dwarf -Wall -Wl,-Map,"profinet_slave_RT_MRP.map" --entry 0x80000000 -nostartfiles -nodefaultlibs -static -Wl,--gc-sections -L"C:/ti/bios_6_45_01_29/packages/gnu/targets/arm/libs/install-native/arm-no

ne-eabi/lib/fpu"

-L"C:/ti/sysbios_ind_sdk_02.01.03.02/sdk/starterware/binary/dal/lib/am335x-e

vm/a8/release/gcc"

-L"C:/ti/sysbios_ind_sdk_02.01.03.02/sdk/starterware/binary/device/lib/am335

x-evm/a8/release/gcc"

-L"C:/ti/sysbios_ind_sdk_02.01.03.02/sdk/starterware/binary/board/lib/am335x

-evm/a8/release/gcc"

-L"C:/ti/sysbios_ind_sdk_02.01.03.02/sdk/starterware/binary/soc/lib/am335x-e

vm/a8/release/gcc"

-L"C:/ti/sysbios_ind_sdk_02.01.03.02/sdk/starterware/binary/utils/lib/am335x

-evm/a8/release/gcc"

-L"C:/ti/sysbios_ind_sdk_02.01.03.02/sdk/os_drivers/lib/am335x"

-L"C:/ti/sysbios_ind_sdk_02.01.03.02/sdk/protocols/profinet_slave/stack_lib_

RT_MRP/am335x"

-L"C:/ti/sysbios_ind_sdk_02.01.03.02/sdk/protocols/snmp/stack_lib/am335x"

-L"C:/ti/sysbios_ind_sdk_02.01.03.02/sdk/board/lib/am335x"

-Wl,--defsym,STACKSIZE=0x18000 -Wl,--defsym,HEAPSIZE=0x400 -Wl,--start-group'

"C:/ti/ccsv6/tools/compiler/gcc-arm-none-eabi-4_8-2014q3/bin/arm-none-eabi-g

cc.exe" -@"ccsLinker.opt" -o"profinet_slave_RT_MRP.out"

arm-none-eabi-gcc.exe: error: unrecognized command line option '-@ccsLinker.

opt'

arm-none-eabi-gcc.exe: fatal error: no input files compilation terminated.

gmake: *** [profinet_slave_RT_MRP.out] Error 1

gmake: Target `all' not remade because of errors.

**** Build Finished ****

Thanks and regards,

KoT

over 8 years ago

0 Biser Gatchev-XID over 8 years ago

TI__Guru**** 393215 points

The ISDK team have been notified. They will respond here.

Please make sure your customer is aware that ISDK support will be discontinued at the end of this month. For details see: e2e.ti.com/.../580869

0 Paula Carrillo over 8 years ago

TI__Mastermind 40580 points

Hi KoT, by my experience it is better to start from scratch a CCS project, copy all CCS setting from another ISDK 2.X project (you can use profinet as your template). Then, copy all your customer source, header files, include paths, libraries paths etc.
Debugging CCS old makefiles issues could be cumbersome and inefficient in my opinion.

Thank you,
Paula

0 Koichiro Tashiro over 8 years ago in reply to Paula Carrillo

TI__Mastermind 22945 points

Hi Paula,

Thanks for your quick reply.
But, customer already uses ISDK2.x project and copy necessary files from ISDK1.x project.
Still the error is generated. We do not know why command for TI compiler is generated.

Thanks and regards,
KoT

0 Paula Carrillo over 8 years ago in reply to Koichiro Tashiro

TI__Mastermind 40580 points

Hi KoT-san, but do you know if they start from scratch a CCS project?. My point, is that sometimes if you reuse and old project and start updating things (paths, configuration, lib) not always "make clean" clean everything and it could be some ghost files..

Let me try to get help here from our CCS experts.

thank you,

Paula

0 Paula Carrillo over 8 years ago in reply to Paula Carrillo

TI__Mastermind 40580 points

A wild guess.. did you customer removed "Linker command file" from CCS project properties. Attached snapshots from ISDK 1.x and ISDK 2. x as a reference

Could they share their project with us so we can take a look?

thank you,

Paula

0 Paula Carrillo over 8 years ago in reply to Paula Carrillo

TI__Mastermind 40580 points

Hi KoT, another wild guess. Please ask them to delete Debug\configPkg and\or Release\configPkg and rebuild. Sometimes this folders have some files using previous XDC configuration which doesn't get clean.

thank you,
Paula

0 Koichiro Tashiro over 8 years ago in reply to Paula Carrillo

TI__Mastermind 22945 points

Hi Paula,

Customer tried your suggestions, but results were the same.

I got customer CCS project. I will send them to you by separate e-mail.

Thanks and regards,

KoT

0 Koichiro Tashiro over 8 years ago in reply to Koichiro Tashiro

TI__Mastermind 22945 points

Hi Paula,

Customer found below E2E.

https://e2e.ti.com/support/development_tools/code_composer_studio/f/81/t/524321

It seems CCS mistakenly generates makefile to use ccsLinker.opt if command line exceeds the maximum limits.
Customer also uses hundreds of source files. Could you ask CCS experts how to workaround the issue?
The certification date is June 26^th, so it needs to be fixed very soon.

Thanks and regards,
KoT

0 Koichiro Tashiro over 8 years ago in reply to Koichiro Tashiro

TI__Mastermind 22945 points

Customer avoided the problem by converting a number of files into one library so that command line length is shorter than the maximum length (8191 characters).

And I also found the root cause of this issue (CCS generates -@ccsLinker option for GNU Linker if command length is longer than 8191) was fixed in CCS6.1.3 or later versions.

Thanks and regards,

KoT

Processors

Processors forum

AM3358: Profinet Slave build error