• State Answer Suggested
  • Locked Locked
  • Replies 13 replies
  • Answers 2 answers
  • Subscribers 102 subscribers
  • Views 3253 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

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.

Compiler errors from MessageQ examples for ARM and DSP for LCDKOMAPL138

Usman Majid
Intellectual 620 points
Other Parts Discussed in Thread: OMAPL138, MATHLIB, SYSBIOS

I have a fresh install of CCSv6 with the following components: MCSDK_1_01_00_02, bios_6_41_04_54, xdctools_3_30_06_67_core, ipc_1_25_03_15, pdk_OMAPL138_1_01_00_02, dsplib_c674x_3_1_1_1, edma3_lld_02_11_09_08, imglib_c64Px_3_1_1_0, mathlib_c674x_3_0_2_0, and syslink_2_21_01_05

I did the following procedure: File > New CCS Project > Target: LCDKOMAPL138 > Connection Texas Instruments XDS100v2 USB Debug Probe > Verified (successful) > on the ARM9 tab, named the project > Compiler version: TI v5.2.4 > Project Templates and examples > IPC Examples > OMAPL138 Examples > OMAPL138: MessageQ (ARM) > clicked Next > XDCtools version: 3.30.6.67_core > under Products and Repositories tab the following are selected: Inter-processor Communication > 1.25.3.15, SYS/BIOS > 6.41.4.54, Target: ti.targets.arm.elf.Arm9, Platform: ti.sdo.ipc.examples.platforms.evmOMAPL138.arm, Build-profile: release > clicked Finish

I get the following errors when compiling:

Description Resource Path Location Type
#10010 errors encountered during linking; "messageQ_ARM.out" not built messageQ_ARM C/C++ Problem

Description Resource Path Location Type
<a href="file:/c:/ti/ccsv6/tools/compiler/dmed/HTML/10234.html">#10234-D</a> unresolved symbols remain messageQ_ARM C/C++ Problem

Description Resource Path Location Type
Undefined reference to 'ti_sdo_ipc_gates_GateMPSupportNull_query__E' in file C:\Users\QDI_LAB\workspace_v6_1\messageQ_ARM\Debug\configPkg\package\cfg\message_arm_pe9.oe9 .xdchelp /messageQ_ARM C/C++ Problem

Description Resource Path Location Type
Undefined reference to 'ti_sdo_ipc_gates_GatePeterson_query__E' in file C:\Users\QDI_LAB\workspace_v6_1\messageQ_ARM\Debug\configPkg\package\cfg\message_arm_pe9.oe9 .xdchelp /messageQ_ARM C/C++ Problem

Description Resource Path Location Type
Undefined reference to 'ti_sdo_ipc_heaps_HeapBufMP_getStats__E' in file C:\Users\QDI_LAB\workspace_v6_1\messageQ_ARM\Debug\configPkg\package\cfg\message_arm_pe9.oe9 .xdchelp /messageQ_ARM C/C++ Problem

Description Resource Path Location Type
Undefined reference to 'ti_sdo_ipc_heaps_HeapBufMP_isBlocking__E' in file C:\Users\QDI_LAB\workspace_v6_1\messageQ_ARM\Debug\configPkg\package\cfg\message_arm_pe9.oe9 .xdchelp /messageQ_ARM C/C++ Problem

Description Resource Path Location Type
Undefined reference to 'ti_sdo_ipc_heaps_HeapMemMP_isBlocking__E' in file C:\Users\QDI_LAB\workspace_v6_1\messageQ_ARM\Debug\configPkg\package\cfg\message_arm_pe9.oe9 .xdchelp /messageQ_ARM C/C++ Problem

