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.

RTOS/PROCESSOR-SDK-AM335X: Debug issue

Part Number: PROCESSOR-SDK-AM335X

Tool/software: TI-RTOS

I am working on an RTOS project using GNU v4.9.3 Linaro compiler as provided by CCSv7.1.

Now while trying to debug a memset() issue I see this:

Can't find a source file at "/home/xlibrary/trees/gnu/gnu-c04/src/linaro/gcc-arm-none-eabi-4_7-2012q4-20121208/src/newlib/newlib/libc/string/memset.c"
Locate the file or edit the source lookup path to include its location.

Why does the path in default lib here seem to be based on a 4.7 code base (2012!)? Isn't there a new one for 4.9 at all? Or do I need to configure RTS lib somewhere? I don't think I have a 4.7 compiler installed anyway.

Just makes me wonder...

Regards,

  • Hi Frank,

    I have notified the RTOS team. They will reply here.
  • Any comments? I don't think this is a CCS issue as the compiler is Linaro in this case. However it is a packaging issue in RTOS SDK - if there is any issue.
    By the way in the past we supplied RTS lib sources with the compiler. I can't find this for GCC compiler...
  • Frank,

    This is a typical issue described on section 6 of the wiki page below, but with GCC.
    processors.wiki.ti.com/.../Debug_Handbook_for_CCS

    The source code for GCC is provided in a separate package not provided with CCS, therefore you will have to download the source package for the exact version you are using , extract it somewhere and pass the path to the CCS debugger so it can perform source code debugging on the library code.
    The sources can be obtained either from Linaro or launchpad. Linaro does not seem to have 4.9.3 anymore on their trees.
    releases.linaro.org/.../
    launchpad.net/.../ download

    Hope this helps,
    Rafael
  • Hi Rafael,

    thanks. In general the issue is clear to me. It is normal that the paths shown in such messages are not related to my own machine and for full debug I need to have the sources (and compile locally). However with the above error message it looks like the RTS libs we provide are older than the compiler version (or the original folder was never renamed...). So I wonder if we are really delivering the correct lib here or not. Again I don't think the CCS team can answer this.

    Thanks for providing download links and I hope it will be helpful for someone else. In my case it turned out I was calling the API with a wrong parameter. Luckily I was able to figure this out without going through a full debug of the RTS lib (usually they are pretty stable anyway...).
    In general if we are using versions that are already a bit outdated (and therefor sources difficult to acquire) we may think about delivering the ZIP with sources within our compiler package. With SDKs in the 1-3GB range a few MB shouldn't matter that much. :-)

    Regards,
  • Frank,

    Thanks for reporting back your findings.

    Regarding your question, we grab the package from Linaro as-is without modifications - we don't rebuild their RTS. Therefore you are right: the disconnect between the toolchain version and the path to the source file cannot be answered by the CCS team - you would have to ask Linaro about this.

    Cheers,
    Rafael