• State Resolved
  • Locked Locked
  • Replies 7 replies
  • Subscribers 52 subscribers
  • Views 1318 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 5.1.1 build/Debug problem/Could not write metadata

Sabina Greenberg101872
Expert 2780 points
Other Parts Discussed in Thread: SYSBIOS, TMS320F28035

Hi,

I working with Piccolo device TMS320F28035/CCS 5.1.1.00031 / compiler c2000_6.0.3/SysBios 6_33_03_33

I get the following messages when try to build/debug an application(any example from SYSBIOS also):

Could not write metadata for '/TestGuiLib'.
..\workspace_v5_1\.metadata\.plugins\org.eclipse.core.resources\.projects\TestGuiLib\.markers.snap (The system cannot find the path specified)

directory ..\workspace_v5_1\.metadata\.plugins\org.eclipse.core.resources\.projects\TestGuiLib doesn't exist. ShouldI create it ?

Could you help me with it? 

Thanks,Sabina

 

  • 0
    TI__Guru*** 130875 points

    Hi Sabina,

    Do you have full admin privileges?  What OS are you running CCS on?  How did you install CCS?  What directory do you have CCS installed into?

    Were any error logs generated?

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

    Please keep us informed.

    Best Regards,

    LIsa

  • 0 in reply to Lisa TI
    Expert 2780 points

    Hi Lisa,

    1. I have full admin privileges.
    2. Work with Win7, perform installation CCS from internet -CCS5.1.1.00031_win32.zip
    3. Installation done in the directory C:\ti\ccsv5
    4. I get the following message during build: Could not write metadata for '/TestGuiLib'.
      C:\Users\sabina.greenberg\workspace_v5_1\.metadata\.plugins\org.eclipse.core.resources\.projects\TestGuiLib\.markers.snap (The system cannot find the path specified)
    5. Setup Configuration .CCXML attached: 4300.Picollo.zip
    6. Setup Configuration 1781.sdopts.cfg
    7. GEL file: 7457.f28035.gel
    8. Simulator C2000 - ocing-tn USB-EMU[R3]
    9. logging file

     

     

     

     

  • 0 in reply to Sabina Greenberg101872
    TI__Guru*** 130875 points

    Hi Sabina,

    Would you be able to give this a try in the latest 5.2 beta?  Do you only get the error on build or do you get errors during project creation as well.  I just used the 5.2 beta and could build a SYS/BIOS example for the piccolo with no issues.  I would like to see if I can reproduce what you are doing.  What exact example/steps have you taken?  Did you select the example right from the new project wizard?

    Best Regards,
    Lisa

  • 0 in reply to Lisa TI
    Expert 2780 points

    Hi Lisa,

    After removing the example and import it again the problem disappeared in the example, but still exist in my project. Last changes that I did before this problem appeared is chanhe .gel file : run application from SRAM and not from the flash. So I changed DEBUG setting: F28035 Flash Setting-> Load RAM Only, and Erase Sector Selection - unchecked all Sectors (A-H).

    Now I restore .gel file and Debug option: running from Flash with erase all sectors - but it doesn't help. it seems that .gel file changing cause some problems  in my CCS. 

    So I had to reinstall CCS&SYS/BIOS on another place, copy my project to the new workspace_v5_1 and the project run without any problems.

    question: Could I change .gel file ? Why one file change(for this project) influence to other projects?

    Thanks, Sabina

  • 0 in reply to Sabina Greenberg101872
    TI__Guru*** 130875 points

    Hi Sabina,

    I am very glad to hear that you now have things building correctly and can work with your project without issues.

    Regarding the gel file.  This depends on where/how you made a change.  For example if you modified the gel file used by a target configuration file, it could be that other projects are using this target configuration file as well and this is why you see this effect.  It could also be that you have changed some setting at the workspace level that affect all projects in a workspace.  So I hope this helps clarify.

    All the best with development.

    Best Regards,

    Lisa

  • 0 in reply to Lisa TI
    Expert 2780 points

    Hi Lisa,

    Thank a lot for your support.

    Regards,Sabina

  • 0 in reply to Sabina Greenberg101872
    TI__Guru*** 130875 points

    Hi Sabina,

    that's what we are here for.  Glad if I could help.

    All the best with development.

    Best Regards,
    Lisa