• State TI Thinks Resolved
  • Locked Locked
  • Replies 3 replies
  • Answers 1 answer
  • Subscribers 52 subscribers
  • Views 692 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/TMDX570LC43HDK: Project and library organization doubt

Etantonio
Intellectual 920 points
Part Number: TMDX570LC43HDK
Other Parts Discussed in Thread: HALCOGEN

Tool/software: Code Composer Studio

Hy,

I would like to create a CCSV7 HalCoGen project to be used by several development groups, concerning this I've the following questions:

1) HALCOGEN_PRJ is a library that contains the files generated by HalCoGen

2) UTILS_PRJ is a library that uses library HALCOGEN_PRJ

3) FTTE_PRJ is a library that uses both HALCOGEN_PRJ and  UTILS_PRJ

4) MAIN_PRJ is the main project that uses all 3 above libraries

I also want that FTTE_PRJ source code in not visible to the MAIN_PRJ development team, instead source code from libraries HALCOGEN_PRJ and  UTILS_PRJ have to be visible,

so I'm a little bit confused about how to structure all, maybe:

A) UTILS_PRJ needs just to reference the projects HALCOGEN_PRJ

B) FTTE_PRJ needs just to reference the projects HALCOGEN_PRJ and UTILS_PRJ

C) MAIN_PRJ  reference the projects HALCOGEN_PRJ and UTILS_PRJ and I copy in it FTTE_PRJ.lib and FTTE_PRJ.h

Could this be a good solution to arrange the projects?

Antonio

  • 0
    TI__Guru**** 173310 points

    Etantonio said:
    Could this be a good solution to arrange the projects?

    Yes this sounds like a good solution.

    If FTTE_PRJ.lib is only linked into the main project and not added as a dependent project, as you suggested, then its source will not be visible in the main project.

  • 0 in reply to AartiG
    Intellectual 920 points

    OK,

    I implemented the solution, at the moment are all referenced project, also FTTE_PRJ,

    I have a problem concerning the linker because it is produced by HalCoGen and so it is inside the HALCOGEN_PRJ,

    in any case using the main Project I can select the linker command file,

    I prefere it is a link to the HalCoGen linker command file instead it is copied in the new project,

    and, in any case, it seems something is not working because when starting the project it jumps to address #00000004 and stops there.

    Any idea about how to solve the problem? The projects are in the zip file NMLV_LinkerProblem.zipattached.

    Thanks,

    Antonio

  • 0 in reply to Etantonio
    TI__Guru**** 173310 points

    Antonio,

    In terms of the set up of projects, the way you have things configured looks ok.

    Etantonio said:
    I prefere it is a link to the HalCoGen linker command file instead it is copied in the new project,

    You can link to the linker command file rather than copying it to the main project, if that is what you prefer.


    Etantonio said:
    and, in any case, it seems something is not working because when starting the project it jumps to address #00000004 and stops there.

    I'm not in the best position to answer this. This would be dependent on your application and whether the linker command file/linker options are set up properly for your application and hardware. I would suggest asking this question at the Hercules device forum as the experts there might have better advice in this regard.