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.

RTOS/TMS320C6472: Compiling XDC Modules For Host Testing

Part Number: TMS320C6472

Tool/software: TI-RTOS

Hello,

I have a set of XDC modules which were developed for the C6472, and would like to compile them for functional testing under Linux.

I have attempted to mimic the example from the RTSC-Pedia:

rtsc.eclipse.org/.../Consuming_Configurable_Content

rtsc.eclipse.org/.../makefiles

When running make I get the following error message:

/home/domain/borton/Perforce/tidsp/ti_rtsc/bios_6_52_00_12/packages/gnu/targets/rts86U/lib/gnu.targets.rts86U.a86_64U(Error.o86_64U): In function `xdc_runtime_Error_policyMin__E':
Error.c:(.text.xdc_runtime_Error_policyMin__E+0x16): undefined reference to `xdc_runtime_Error_IgnoreBlock'
/home/domain/borton/Perforce/tidsp/ti_rtsc/bios_6_52_00_12/packages/gnu/targets/rts86U/lib/gnu.targets.rts86U.a86_64U(Error.o86_64U): In function `xdc_runtime_Error_init__E':
Error.c:(.text.xdc_runtime_Error_init__E+0x8): undefined reference to `xdc_runtime_Error_IgnoreBlock'
collect2: error: ld returned 1 exit status

I am running xdctools_3_32_01_22_core

  • Hi,

     Please check all paths in your CCS project.

    Best Regards,
    Yordan

  • I edited my previous post.
  • Nick,
    the first thing you need to do is to upgrade to XDCtools 3.50. SYS/BIOS 6.52 is not going to work with XDCtools 3.32.
  • Sasha, changing xdctools fixed my initial concern above.

    I was ultimately hoping to compile my XDC module into a python2.7 C Extension module. I have run into a weird issue where python's distutils cannot compile the file, but when I copy the gcc call which python claims it has issues with it seems to compile...

    Below is a copy of the python distutils output. Maybe you can see something in the gcc line which may cause an issue?

    running build
    running build_ext
    building 'covariance' extension
    gcc -pthread -fno-strict-aliasing -O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector-strong --param=ssp-buffer-size=4 -grecord-gcc-switches -m64 -mtune=generic -D_GNU_SOURCE -fPIC -fwrapv -DNDEBUG -O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector-strong --param=ssp-buffer-size=4 -grecord-gcc-switches -m64 -mtune=generic -D_GNU_SOURCE -fPIC -fwrapv -fPIC -Dxdc_target_types__="gnu/targets/std.h" -Dxdc_target_name__=Linux86_64 -Dxdc_cfg__xheader__="\"/home/domain/user/Perforce/srcparts/src4300/src4384/matrix_benchmark/DSP/python/covara/package/cfg/covara_p86_64U.h\"" -DNPY_NO_DEPRECATED_API=NPY_1_7_API_VERSION -I/home/domain/user/Perforce/tidsp/ti_rtsc/bios_6_52_00_12/packages -I/home/domain/user/Perforce/srcparts/src4300/src4384/matrix_benchmark/DSP/Program_Common/RTSC_Common -I/home/domain/user/Perforce/tidsp/ti_rtsc/lin/xdctools_3_50_03_33_core/packages -I/home/domain/user/Perforce/srcparts/src4300/src4384/matrix_benchmark/DSP/python/covara/.. -I/usr/include/python2.7 -c covariancea.c -o build/temp.linux-x86_64-2.7/covariancea.o
    In file included from covariancea.c:10:0:
    /home/domain/user/Perforce/tidsp/ti_rtsc/lin/xdctools_3_50_03_33_core/packages/xdc/std.h:81:22: fatal error: "gnu/targets/std.h": No such file or directory
    #include xdc_target__
    ^
    compilation terminated.
    error: command 'gcc' failed with exit status 1

    As always, thanks for the help.

    Nick
  • I don't really know what's distutils, but from your comment it seems that it changes something in the functionality of the gcc compiler.
    The file gnu/targets/std.h is located in the directory /home/domain/user/Perforce/tidsp/ti_rtsc/bios_6_52_00_12/packages, and I think you are saying that gcc finds it just fine when executed on a command line. All I can recommend is to find some ind of verbose option for distutils and gcc, and compare what's happening in the working and the non-working case.