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.

LAUNCHXL-CC26X2R1: New error, not sure why it cropped up after 2 years of working with the SDK?

Part Number: LAUNCHXL-CC26X2R1

Hi All,

I have a new undefined error on two calls from Main() start up that have compiled right up do now?

Now sure if I butter fingered something or fell asleep at the keyboard and caused this.

Here is the compile results, two "undefined" items which are calls that are in vims.h and should

be satisfied in the build.  The build finishes, no undefined in the link stage.  I tel it to proceed

and flash the MCU and the code runs find, well seems to.  I hate to go forward with any errors

like this being left there.

VIMSConfigure and VIMSModeSet both pop up undefined? (red line under them).

vims.h is still fine and there where it should be, in the SDK folders.

Later in another module (same include files) I use this call and it is ok, defined as such:

I'm not sure what gives, VIMSModeSafeSet() is fine but the other two are now giving an error.

I know this has something to do with ROM vs. NOROM builds and I haven't touched any of those

defines or settings since I first grabbed the Project_One code base a couple of years ago.

Please point me what to check to find the root cause of this surprise error?

Thanks in advance, Marc

  • Hi,

    diff compare the code from the original.

    -kel

  • Hello Marc,

    I hope you are doing well! Similar to what Kel recommended, can you do a compare of the code? Can you also provide your SDK version, CCS version, and if your device is a custom board or a launchpad? 

    -Did you change anything recently that you think would cause an issue? like updating CCS, changing tools, changing laptops, etc. 

    Thanks,
    Alex F

  • Thanks for the look, I ran KDiff on a back up folder vs. current one with this small error

    and really didn't turn up anything that would sniff out the issue?  Weird this popped up?

  • SDK: /ti/simplelink_cc13xx_cc26xx_sdk_6_30_01_03

    CCS: Version: 12.3.0.00005 

    I did a full diff of a back up version and this really didn't point to anything unusual that I didn't expect to change do to debug/edit/compile operations.

    I have the include still valid to reach the "vims.h" file which has definitions for these to functions.

    I will recover a back up version that didn't have this and build that to see if something flipped in my CCS installation and/or the SDK I guess.  Time consuming step but I feel my call out to see if anyone had this similar error pop up might be a quick answer.  I'll post what I find.

  • If the compare did not show any changes, then it could be the project not recognizing all files within it maybe? For example, try searching (ctrl + h, do C/C++ search) for "VIMSConfigure", then make sure its define or file is included; then possibly do a re-define of it to see if the project recognizes it. Also try to do a full clean/re-build of the project to see if that helps.  

    Thanks,
    Alex F

  • Hi, I recovered a previous back up version and imported and it builds fine.  Those two VIMS.H items are resolved.  So I did some mystery thing to the newer version which tickled those somehow.

    I did the full compare/diff include .syscfg files hoping to see something pop up.  A full clean and build also, etc.  Sometimes it helps to delete everything in the 'debug' folder your building into as I have see some of those items held on to something which affects a future build, all that comes back when 'build project' is ticked again any ways but freshened up.

    I'll keep on it as I don't like to ignore warnings/errors.  Funny thing, the build won't flash when done as usual but rather does the 'you have errors' dialog at which I click 'proceed' it flashes and seems to run fine.  Also the linker never kids out any undefined stuff?  Strange one, they are actual ROM routines any way but why I get this compile time error is strange when it is going to work any ways?

    I gather no one else has seen a similar error as I was hoping to save time.  But with an old one that works and compare to the new one I should find it soon.  We are near finale code and release time and don't need time consumers like this cropping up, oh drat.

    Back to 'diff' and the sleuthing...

  • Hmm, still wondering about this.  I got by the errors, which the editor after compile says are "type" errors, rather than undefined.

    I got by the situation by changing to what vims.h has in it with this code:


      // Enable iCache prefetching
        ROM_VIMSConfigure(VIMS_BASE, TRUE, TRUE);

      // Enable cache
        ROM_VIMSModeSet(VIMS_BASE, VIMS_MODE_ENABLED);

    Which is what the defines there do is translate to ROM_ versions of the functions and

    this builds with no warnings.  Really strange.  In the same workspace I build the previous

    version and it has no complaints?  I am wondering if I messed somehow with the define

    which selects ROM_ or NOROM_ versions of library calls to use? 

  • Hello Marc,

    We do have a webpage with details a bit about CCS errors: Project Import and Build errors in CCS

    Really strange.  In the same workspace I build the previous

    version and it has no complaints? 

    -Sometimes when you build the project it may not build the code in the expected order which may explain the warnings. You could play around with the optimization level. 

    Thanks,
    Alex F

  • I know what your hinting at, have seen simular.  I do a clean and full build often to see if all is well.

    I will stick with the things I copied out of vims.h to my header file as it completes and goes into the flash step now.  Don't want to spend more time on exactly what caused this to occur as I'm porting over to a new WiFi version of the MCU any way.

    Thanks all.