• State TI Thinks Resolved
  • Locked Locked
  • Replies 3 replies
  • Answers 1 answer
  • Subscribers 80 subscribers
  • Views 305 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.

MSP430FR2355: main application jumps to wrong library source files when F3 Focus hit in CCS

Steve Wenner
Genius 3240 points
Part Number: MSP430FR2355


I have posted this in the compiler forum but decided to post here as well as that forum tends to not be monitored as much.......

CCS V10.0.0.00010

I have a library created for a project.

I then have a separate main application area where I am creating code.  In the main application I include <Project - Properties - MSP430 Linker - File Search Path> and point it to my library (.lib).  I also point <Project - Properties - MSP430 Compiler- Include Files> it to my header folder within the library of interest.

If I hit the F3 Focus within the application I automatically jump to another library that has very similar code but slight modifications.  Can someone tell me what I am missing?????  How do I break the compiler link so that it stops focusing on the one library and instead focuses on the one I want?

Thanks

  • 0
    Guru 100845 points

    Are you fairly certain that your executable contains the new library, not the old one? You wouldn't be the first to accidentally do this. In a pinch: Rename the .lib file (in the file system, not in CCS), rebuild the project, and see what happens.

    Beyond that, I'll just observe that CCS (really Eclipse) is a strange monster [but it's so useful!] with control information all over everywhere. The CCS Forum is watched by people who really know all this stuff, and appear to be very responsive.

    https://e2e.ti.com/support/tools/ccs/f/81

  • 0 in reply to Bruce McKenney
    Genius 3240 points

    Yes I am pretty sure.....The linker location is pointed at the 'new' library that I want to use.  .....The compiler include is pointed at the 'new' library I want to use....

    I believe that is all the pointers needed.  I think I will delete the compiler pointer, build and have it break then try and re-associate by adding back in the header folder into the compile include area.

    The confusion I believe is because I ran into some issues in the application so out of frustration I created a 'junk' application project and a 'junk' library project and copied all the files from the 'real' application / library over.  hence they all have the same name just different locations now.....Unfortunately for me within the 'junk' I found issues,  began to fix them and well.....now that has become my goto vs the old 'real' location.

  • 0 in reply to Steve Wenner
    Guru 100845 points

    By "fairly certain" I was thinking about something like looking for something distinctive about the new library (character string, function name, code sequence) in the new executable.

    In extremum, create a new project and copy the contents (in the file system). I've seen people "fix" things many times by doing this -- presumably they accidentally made some arcane setting, and creating a new project was quicker than finding it.

    I say "in the file system" since once I used Eclipse (I don't recall if it was CCS) to copy files from one project to another, and it created links instead, so modifying one file implicitly modified the other. I'm sure it was trying to Improve My Life. I don't do that any more.

    [Edit Minor wording fix]

**Attention** This is a public forum