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

LP-MSPM0G3519: warning: archive symbol directory is missing from archive

Kiran Kumar Sevana
Prodigy 60 points

Part Number: LP-MSPM0G3519

Tool/software:

Hello Team,

While linking, i am facing the following warning "warning: archive symbol directory is missing from archive".

Also i have gone through the other  thread - https://e2e.ti.com/support/tools/code-composer-studio-group/ccs/f/code-composer-studio-forum/1057190/error-archive-symbol-directory-is-missing-from-archive

but not found any solution. Can you please assist to resolve.

SDK version i am using - mspm0_sdk_2_03_00_07

Micro - MSPM0G359

  • 0
    TI__Genius 16050 points

    Hi Kiran,

    What tool are you using to get this output? Also what are you trying to do?

    I am not clear on the setup here so please indicate the steps you take to get this behavior so we can start root-causing the issue.

  • 0 in reply to Dylan OBrien
    Prodigy 60 points

    I am using cmake to compile the code. I am trying to compile my application by including the SDK driverlib and devices files. The cmake generates the libraries (libstartup.a and libplatformstub.a) as you see in the image. Finally i am generating the .ELF file by linking all these libraries. During linking i am getting this warning. Is it something to do with tiarmar ? where its failed to identify the library location?  

  • 0 in reply to Kiran Kumar Sevana
    TI__Genius 16050 points

    I see. Unfortunately we do not have any documentation or guidance for using cmake with our SDK. Looking at the information here I am not clear on what the exact issue is. I would recommend taking a look at the cmake documentation to help resolve the issue.

**Attention** This is a public forum