• State Resolved
  • Locked Locked
  • Replies 6 replies
  • Subscribers 31 subscribers
  • Views 313 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.

MSP430-SDK: CCS V20 - importing projects from earlier versions failure

ANDREW JAMES
Prodigy 50 points

Part Number: MSP430-SDK

Hello, it has been a few years since I have used CCS and I remember creating and importing projects etc and it was awful so I was hoping the new clean looking V20 will be an improvement.....its not :-(

Cutting a long story short I am only trying to import a CCS projects from an earlier version (I dont know which).   This project did build in the older verion used.

The import appeared to work until I hit "rebuild" and it appears in the import process it lost where many of the projects include path(s) are. 

I found a settings menu I could enter all these paths into but this reduced the number of build errors but it was still complaining about missing .h files despite being told where they are.

I now cannot find that menu screen I manually entered these paths into which is even more fustrating.  Im sure even if these include paths were found there will yet more reasons why it cant build a valid project!

Q1 Is there a way to import older projects without loss of important settings?

Q2 what menu/settings/preferences screen should I use to manually enter project inlcude paths?

Thanks

  • 0
    TI__Mastermind 26212 points

    Hi Andrew,

    1. Sadly, I think you'll have to manually set certain paths if the original project had special path routing

    2. Let me consult with my team about this.

    Best Regards,

    Diego Abad

  • 0 in reply to Diego Abad Sajamin
    Prodigy 50 points

    Hello Diago,

    FYI I have abandoned V20 in preference for the older V6 as I believe this was originally used although this isnt without issues either.

    In V20 I did find a screen to manually enter the file paths then tried rebuilding.  The build failed complaining about file paths it should now be able to find, but when I went back to check I entered all the paths required the listbox was empty (hence why I was confused I couldnt find the correct screen again).  This 'path amnesia' is why I have abandoned V20 for now.

    V6 doesnt have this 'file path amnesia' but instead is failing to build and reports "error #10016-D: --abi=coffabi not supported when producing ELF output files  fatal error #10011: cannot continue with specified options; aborting" suggesting its trying to mix .elf and .COFF files despite the project settings specifying the final output to be a .coff to match a .lib file which is apparently a .coff. 

    V6 is painfully slow to build and only at the end does it report error which I realize may not be the true fault anyway :-(

  • 0 in reply to ANDREW JAMES
    TI__Mastermind 26212 points

    Hi Andrew,

    There might be a chance that using V12 can help since it it the latest CCS Eclipse IDE we released.

    Best Regards,

    Diego Abad

  • 0 in reply to Diego Abad Sajamin
    Prodigy 50 points

    Hello Diego, I have installed V12 and the first problem is it wont even open/import an existing project so the chances of it compiling it less than zero!

    Quite why the project open menu item is called "import" has always worried me, but it can see there is a CCS project in the folder I nominated but denies me the option to select it:

  • 0 in reply to ANDREW JAMES
    Prodigy 50 points

    I have worked out why CCS12 wont let me open a valid project......it quietly opened it on start up but there's a UX bug where the user is totally unaware of this this (where the project explorer vanished from view) and then cant reopen it.  Odd, as most GUI apps allow users to reopen a documents etc, but anyway......

    V12 compiles much faster but still fails with the same cryptic error:

    driverlib_small_CCS.lib   exists as a real file and maybe COFF rather than ELF (i cant easily tell)

    HAL_FLASH.obj   doesnt exisit as a file at all

    It appears if the compiler cant find HAL_FLASH.obj and assumes its an ELF as a result gives a fake compile error

  • 0 in reply to ANDREW JAMES
    Prodigy 50 points

    I have managed to get the project to compile by setting any project settings mentioning to ELF format to COFF  - I cant now remember which ones after ChatGPT had me try virtually all settings combinations possible Open mouth