• State TI Thinks Resolved
  • Locked Locked
  • Replies 3 replies
  • Answers 1 answer
  • Subscribers 101 subscribers
  • Views 209 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

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-AM263: Library assembler source code files not visible for debugger although lookup pathes are correct

Jo Scho
Prodigy 205 points
Part Number: LP-AM263

Hello,

I'm testing AM263x with Code Composer studio 12.2 and launchpad LP-AM263x. 
For this purpose we imported some examples from the available SDK (version 8.5.24) in the Code Composer studio, e.g fsi_loopback_dma_nortos.

The examples use the prebuilt libraries from the SDK.


Our problem is, that Code Composer studio cannot find the assembler sources, wen we debug library code.


We configured the lookup pathes to the library sources correctly.

For C-files from the library, the debugger can find the sources, but assembler files are not found from the debugger.

Here, e.g. the function _system_pre_init



What is the problem? What can I do, that the assembler files are found by debugger?  Please help

  • 0
    TI__Mastermind 25498 points

    Hi 

    I would recommend to use CCS 12.1 with SDK 8.5 release. You can look in imports.mak for compatible version of tools.

    Jo Scho said:
    What is the problem? What can I do, that the assembler files are found by debugger?  Please help

    Let me try it on my end and come back on it by tommorow.

  • 0 in reply to Nilabh Anand
    Prodigy 205 points

    Hi Nilabh Anand,

    I have checked the following combinations now, no one of them functions:

    -  CCS 12.1 with SDK 8.5.24: does not work

    -  CCS 12.1 with SDK 8.6.24: does not work

    -  CCS 12.2 with SDK 8.5.24: does not work

    -  CCS 12.2 with SDK 8.6.34: does not work

    What do you mean with the the imports.mak in detail? Both imports.mak of the both SDKs have the same content.
    CCS_PATH is configured to 1210, so I think 12.1 is the better option.

    I hope you can reproduce the problem at your installation, too.

    Regards

    Jo

  • 0 in reply to Jo Scho
    TI__Mastermind 25498 points

    Hi Jo,

    I was able to reproduce the issue on my end. It is an expected behavior, as the source for _c_int00() lies in an assembly file which is located at source\kernel\nortos\dpl\r5\boot_armv7r_asm.S. It is an assembly file which can be viewed only in disassembly window.