• State Resolved
  • Locked Locked
  • Replies 4 replies
  • Subscribers 52 subscribers
  • Views 515 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 V5 convert from V4 Unresolved Symbol In Simpliciti demo V1.1.1

InnoPlay
Prodigy 130 points

Other Parts Discussed in Thread: SIMPLICITI, CC430F5137, CC430F6137

I loaded up CCS V5 and loaded in a Simpliciti Demo application. The Simplicity version is 1.1.1. Everything seems to work fine. I loaded the .OUT file into my target boards and they seem to communicate to each other.....however in the Project tree, under Applications (where the source happens to fall), it shows I have unresolved references in the 2 files that exist. The references happen to be P1OUT, P1IN, ....which I know are located in the device files.... the error will only pop up after I load the files in the editor window and then of course a small red X is displayed in the project tree by each folder and file.......I'm not understanding what kind of checking is being done at what seems to be a pre-compile ...state....any thoughts??

 

Regards,

 

John

  • 0
    TI__Guru*** 130875 points

    Hi John,

    it seems like when importing/migrating some include paths got broken or are no longer correct/there.

    Please double check these.  The following wiki will help you to do that.  Please keep us informed.

    http://processors.wiki.ti.com/index.php/Include_paths_and_options


    Simply loading a .out is of course expected to work as not files need to be linked or built.

    Best Regards,
    Lisa

  • 0 in reply to Lisa TI
    Prodigy 130 points

    Lisa,

     

    Thanks, I'll look around a bit...I looked hard at the includes and paths and such.....to be clear....I rebuild the whole project and I get no errors and a new .out is created and I loaded that into the development system.....its just in the editor enviroment that I get the error...

    What is throwing me off is the error at the editing point....seems like the reference to the file cc430f5137.h should be done at compile time......

    So to get rid of the error I just added an include of the file at the top of main and everything is hunky dorry....but I want to understand it....

    Where are the follwoing bold literals defined defined?   (a couple years ago I thought I needed to add them on the compile command line)...but again...my error seems to be before compile.......its weird to me...

    /* ---------------------- Code Composer ---------------------- */

    #elif (defined __TI_COMPILER_VERSION__) && (defined __MSP430__)

    #define BSP_COMPILER_CODE_COMPOSER

    /* At time of 1.1.0 release, CC430 support not in msp430.h */    <---- it looks like it is supported to me now but needs the literal __CC430F5137__  to be defined

    #if (__CC430F6137__)

    #include <cc430x613x.h>

    #else

    #include <msp430.h>

    #endif

     

    Thanks,

    John

  • 0 in reply to InnoPlay
    Prodigy 130 points

    I'm going to reply to my own post...I searched the world over and did some re-installing to no real solution. However, I decided that the amount of indirection might just be too much for Eclipse to handle so I went into editor prefrences and unchecked a few things.....I'm old school so I'll let the compiler and linker find certain errors.

    I will also say that I did this because __interrupt was throwing an error and I found a forum response to that in the same effect...

    Finally, as I open up some of Simpliciti's files such as BSP.c.....I got errors in those for not being able to resolve TYPEs of some indirected literal functions....

    Time to move on.....the code works....

    Regards,

    John

  • 0 in reply to InnoPlay
    TI__Guru*** 130875 points

    Hi John,

    ok, glad you are happy enough that the code is running.  I am unfortunately no compiler expert but I believe the two highlighted definitions you refer to are compiler macros. 

    It seems from your initial post you simply had a couple path or build variables broken.

    At any rate, glad you have working code and all the best with development.

    Best Regards,

    Lisa