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.

Is C6747 / OMAP-L137 supported in CCS v6?

Other Parts Discussed in Thread: TMS320C6747, OMAP-L137, SYSBIOS, OMAPL138

Hi there, 

I am using OMAP-L137/C6747 Eval board with CCS v3.3. It is working fine and I am able to run all the examples but I want to use TI-RTOS and NDK tools and I think it would be good to use the latest CCS v6. So after installing CCS and when I tried to add XDC tools 3.10.5.61 I am getting an error. 

Now, I am not sure if I have to still use the old version of the CCS v3.3 if not how can use CCS v6?

The error message below is from CCS v6 when I tried to add XDCTools 3.10.

Operation details
Cannot complete the install because one or more required items could not be found.
Software being installed: RTSC/XDCtools 3.10.5.61 (org.eclipse.rtsc.xdctools.feature.group 3.10.5.61)
Missing requirement: Model Plug-in 3.10.5.61 (org.eclipse.rtsc.xdctools.model 3.10.5.61) requires 'bundle org.eclipse.pde.runtime 0.0.0' but it could not be found
Cannot satisfy dependency:
From: RTSC/XDCtools 3.10.5.61 (org.eclipse.rtsc.xdctools.feature.group 3.10.5.61)
To: org.eclipse.rtsc.xdctools.model [3.10.5.61]

I did install the latest version of the XDC tools 3.32.00.06 but then I am not able to target OMAP-L137 or build example related to OMAP-L137

Could someone please help me with this. Thanks.

Regards,

