• State Resolved
  • Locked Locked
  • Replies 11 replies
  • Answers 4 answers
  • Subscribers 99 subscribers
  • Views 1522 views
  • Users 0 members are here
Support feedback
Options
Options
Related

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/TMS320C6678: Issue Porting Low level library to latest TI RTOS

Balasubramani C
Expert 1685 points
Part Number: TMS320C6678


Tool/software: TI-RTOS

Hi 

I have projects which are created using following tool versions to latest versions of TI Tool set.

CCS v5.5

bios_6_37_02_27

pdk_C6678_1_1_2_6

mcsdk_2_01_02_06

ipc_3_21_00_07

xdctools_3_25_05_94

Now i want to port this project into latest TI tool versions.for which i have installed following versions and changed the tool path to latest version in my project.

CCS v8.1

ti-processor-sdk-rtos-c667x-evm-04.03.00.05-Windows-x86-Install - i assume this SDK contains latest versions of toolset required for project build.

when i build the project, it throws lot of errors on low level library. please find the error snapshots.

am i missing any file path here? this is my include directory.

Regards

Bala

  • 0
    TI__Guru**** 161600 points
    The RTOS team is notified. They will post their feedback directly here.

    Best Regards,
    Yordan
  • 0
    TI__Guru** 116180 points

    Bala,

    The new CSL implementation requires uses to define a symbol( -DSOC_XXX) for indicating on what SOC the CSL library is being used as described here:
    processors.wiki.ti.com/.../Processor_SDK_RTOS_CSL

    In your case, please add the define -DSOC_C6678 to your project. Can you please add the symbol to your Compiler symbol defines and let us know if the issue is resolved.


    Regards,
    Rahul

  • 0 in reply to Rahul Prabhu
    Expert 1685 points

    HI Rahul,

    Rahul Prabhu said:
    The new CSL implementation requires uses to define a symbol( -DSOC_XXX) for indicating on what SOC the CSL library is being used as described here:
    processors.wiki.ti.com/.../Processor_SDK_RTOS_CSL

    I am following the document and will be able run the run the command to build the csl library. but its not building it seems.

    getting following messages.

    and also find the make file commands available in the makefile inside csl directory and it does not contain valid make command it seems.

    include $(PDK_INSTALL_PATH)/ti/build/Rules.make

COMP = csl

lib_$(COMP)_BUILD_DEPENDENCY = soc

$(COMP)_DOXYGEN_SUPPORT = yes

include $(PDK_INSTALL_PATH)/ti/build/comp_top.mk

    can you please help me to get it resolved?

    Regards

    Bala

  • 0 in reply to Rahul Prabhu
    Expert 1685 points

    Hi Rahul,

    Rahul Prabhu said:
    In your case, please add the define -DSOC_C6678 to your project.

    How to do this?

    Bala

  • 0 in reply to Balasubramani C
    TI__Guru** 116180 points

    Bala,

    This seems to an issue with out documentation. The document only seems to indicate how to build CSL examples and not the library itself.

    There are no apps supported inside the CSL folder for C667x devices. The CSL usage is demonstrated in the LLD and the platform library and the IBL bootloader code. So the target app and app_clean doesn`t apply to this device

    To build the CSL libraries for C667x, please follow the steps below:

    cd pdk_c66x_x_x_xx\packages

    pdksetupenv.bat                                  

    //If you have installed SDK in custom directory other than default C:\ti then follow the developers guide for alternate options.

    To clean build CSL library use:

    gmake csl

    gmake csl_clean

    The build will take a while but the clean build step is required only if you have modified the CSL library code and want to update the library. The package comes with these libraries pre-built in the folder: pdk_c667x_x_x_x\packages\ti\csl\lib\C667x\c66\release

    I have shown how to add the -D SOC_C6678 in the CCS project using the screen shot below, let me know if this helps resolve your issue:

  • 0 in reply to Rahul Prabhu
    Expert 1685 points

    Hi Rahul,

    Thank you, Now i will be able to build the library project. but when i build the core project i am ending with the following errors.

    fatal error #6001: cannot open file "C:/ti/pdk_c667x_2_0_9/packages":  Permission denied

    i have tried changing the file permission as suggested in the forum, but it does not get this solved.

    Linker file search path:


     

    expansion of my macros as follows

    C:\ti\bios_6_52_00_12\packages - BIOS_PACKAGE


    C:\ti\xdctools_3_50_07_20_core\packages - XDC_TOOL_PACKAGE

    C:\ti\pdk_c667x_2_0_9\packages - C6000_CSL_ROOT

    C:\ti\ndk_2_26_00_08\packages- NDK_PACKAGE

    C:\ti\uia_2_21_02_07\packages - UIA_PACKAGE

    C:\ti\ipc_3_47_01_00\packages  - IPC_PACKAGE

    if i remove PDK from there, its come with XDC Path is not found.

    if i remove entire file path from linker, then i will be getting unresolved symbols for many of the library file.

    do you have any solution for this?

    Regards

    Bala

     

  • 0 in reply to Balasubramani C
    Expert 1685 points

    Hi,

    as per the forum thread below, its been asked to passing -l option to linker is not correct.

    .

    Please look at the my library are passing with option -l. how do we remove the option -l ?

    Regards

    Bala

  • 0 in reply to Balasubramani C
    TI__Guru** 116180 points
    Bala,

    the option "-l " for the compiler is used to link the libraries and --search_path or -L is used to add the search path for the library for examples if the library bios_elf.lib is located at C:\ti\bios_6_52_00_12 then you need to add

    bios_elf.lib in the CCS Linker settings -l and the path to the library in --search_path option. In your screenshot you have several paths that you have added to -l option, remove that and move them to --serach_path option and this should resolve your issue.

    Regards,
    Rahul
  • 0 in reply to Rahul Prabhu
    Expert 1685 points

    HI Rahul,

    As you suggested I have kept all my library in Linker and added search path for all the library as follows.

    But still I am getting the following errors while building the project. do you have any suggestion for this errors?

    undefined first referenced

    symbol in file

    --------- ----------------

    Osal_qmssAccCsEnter C:\ti\pdk_c667x_2_0_9\packages\ti\drv\qmss\lib\c66\ti.drv.qmss.ae66<qmss_acc.oe66>

    Osal_qmssAccCsExit C:\ti\pdk_c667x_2_0_9\packages\ti\drv\qmss\lib\c66\ti.drv.qmss.ae66<qmss_acc.oe66>

    error #10234-D: unresolved symbols remain

    error #10010: errors encountered during linking; "TRS_appC0.out" not built

    Regards

    Bala

  • 0 in reply to Balasubramani C
    TI__Guru** 116180 points

    Bala,

    You are fairly close to building/porting the project. I am not a QMSS expert so I am not familiar with the dependencies. It appears, you either are missing a library link or source file in the project that provides those two symbols. I did a quick windows search for those symbols and found a file infrastructure_osal.c that contains that symbol. You can try to add that to your project 

    Regards,

    Rahul

  • 0 in reply to Rahul Prabhu
    Expert 1685 points

    HI Rahul,

    Rahul Prabhu said:
    I did a quick windows search for those symbols and found a file infrastructure_osal.c that contains that symbol. You can try to add that to your project 

    Thank you for your timely support. After adding the definitions of those functions to my project, now i will be able to compile all the projects without any errors. 

    i am going for the testing.. hope it should work without any issues.

    Bala