• State TI Thinks Resolved
  • Locked Locked
  • Replies 4 replies
  • Answers 1 answer
  • Subscribers 100 subscribers
  • Views 458 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.

CCS5 and CSL2.5 and CSL3

Todd Anderson78572
Guru 14640 points

All:

I have a EVM5505, which contains a VC5505 processor.

I can build and run examples from the examples of CSL 2.5, but it requires that I first build the cslVC5505 "library" AND have that library in the same workspace as the example that I am building. Recently I built the GPT example, and unless the cslVC5505 library was built and in the same workspace, the GPT example would not even build.

I was then able to point at the C5505EVM_OnboardEmulator.ccxml file and use that to load and run the example.

NOT so with the CSL 3.0 examples.

First, there is a requirement to also include the "atafs driver library." For what reason? I do not know.

So, to build the same GPT example under CSL 3.0, I need to first build the atafs library, Then build the cslVC5505 library, and then build the GPT example.

However, when I try to load, I first received an error about GEL file; when I ran the example, the GPT test failed.

 

I am not sure that I have seen documented anywhere the build process that I have described.

And Why does CSL 3.0 also require the atafs driver library to be included?

I am trying to move from CSL 2.5 to CSL 3.0, but it is very difficult...

 

  • 0
    TI__Mastermind 23785 points

    Since you are using VC5505, you need to stay with CSL2.50. This is in the CSL3.0 Release Note:

    "Starting with this version of the CSL, the TMS320VC5504/05 DSPs will no longer be supported. For
    support, refer to CSL version 2.50.00. Any pre-existing examples from CSL 2.50.00 will still work on
    VC5504/05 DSPs, including bug fixes. However, any new examples will not have the option for
    VC5504/05 DSPs. The chip definitions have been taken out of csl_general.h file, but the examples
    will still work when using the previous csl_general.h files."

    Hope this help.

    Regards.

  • 0 in reply to Steve Tsang
    Guru 14640 points

    Steve:

    Thanks.

    One thing I think should be done on CSL 3.0 - rename the library from vc5505.lib to c55xx.lib to avoid confusion. Also, when building the examples, clearly state that the following libraries need to be added to the workspace - the "vc5505.lib" and the "atafs driver lib."

    By the way, Why does the atafs lib need to be added, when that was NOT a requirement when building the CSL 2.5 examples?

    I have managed to run on a C5505 target with the GPT example. I found that to do so, I needed to do the following:

    1. Make sure that the csl_general.h file had a definition for the C5505_C5515.

        The line defining was         #define CHIP_C5505_C5515    just having   #define CHIP_C5505  did NOT work.

    2. Added vc5505 library to the example workspace. (Even though vc5505 is NOT used, the library must be built and added.)

    3. Added atafs_bios_drv_lib to the example workspace.

    4. Added CSL_GPT_Example_Out to the example workspace.

    5. Under project, I did "Clean" and complete rebuild - no errors.

    6. Because I am using an XDS100 to load into my C5505-based target board, I had to associated a user-defined XDS100.ccxml file with the project. Then inside the project, I needed to make sure that the XDS100.ccxml file was "default/active"

    After that, the GPT example DID work on my C5505-based target board. I am having problems right now with the PLL example, though. (That worked on the CSL 2.5, but appears to be hanging somewhere inside the CSL 3.0 code.)

  • 0 in reply to Todd Anderson78572
    TI__Prodigy 225 points

    Hi Todd,

    Glad to see that you were able to get the GPT example working with CSL 3.01.

    I have provided some code in your other thread regarding PLL for getting proper system clock. If you are facing any other issue with the PLL example, please let us know the details.

    Regards,

    Rahul Nair

  • 0 in reply to Todd Anderson78572
    TI__Intellectual 1755 points

    Todd, 

    To answer a couple more of your questions:

    - A bug has been filed to rename the cslVC5505.lib to avoid confusion. It will be implemented in a future release of the CSL

    - The atafs lib needs to be added because the cslVC5505.lib depends on it (you can see in the settings of the cslVC5505 project). Some of the new features of CSL require it.

    - On the release notes, it says to run projects on C5504/05/14/15, the #define on csl_general.h should be #define CHIP_C5515 (or #define CHIP_C5505_C5515 as you noticed). There is not an option for CHIP_C5505 only.