Are there any special configurations that have to be done to the project in order for this to compile? I get similar errors on the DSP version of this example project also. Also, the first 2 errors (#10010 and #10234-D) occur on other projects as well but those projects compile successfully using the arm_arago_linux_gnueabi-gcc toolchain and run on the board with no problems.

  • 0
    Mastermind 6115 points
    Hi Usman,

    Thanks for your post.

    Please check below mentioned wiki for creating CCS project for syslink examples(MessageQ).
    processors.wiki.ti.com/.../Creating_CCS_Project_for_SysLink_samples
  • 0 in reply to Arvind Singh
    Intellectual 620 points

    I am getting the same errors, also I think this tutorial is out of date, it was created for a much older version of syslink. I do not have the files it refers to in my example project. I attached my example project files to this post.

    messageQ_examples.zip

  • 0 in reply to Usman Majid
    TI__Guru** 116100 points

    Hi,

    How did you get this both projects ?

    I did the following procedure: File > New CCS Project > Target: LCDKOMAPL138 > Connection Texas Instruments XDS100v2 USB Debug Probe > Verified (successful) > on the ARM9 tab, named the project > Compiler version: TI v5.2.4 > Project Templates and examples > IPC Examples > OMAPL138 Examples > OMAPL138: MessageQ (ARM) > clicked Next > XDCtools version: 3.30.6.67_core > under Products and Repositories tab the following are selected: Inter-processor Communication > 1.25.3.15, SYS/BIOS > 6.41.4.54, Target: ti.targets.arm.elf.Arm9, Platform: ti.sdo.ipc.examples.platforms.evmOMAPL138.arm, Build-profile: release > clicked Finish

    I'm not getting any "IPC Examples" option in my CCSv6.

    Did you install any extra package for IPC etc., ?

  • 0 in reply to Titusrathinaraj Stalin
    Intellectual 620 points

    I have the following things installed from the updater:  

    Blackhawk CCSv6.0 Emulation Update 6.0.0.344

        C6000 device support 1.1.1

        C6000 multicore device support 1.0.4

    CCSv6 Service Release Windows 6.1.0.00104

        Debug Server Flash 6.1.0.1247

        OMAP device support 1.0.8

        OMAPL/Integra device support 1.0.9

        Shared device support 1.0.8

        C6000 7.4.0 Help Feature 7.4.0.201303051055

        TI ARM Compiler 5.2. Help 5.2.0.201501080900

        ARM Compiler Tools 5.2.4

        ARM Compiler Tools 5.1.12

        C6000 Compiler Tools 8.0.3

        C6000 Compiler Tools 7.4.14

        C6000 Compiler Tools 7.2.12

        Compiler Tools On-line Documentation 1.1.4

        Hercules Emulation 6.0.7

        TI Emulators 5.1.641.0

    and this is what my new CCS project window looks like

  • 0 in reply to Titusrathinaraj Stalin
    Intellectual 620 points
    I made some progress. I deleted everything TI related and reinstalled CCSv6, the latest MCSDK, and the latest SYSBIOS with its recommended matching XDCTools. This made the first 2 errors (#10010 and #10234-D) disappear. After some more research I installed sysbios 6.37.05.35 and its matching xdctools 3.25.06.96, this fixed all the errors on the messageQ_ARM version and it runs successfully now.

    Now the DSP version of this example still has errors, but only one error:
    Description Resource Path Location Type
    ti.sdo.ipc.examples.platforms.evmOMAPL138.dsp.Platform: no property named 'CPU' .xdchelp /messageQ_DSP line 472 C/C++ Problem
  • 0 in reply to Titusrathinaraj Stalin
    Intellectual 620 points

    Fixed the DSP version by using bios6_35_06_56 for that project with the same xdctools as the arm.

    How do I run both projects at the same time on the arm and dsp?


    Edit: I figured out how to do this and both run successfully.

    Now my question is, how do I load this on the LCDKOMAPL138 board and run it in Linux, not bios. Because currently when it runs through CCS, the board has to be in UBOOT. It does not work when its in Linux. Is there a way to run this inside Linux?

  • 0 in reply to Usman Majid
    TI__Guru** 116100 points
    Hi,
    I'm glad that you able to solve the problem.
    Do you want to load the DSP app on DSP core when Linux is running in ARM ?
    You can use SYSLINK.
    processors.wiki.ti.com/.../MCSDK_OMAPL138_User_Guide_Chapter_Exploring
  • 0 in reply to Titusrathinaraj Stalin
    Intellectual 620 points

    This tutorial didn't really help much. I have syslink module installed in Linux on the arm processor. 

    I want to run both messageQ programs on the ARM and DSP at the same time while the ARM is booted into Linux, how do I do this? Since this is an IPC example I referred to the IPC_User_Guide.pdf in the ipc folder, I rebuilt ipc. What do I do next? 

    I also saw the instructions here: 

    but I don't think these apply to ipc_1_25_03_15

    Also, on a unrelated note, if I want to compile a program using the arm-arago-linux-gneuabi toolchain from inside code composer, how do I set it up? I read this:  and it didnt really help.

  • 0 in reply to Usman Majid
    TI__Guru** 116100 points
    Hi,
    What is your kernel version ?
    IPC is later version of SYSLINK. I hope, latest IPC version required higher versions of kernel version which we didn't release, so you may have to bringup new kernel version to use newer IPC3.

    Please refer to the following TI wiki page to use new ARM/DSP compiler in CCS.

    processors.wiki.ti.com/.../Compiler_Installation_and_Selection
  • 0 in reply to Titusrathinaraj Stalin
    Intellectual 620 points

    I am using the latest mcsdk_1_01_00_02 available for the OMAPL138. The only files I added to the package are: xdctools_3_25_06_96 and bios_6_35_06_56 in order to make the IPC examples compile.

    Thanks for that link, do you know if there is a windows version of arm-arago toolchain, because code composer will not detect the linux files.

  • 0 in reply to Titusrathinaraj Stalin
    Intellectual 620 points

    Any ideas? I still haven't figured it out myself.

  • 0 in reply to Usman Majid
    TI__Guru** 116100 points
    Hi,

    Thanks for that link, do you know if there is a windows version of arm-arago toolchain, because code composer will not detect the linux files.


    I've installed "arm-none" toolchain windows version in the following path.

    I've not installed separately as package but got from some TI package.

    Please check yours.

    C:\ti\ccsv5\tools\compiler\gcc-arm-none-eabi-4_7-2012q4\bin

    If not, you can also get the package from code soucery website.
  • 0 in reply to Titusrathinaraj Stalin
    Intellectual 620 points

    Any ideas on the other problem? The toolchain isn't much of a problem as I can cross compile it via terminal to get around that, it is just a convenience factor. The IPC problem is limiting me from using the program while booted in Linux.