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.

GPP side of DSLINK apps in CCStudio 3.3?

Other Parts Discussed in Thread: CCSTUDIO

Hello,

Can someone tell me how do I setup a project in order to compile the GPP side of a DSPLINK sample app (say, loop) in CCStudio v3.3? I found and followed instructions to build the DSP side of the same app and have been successful. I don't know which linker file to add to the project (if at all it needs one) and what include paths/libraries to include.

Thank you,

Bindu

  • I have added the source files (loop.c from the sample code provided in DSPLINK), a linker found online and set up the include paths/libraries in the compiler and linker sections. But I still get this error:

    ---------------------------- loopgpp.pjt - Debug ----------------------------
    [loop.c]
    "C:\CCStudio_v3.3\tms470\cgtools\bin\cl470" -g -pdsw225 -o2 -fr"C:/CCStudio_v3.3/MyProjects/loopgpp/Debug" -i"D:/angstrom/arm/lib/gcc/arm-angstrom-linux-gnueabi/4.3.3/include" -i"D:/linux-03.20.00.14/include" -i"D:/dsplink_mod/gpp/inc" -i"D:/dsplink_mod/gpp/inc/usr" -i"D:/dsplink_mod/gpp/inc/sys/Linux" -i"D:/dsplink_mod/gpp/inc/sys/Linux/2.6.18" -i"D:/dsplink_mod/gpp/src/samples/loop" -i"D:/dsplink_mod/gpp/src/samples/loop/Linux" -i"D:/dsplink_mod/gpp/src/samples/loop/Linux/2.6.18" -i"D:/angstrom/arm/arm-angstrom-linux-gnueabi/usr/include" -i"D:/dsplink_mod/gpp/BUILD/INCLUDE/USER" -d"_DEBUG" -d"OS_LINUX" -d"MAX_DSPS=1" -d"MAX_PROCESSORS=2" -d"ID_GPP=1" -d"OMAPL1XX" -d"PROC_COMPONENT" -d"POOL_COMPONENT" -d"NOTIFY_COMPONENT" -d"MPCS_COMPONENT" -d"RINGIO_COMPONENT" -d"MPLIST_COMPONENT" -d"MSGQ_COMPONENT" -d"MSGQ_ZCPY_LINK" -d"CHNL_COMPONENT" -d"CHNL_ZCPY_LINK" -d"ZCPY_LINK" -d"KFILE_DEFAULT" -d"DA8XXGEM" -d"DA8XXGEM_PHYINTERFACE=SHMEM_INTERFACE" -d"GPP_SWI_MODE" -d"_REENTRANT" -d"VERIFY_DATA" -d"DDSP_DEBUG" -m
    e -mv5e --abi=eabi --gcc --elf --verbose -c -@"../Debug.lkf" "loop.c"
    TMS470 C/C++ Compiler v4.4.12
    Tools Copyright (c) 1996-2008 Texas Instruments Incorporated
    "loop.c" ==> LOOP_Create
    "loop.c" ==> LOOP_VerifyData
    "loop.c" ==> LOOP_Execute
    "loop.c" ==> LOOP_Delete
    "loop.c" ==> LOOP_Main

    [Linking...] "C:\CCStudio_v3.3\tms470\cgtools\bin\cl470" -@"Debug.lkf"
    <Linking>
    fatal error: file "C:\\CCStudio_v3.3\\MyProjects\\loopgpp\\Debug\\loop.obj" has
    a Tag_ABI_PCS_wchar_t attribute value of "2" that is different than one
    previously seen ("4"); combining incompatible files

    >> Compilation failure

    Build Complete,
    1 Errors, 0 Warnings, 0 Remarks.

    PLEASE HELP.

    Bindu

  • Bindu,

    We don't ship CCS projects with DSPLink. You will need to create the project from scratch.

    You should use the same toolchain that is used by the DSPLink examples when building for the ARM side. Probably GNU toolchain, not TI TMS470. From the your linker error, I would guess you are linking in libraries built with a different toolchain.

    You might consider updating CCS, you are using an old version. The version you have might not have ARM support. You would need to create a makefile project.

    What device are you using?

    ~Ramsey

  • Hello Ramsey,

    I have the OMAPL137 EVM. CCS v3.3 came with the board, so I haven't updated it. I can't find a way to change the default library CCS uses. I tried to supply -l"\dsplink\gpp\export\BIN\Linux\OMAPL1XX\DEBUG\dsplink.lib", but the error still talks about "[Linking...] "C:\CCStudio_v3.3\tms470\cgtools\bin\cl470" -@"Debug.lkf"

    ---------------------------- loopgpp.pjt - Debug ----------------------------
    [Linking...] "C:\CCStudio_v3.3\tms470\cgtools\bin\cl470" -@"Debug.lkf"
    <Linking>
    fatal error: file "C:\\CCStudio_v3.3\\MyProjects\\loopgpp\\Debug\\loop.obj" has
    a Tag_ABI_PCS_wchar_t attribute value of "2" that is different than one
    previously seen ("4"); combining incompatible files

    >> Compilation failure

    Build Complete,
    1 Errors, 0 Warnings, 0 Remarks.

    Thanks.

  • Bindu,

    Looks like you are still using TI TMS470 toolchain for building your Linux application. This is incompatible. Have you tried using GNU toolchain?

    ~Ramsey