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.

Compiling Syslink examples

Hi

We have build and tested successfully Syslink_2_00_02_80 on board similar to ti814x. However we like to test syslink examples and in a process to compile the same we are getting errors for cl6x* not found. Can somebody guide us for the correct compilation process and for the required tool. We are interested in running notify application so that we can send notification from ARM(cortex a8) to DSP(M3),register event function on DSP and then resend notification to ARM.

Thanks in advance

Manish

  • There is a file at the root of your SysLink installation called "products.mak".  You need to edit that file according to its instructions.  You will be setting DEVICE=TI814X, and as such you will need to edit the
        else ifeq ("$(DEVICE)","TI814X")
    section.

    Regards,

    - Rob

     

  • Hi

    I think we have edited the products.mak file but we are not sure where to get the correct tool chain and version thereof.

    we are using ezsdk_dm814x-evm_5_02_00_57 but  I dont see any cl470 tools

    Following is the command we use to build rtos side samples.

    make DEVICE=TI814X  GPPOS=Linux LOADER=ELF SDK=NONE SYSLINK_INSTALL_DIR=/bdrse_bsp_sasken_r4/syslink_2_00_02_80 IPC_INSTALL_DIR=/opt/TI/ipc_1_23_03_31 BIOS_INSTALL_DIR=/opt/TI/bios_6_32_01_38 XDC_INSTALL_DIR=/opt/TI/xdctools_3_22_01_21 CGT_C674_ELF_INSTALL_DIR=/Dvsdk/ezsdk_dm814x-evm_5_02_00_57/dsp-devkit/cgt6x_7_3_0 CGT_ARM_INSTALL_DIR=/opt/arm-2010q1 LINUXKERNEL=/bdrse_bsp_sasken_r4/linux samples_rtosmakefile:467: *** CGT_M3_ELF_INSTALL_DIR is set to "", which is invalid (could not find file "/bin/cl470*"). Set this in <SysLink Install>/products.mak. Refer to the SysLink Install Guide for more information..  Stop.

    If above command is correct please let us know the url where we can download the tool chain.

    Thanks

    Manish

     

  • Hi,

    You should also set

    SDK=EZSDK

    otherwise your SysLink build will have a dependency on the M3 components and tool chain which are not included in the EZSDK.

    Best regards,
    Murat