AM263P4-Q1: Code Compilation error for Cdd_Ipc driver

Part Number: AM263P4-Q1

Hello Team,

MCAL Package: MCAL_AM26XX_26.00.008
Compiler: ti-cgt-armllvm_4.0.4.LTS

Below is the error message reported while integrating Cdd_Ipc driver from above mentioned MCAL Package:

ipc.png

We are using compiler ti-cgt-armllvm_4.0.4.LTS, assembler doesn't recognize or support ";" for comments and assembler directive .sect ".text.pmu" for code section.

After updating "sys_pmu_asm.asm" as per TI_Arm_Clang_Compiler_Tools_User_Guide, we are able to fix the issue.

gnu.png

After updating the comment from ";" to "//" it is compiling

compare.png

Can you please check and provide me your feedback

Regards, 

Mohasin

  • Hello,

    This expert is currently out of office. Please expect a delay in response until they return next week.

    Kind regards,

    AJ Favela

  • Hi Mohasin,

    This follows the same response as mentioned in the below e2e

    (1) AM261-SOM-EVM: Code Compilation error for Cdd_Ipc driver - Processors forum - Processors - TI E2E support forums

    As discussed in the one of the EB call, have you tried using the flag -x ti-asm only for this file?

    Thanks and Regards,

    Nikhil Dasan

  • Hello Nikhil,

    We have tried to use the flag -x ti-asm. but we are not able to build the file, and it is showing error as below:

    We have used these options to build the sys_pmu_asm.asm file:

    tiarmclang.exe -D_EMPTY -DOSB_TOOL=OSB_clang -mcpu=cortex-r5 -mfpu=vfpv3-d16 -mfloat-abi=hard -mlittle-endian -g -mthumb -x ti-asm -DATOMICS_USER_MULTICORE_CASE=0 -DTS_ARCH_FAMILY=TS_ARM -DTS_ARCH_DERIVATE=TS_AM263PX -DOSB_TOOL=OSB_clang -DAM263PX_SIP_PACKAGE=0 -DSOC_AM263PX=0 -DAM263PX_PLATFORM=0 -DIP_VERSION_LBIST_V0=0 -DIP_VERSION_ESM_V2_0=0 -DDebugP_ASSERT_ENABLED=0 -DMCALEXT_IRQ_USE_OS=1 -DATOMICS_USE_GENERIC_IMPL=1 -c -x assembler-with-cpp sys_pmu_asm.asm -o sys_pmu_asm.o

    Can you please confirm which executables were used by TI to build this file?

    can you please check and provide your feedback 

    Regards,

    Mohasin

  • Hi Mohasin,

    Below is the command to build .asm file

    # Compiling am263px:r5f0_0:release:fls_app: C:/ti/mcal_am263px-REL.MCAL.AM26XX.26.00.00.08/mcal/Mcal_Lib/sys_pmu_asm.asm


    C:/ti/ccs2040/ccs/tools/compiler/ti-cgt-armllvm_4.0.4.LTS/bin/tiarmclang -mcpu=cortex-r5 -mfloat-abi=hard -mfpu=vfpv3-d16 -mlittle-endian -mthumb -c -x ti-asm C:/ti/mcal_am263px-REL.MCAL.AM26XX.26.00.00.08/mcal/Mcal_Lib/sys_pmu_asm.asm -Wti-a,-d=CLANG -o C:/ti/mcal_am263px-REL.MCAL.AM26XX.26.00.00.08/mcal/binary/fls_app/obj/am263px/r5f0_0/release/sys_pmu_asm.oer5f

    May I know why are you using assembler-with-cpp in your command? 
    This is causing the issue, when used along with .asm file.

    Regards,

    Nikhil Dasan

  • Hello Nikhil,

    On our test environment, flag -x assembler-with-cpp is enabled by default to interpret subsequent files as GNU-syntax Arm assembly source files that will be preprocessed by the compiler.

    After discussing internally, it is recommended to continue with replacing comment style ";" with "/" for GNU-syntax as an integration step. No modification is needed from TI side.

    Regards,

    Mohasin

  • Hi Mohasin,

    Wanted to do a quick check at your end before confirmation. The issue here is that if you pass -x multiple times, only the last one will take effect. So in this case the file is compiled with -x assembler-with-cpp because it was passed after -x ti-asm.

    The issue would resolve for this file if you pass -x ti-asm at the end (i.e. after -x assembler-with-cpp)

    I would like to know if this causes failure in other files ? or is there a way for you to build only this file with this order?

    Thanks and Regards,

    Nikhil

  • Hello Nikhil,

    We have checked the option -x ti-asm after -x assembler-with-cpp, unfortunately this will not work out as it is not easy to build a single file using the option suggested by you (lot of modification is needed in dependent modules).

    Hope this is fine as the same approach has been used and accepted by other TI MCALs as well.

    Regards,

    Mohasin

  • Got it. 

    In that case, I believe this is an aligned change at EB end which would be maintained at your end and not be a part of TI MCALs. Hope this okay with current Lucid's delivery as well.

    Thanks and Regards,

    Nikhil Dasan 

  • Hello Nikhil,

    Thanks for the clarification.

    We will take this as confirmation that the change is to be maintained at the EB side and is not part of the TI MCAL deliverables.

    We will keep this as a reference and adapt accordingly in future releases if required.

    Thank you.

    Regards,

    Mohasin