• State Resolved
  • Locked Locked
  • Replies 5 replies
  • Subscribers 54 subscribers
  • Views 1857 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.

CCS/TMS320C5515: Chip Support Library installation and #10234-D: unresolved symbols remain error

Denn
Prodigy 230 points
Part Number: TMS320C5515


Tool/software: Code Composer Studio

Hi all, this is the first time I am doing this and I am sorry if I am doing something stupid here (probably I am). I am kind of lost and any help will be appreciated.

I am working on TMS320C5515, both EVM and custom board and using CCSv6.1.2 on Win7. I am using the linker given in the link, which enables the use of printf, in case you need to know; https://e2e.ti.com/support/development_tools/code_composer_studio/f/81/p/215845/761954

I have been trying to integrate Chip Support Library 3.07 to my project. I followed the installation instructions for C5515 in C55XCSL-LOWPOWER-3.07.00_Installation_Guide.pdf and managed to load the ccxml file and set it as default, seen under the target configurations, and also to load the .gel file. The next steps in the instructions include the example projects for the silicon. I have imported them but I couldn’t have run them and it has not been enough to include the headers from CSL..

I tried to follow the instructions in these in links http://processors.wiki.ti.com/index.php/Include_paths_and_options and http://processors.wiki.ti.com/index.php/Portable_Projects#Portable_Projects_in_CCSv6

I have created a new build variable called COMMON_ROOT and used it to include header and source files from the CSL in the Include Options. Then on, I can include the headers in my code. However I cannot call functions. When I do so I get the error #10234-D: unresolved symbols remain.

I also tried to “Add Files” by right clicking on the project. It makes add the header and source files without any folder, they appear under my main.c and this also did not work. I am missing something and will be happy if you can please point out what it is.

 

 

 

 

 

 

 

 

  • 0
    TI__Guru**** 472221 points

    Denn said:

    I have created a new build variable called COMMON_ROOT and used it to include header and source files from the CSL in the Include Options. Then on, I can include the headers in my code. However I cannot call functions. When I do so I get the error #10234-D: unresolved symbols remain.

    I also tried to “Add Files” by right clicking on the project. It makes add the header and source files without any folder, they appear under my main.c and this also did not work. I am missing something and will be happy if you can please point out what it is.

    That error you are seeing has nothing to do with header files or include header file search paths. It is a linker error telling you that it cannot fine the object file / library that contains _SYS_setEBSR.

    more details on the meaning of the error is documented in:

    http://processors.wiki.ti.com/index.php/Build_Errors_in_CCS#Error:_unresolved_symbols_remain

    Where is that symbol defined in your application? You need to make sure the source file for it is part of your project or you are pulling in the library that has it.

    Thanks

    ki

  • 0
    Prodigy 230 points

    Hi Ki,

    Thanks for your response. I am trying to overcome the problems one by one until I get the CSL working fine in my project.

    I have now added the source files (right click Add Files, select all the source files and copy them) into the project directory. Then I dragged and dropped them into the src folder to tiny up the directory. _SYS_setEBSR can now be found by the linker.

    Having added the source files brought me new problems. The first problem is I2C_read function in the csl_i2c_ioExpander.c, which I have solved. The solution is given here; e2e.ti.com/.../486861

    The other problem is the assembly (.asm) files, they gave more than 100 errors. I have searched and found that changing assembly source language in Runtime Model Options from mnemonic to algebraic solves this problems. processors.wiki.ti.com/.../C5000_DSP_FAQ

    Another problem is the log.h file. csl_hid.c includes log.h however, this file cannot be found, as seen under the Problems Tab. The only log.h files I could have found are in the xdctool folders, which I believe are used for DSP/BIOS (I am not using it DSP/BIOS). I am wondering whether this problem is because of the location of my workspace. My workspace is in E:\Texas\c55_csl_3.07 (as told in the CSL 3.07 installation guides) and log.h files are in E:\Texas\xdctools_3_32_00_06_core\packages\xdc\runtime  and E:\Texas\xdctools_3_31_00_24_core\packages\xdc\runtime.

    If I am not using BIOS, does it hurt to remove csl_hid.c from the project?

    Can you please comment on this problem as well?

    P.S: I am sharing the solutions with sources here to ease the things for others. Once I get CSL working I will write up every single step I took to integrate it in one single post.

  • 0 in reply to Denn
    Prodigy 230 points
    anyone?
  • 0 in reply to Denn
    TI__Guru**** 472221 points

    Hi Denn,

    Sorry for the delay in response.

    Denn said:

    Another problem is the log.h file. csl_hid.c includes log.h however, this file cannot be found, as seen under the Problems Tab. The only log.h files I could have found are in the xdctool folders, which I believe are used for DSP/BIOS (I am not using it DSP/BIOS). I am wondering whether this problem is because of the location of my workspace. My workspace is in E:\Texas\c55_csl_3.07 (as told in the CSL 3.07 installation guides) and log.h files are in E:\Texas\xdctools_3_32_00_06_core\packages\xdc\runtime  and E:\Texas\xdctools_3_31_00_24_core\packages\xdc\runtime.

    If I am not using BIOS, does it hurt to remove csl_hid.c from the project?

    Can you please comment on this problem as well?

    log.h is a BIOS header file. Same with sem.h, mbx.h, swi.h, task.h, etc. I installed the CSL and there is a strong dependency with DSP/BIOS (v5.42.02.10). If you don't have it installed (it doesn't come with CCSv6 by default), you will need to install it. A link to it is available from the CCS App Center.

    As for your question about not using BIOS and removing the csl_hid.c from your project, I don't know the impact. They may be other BIOS dependencies. I would post in the C5000 forum. The experts there will be more knowledgeable with the CSL and its dependencies.

    Thanks

    ki

  • 0 in reply to Ki
    Prodigy 230 points
    For others who are having the same problems; the rest of the solution is here:

    e2e.ti.com/.../585355


    Thanks.