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

Linking a SYS/BIOS application against a custom library that uses SYS/BIOS

BrianBrianBrian
Expert 1085 points

I've tried so many things to try to get this to work and they all failed.  So instead of going through the details of my failed efforts, I will just stick to the original purpose:

I am working with Processor SDK RTOS for AM335x in CCSv6.  I need to write a McASP driver and this driver will refer to components in:

- the EDMA3 LLD driver (a RTSC package)

- SYS/BIOS (also an RTSC package)

Obviously, I would like the McASP driver to be in a separate CCS project from my application project because multiple applications will reuse this driver!  So what are the steps to set this up in CCSv6?

  • 0
    TI__Mastermind 37985 points
    CCS is not really set up to build RTSC library packages. Here is a longer thread with much more details:
    e2e.ti.com/.../297814
  • 0 in reply to Sasha Slijepcevic
    Expert 1085 points

    So that's it?  

    I spent $800 on an IDE just to be told that when I want to reuse code I have to copy it into a new project like an amateur?  Since you are professional developers, I guess that means you are not even using CCS to do serious development then?  That just sounds too ridiculous to me.  So please allow me to reiterate my question in more directed fashion:  

    How do the TI application developers (not the SYS/BIOS developers) create libraries that they can link their applications against?

  • 0 in reply to BrianBrianBrian
    TI__Mastermind 37985 points

    It's not impossible to create a CCS project that generates a library that can be reused in another CCS project. But, it's not meant to be used that way, so any existing solution is ad-hoc and it's hard to debug if something goes wrong. Developers who create libraries that use SYS/BIOS deliver such libraries as RTSC packages, and such packages are mostly built on the command line, like here for example: processors.wiki.ti.com/.../Processor_SDK_RTOS_Building_The_SDK, and then delivered as products that can be installed in CCS.
    All that said, I'll create an example of such an ad-hoc solution and post it to this thread next week.

  • 0 in reply to Sasha Slijepcevic
    Expert 1085 points

    I would prefer to use the tools in the way that they were meant to be used.  So let's take step back.  I do not need the library to be a CCS Project but if its going to live outside of CCS then how do I make the CCS debugger aware of the source code in the external library?  Having to press "Locate File" everytime is a serious time waster.  I have to believe that you are using CCS to do development with SYS/BIOS, what do you do?

  • 0 in reply to BrianBrianBrian
    TI__Mastermind 37985 points

    There are several ways to do that, but I usually got to Window->Preferences->C/C++->Debug->Source Lookup Path->Add... and there you can add directories to search for sources.
    You can also do that in Debug view, go to Run->Debug Configurations..., and then click on Source tab. You can add directories there, and the content of the tab is saved between the sessions.