Mitesh

  • Have you tried to create a new RTOS based example on CCSv6 ?

    **** Build of configuration Debug for project C6747_RTOS_Example ****
    
    "C:\\ti\\ccsv6\\utils\\bin\\gmake" -k all 
    'Building file: ../app.cfg'
    'Invoking: XDCtools'
    "C:/ti/xdctools_3_32_00_06_core/xs" --xdcpath="C:/ti/tirtos_c6000_2_00_01_23/packages;C:/ti/tirtos_c6000_2_00_01_23/products/bios_6_40_01_15/packages;C:/ti/tirtos_c6000_2_00_01_23/products/ipc_3_10_01_11/packages;C:/ti/tirtos_c6000_2_00_01_23/products/ndk_2_23_01_01/packages;C:/ti/tirtos_c6000_2_00_01_23/products/uia_2_00_00_28/packages;C:/ti/ccsv6/ccs_base;" xdc.tools.configuro -o configPkg -t ti.targets.elf.C674 -p ti.platforms.evm6747 -r release -c "C:/ti/ccsv6/tools/compiler/ti-cgt-c6000_8.1.0" --compileOptions "-g --optimize_with_debug" "../app.cfg"
    making package.mak (because of package.bld) ...
    generating interfaces for package configPkg (because package/package.xdc.inc is older than package.xdc) ...
    configuring app.xe674 from package/cfg/app_pe674.cfg ...
    generating custom ti.sysbios library makefile ... 
    Starting build of library sources ...
    making C:/Users/10607926/workspace_v6_1/C6747_RTOS_Example/src/sysbios/sysbios.ae674 ...
    gmake[1]: Entering directory `C:/Users/10607926/workspace_v6_1/C6747_RTOS_Example/src/sysbios'
    cle674 C:/ti/tirtos_c6000_2_00_01_23/products/bios_6_40_01_15/packages/ti/sysbios/BIOS.c ...
    "C:/ti/tirtos_c6000_2_00_01_23/products/bios_6_40_01_15/packages/ti/sysbios/knl/Semaphore.c", line 234: remark #2142-D: comparison between signed and unsigned operands
    "C:/ti/tirtos_c6000_2_00_01_23/products/bios_6_40_01_15/packages/ti/sysbios/timers/timer64/Timer.c", line 775: remark #2142-D: comparison between signed and unsigned operands
    asme674 C:/ti/tirtos_c6000_2_00_01_23/products/bios_6_40_01_15/packages/ti/sysbios/family/c64p/Hwi_disp_always.s64P ...
    asme674 C:/ti/tirtos_c6000_2_00_01_23/products/bios_6_40_01_15/packages/ti/sysbios/family/c64p/Hwi_asm.s62 ...
    asme674 C:/ti/tirtos_c6000_2_00_01_23/products/bios_6_40_01_15/packages/ti/sysbios/family/c64p/Hwi_asm_switch.s62 ...
    asme674 C:/ti/tirtos_c6000_2_00_01_23/products/bios_6_40_01_15/packages/ti/sysbios/family/c64p/Clobber_asm.s62 ...
    asme674 C:/ti/tirtos_c6000_2_00_01_23/products/bios_6_40_01_15/packages/ti/sysbios/family/c64p/Exception_asm.s64P ...
    asme674 C:/ti/tirtos_c6000_2_00_01_23/products/bios_6_40_01_15/packages/ti/sysbios/family/c64p/MemoryProtect_asm.s64P ...
    asme674 C:/ti/tirtos_c6000_2_00_01_23/products/bios_6_40_01_15/packages/ti/sysbios/family/c62/TaskSupport_asm.s62 ...
    asme674 C:/ti/tirtos_c6000_2_00_01_23/products/bios_6_40_01_15/packages/ti/sysbios/timers/timer64/Timer_asm.s64P ...
    asme674 C:/ti/tirtos_c6000_2_00_01_23/products/bios_6_40_01_15/packages/ti/sysbios/timers/gptimer/Timer_asm.s64P ...
    asme674 C:/ti/tirtos_c6000_2_00_01_23/products/bios_6_40_01_15/packages/ti/sysbios/timers/dmtimer/Timer_asm.s64P ...
    are674 BIOS.obj c64p_Hwi_disp_always.obj c64p_Hwi_asm.obj c64p_Hwi_asm_switch.obj c64p_Clobber_asm.obj c64p_Exception_asm.obj c64p_MemoryProtect_asm.obj c62_TaskSupport_asm.obj timer64_Timer_asm.obj gptimer_Timer_asm.obj dmtimer_Timer_asm.obj ...
    gmake[1]: Leaving directory `C:/Users/10607926/workspace_v6_1/C6747_RTOS_Example/src/sysbios'
    Build of libraries done.
    cle674 package/cfg/app_pe674.c ...
    'Finished building: ../app.cfg'
    ' '
            1 file(s) copied.
    making ../src/sysbios/sysbios.ae674 ...
    gmake[1]: Entering directory `C:/Users/10607926/workspace_v6_1/C6747_RTOS_Example/src/sysbios'
    gmake[1]: Nothing to be done for `all'.
    gmake[1]: Leaving directory `C:/Users/10607926/workspace_v6_1/C6747_RTOS_Example/src/sysbios'
    'Building file: ../main.c'
    'Invoking: C6000 Compiler'
    "C:/ti/ccsv6/tools/compiler/ti-cgt-c6000_8.1.0/bin/cl6x" -mv6740 --abi=eabi --include_path="C:/ti/ccsv6/tools/compiler/ti-cgt-c6000_8.1.0/include" -g --define=omapl137 --diag_warning=225 --diag_wrap=off --display_error_number --preproc_with_compile --preproc_dependency="main.pp" --cmd_file="configPkg/compiler.opt" "../main.c"
    'Finished building: ../main.c'
    ' '
    'Building target: C6747_RTOS_Example.out'
    'Invoking: C6000 Linker'
    "C:/ti/ccsv6/tools/compiler/ti-cgt-c6000_8.1.0/bin/cl6x" -mv6740 --abi=eabi -g --define=omapl137 --diag_warning=225 --diag_wrap=off --display_error_number -z -m"C6747_RTOS_Example.map" --heap_size=0x800 --stack_size=0x800 -i"C:/ti/ccsv6/tools/compiler/ti-cgt-c6000_8.1.0/lib" -i"C:/ti/ccsv6/tools/compiler/ti-cgt-c6000_8.1.0/include" --reread_libs --define=DSP_CORE=1 --diag_wrap=off --display_error_number --warn_sections --xml_link_info="C6747_RTOS_Example_linkInfo.xml" --rom_model -o "C6747_RTOS_Example.out" "./main.obj" -l"configPkg/linker.cmd" -l"libc.a" 
    <Linking>
    'Finished building target: C6747_RTOS_Example.out'
    ' '
    
    **** Build Finished ****
    

    C6747_RTOS_Example.zip

  • Hi Titus, thanks for your email.
    No I am not able to create the example based on RTOS on ccs v6. When I go to File, New CCS Project I cannot find EVMOMAPL137 in the target list. Could you help me with that first? is it to do with XDCtools versions? thanks.
    Mitesh
  • This is what error message I got, when I tried to import your attached project and tried to open app.cfg file.

    Thanks.

    Mitesh

  • Can you tell me what version of the SYS/BIOS should I install in order to get targets files for OMAP-L137 / TMS320C6747 ? thanks.
  • Mitesh Hiran said:
    Can you tell me what version of the SYS/BIOS should I install in order to get targets files for OMAP-L137 / TMS320C6747? thanks.

    SYS/BIOS 6_45_01_29 supports the OMAP-L137:

  • Hi, thanks for your reply. Do I need to install BIOS PSP to get the header files for the C6747 board? 

    Is BIOSPSP v1.30.0.5 supports to SYS/BIOS or should I install BIOS PSP v3.1.1.0 ? 

    Thanks.

    Mitesh

  • If you look into my screen shot, just I have installed the TI RTOS of C6000 installed and it has the support for all the required dependency packages (IPC,SYSBIOS,XDCtools etc.,) .

    software-dl.ti.com/dsps/dsps_public_sw/sdo_sb/targetcontent/tirtos/2_00_01_23/exports/tirtos_c6000_setupwin32_2_00_01_23.exe

    software-dl.ti.com/.../index.html
  • Hi Titus, thanks I will install from the link. But it recommends to install from CCS App Center but I can't find TI RTOS C6000 in it?
  • Do you think, the CSL package will also be installed as part of TI-RTOS v2.0.1.23?
    Thanks
    Mitesh
  • Nope, you can install the TI-RTOS package directly using *.exe file.
    You need to download the CSL package separately.


    Do I need to install BIOS PSP to get the header files for the C6747 board?

    Is BIOSPSP v1.30.0.5 supports to SYS/BIOS or should I install BIOS PSP v3.1.1.0 ?

    BIOS PSP is legacy packages so you may need to install particular version of SYS/BIOS or DSP/BIOS which are mentioned in release notes of BIOS PSP, so please check.
  • Okay. I am a bit confused now. Is there any way I can call you? or you can?
    Are you saying, TI-RTOS v2.0.1.23 is supported for C6747/OMAPL137 and when I install TI-RTOS it will install particular version of NDK, SYS BIOS, etc. But if I have to use BIOS PSP then I will have to install different version of SYSBIOS ?

    So would the TI RTOS still be the entity and different version of the SYS BIOS, are installed in it? I was under the impression that to use the peripherals like timer, GPIO, etc we have to use the chip support library? but now it sounds like that is the old way of doing it? so what is the current trend, drivers?
  • Okay, understood now.
    Sorry we don't have new SYSBIOS or BIOS driver code for C6747/OMAPL137 devices and also it has very limited source code available but OMAPL138 does.
    OMAPL138 has starterware and SYSBIOS examples.


    Are you saying, TI-RTOS v2.0.1.23 is supported for C6747/OMAPL137 and when I install TI-RTOS it will install particular version of NDK, SYS BIOS, etc. But if I have to use BIOS PSP then I will have to install different version of SYSBIOS ?

    It will support for creating code for C6747/OMAPL137 but doesn't has driver code, you may need to develop on your own.


    ]
    So would the TI RTOS still be the entity and different version of the SYS BIOS, are installed in it? I was under the impression that to use the peripherals like timer, GPIO, etc we have to use the chip support library? but now it sounds like that is the old way of doing it? so what is the current trend, drivers?

    Yes, you need to use older PSP BIOS based code, you can try to use it with latest BIOS. (kind of porting stuff may required)