• State Resolved
  • Locked Locked
  • Replies 5 replies
  • Subscribers 53 subscribers
  • Views 1455 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/CCSTUDIO: Resource 'xxx/main.c' does not exist.

Torsten Robitzki
Expert 2474 points

Part Number: CCSTUDIO

Tool/software: Code Composer Studio

Hello,

I build my software, using make (CMake) and use CCS just for debugging. Up to now, I had little problems with CCS finding and displaying the corresponding sources. After a restart of CSS, I now have the problem, that CSS can't display the sources, when clicking on an entry in the call stack. Concrete, I have a source file named `main.c`. CCS complains about "Resource '/pfc/source/bootloader/bootloader/main.c' does not exist.". I could open the source file, but the main.c file with the file open dialog, but this still would not allow me to debug on source level. The absolute path of the file is something like: /Users/torsten/customername/pfc/source/bootloader/bootloader/main.c (I've changes customername for privacy reasons)

When I grep through the loaded bootloader.out file for strings, I just find the absolute path of the main.c file, but not the complained about file name ('/pfc/source/bootloader/bootloader/main.c'). I tried to give CSS a hint as to where to find the file by adding a "File System Directory" to the debug configuration. I've tried both, `/Users/torsten/customername/pfc` and `/Users/torsten/customername/pfc` but to no avail.

How can I convince CCS to find the sources of a given .out file?

- I build the sources with `--symdebug:dwarf`

- CCS Version is 10.1.0.00010

- Compiler / Linker Version is 20.2.2.LTS

- OS is macOS 10.15.7

- This morning, source debugging was still working

- My debug configuration XML file is under source control, so I'm quite confident, that there was no change

- Restarted CCS already multiple times

Best regards and thanks in advance,

Torsten

  • 0
    TI__Guru**** 476191 points

    Hello Torsten,

    It seems unusual that just a CCS restart would cause your working debug environment to break. I suppose you could try cleaning your workspace and deleting your launch configuration to reset the environment but I am doubtful that it will resolve the issue.

    Can you try using the Modules view to see what the path is for main.c in the loaded symbols? Can you open the file in the editor from the Modules view?

    thanks

    ki

  • 0 in reply to Ki
    Expert 2474 points

    Hi Ki,

    thanks for the quick reply. I've opened the Module view and tried to open the file from that view. It is not possible to open it. Same error. What looks suspicious to me, is that the view claims the path to be a relative path (see screenshot). I've also tried to open interrupt.h, which is part of the TI SDK. That file opens fine (and also reports the absolute file name to be a relative path). Open the main.c from the file open dialog works, so I guess it's not a problem of user rights or something like this. I've copied the full path given by the module view to a shell and used ls on it. And ls was able to file the file as given by the module view.

    What comes to my mind, is that I not only restarted CCS, but also switched from release build to debug build, which usually causes a complete rebuild of the software (and switched back to release to see if this was the cause of the problem),

    I will try the workspace cleanup next.

    best regards and thanks

    Torsten

  • 0 in reply to Torsten Robitzki
    Expert 2474 points

    forgot the screenshot :-)

  • 0 in reply to Ki
    Expert 2474 points

    Using a new workspace did the trick. Thanks again for your quick help!

    Torsten

  • 0 in reply to Torsten Robitzki
    TI__Guru**** 476191 points

    ah, good! Thank you for the update!