• State
  • Locked Locked
  • Replies 2 replies
  • Subscribers 99 subscribers
  • Views 334 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.

Syslink trace in user space not enabled with GT_setTrace() API

Roopesh Rajashekharaiah Nataraja
Intellectual 640 points

Hi,

I am able to get syslink trace on the kernel side using 'insmod syslink.ko TRACE=1 TRACEFAILURE=1' option (which I believe means SYSLINK_TRACE_ENABLE option is enabled with build) but on the application side, using GT_setTrace() API, no syslink call stack/trace is printed. I have included Trace.h in this app.c file.

Link used to use GT_setTrace() API is http://processors.wiki.ti.com/index.php/SysLink_UserGuide#Trace_types : Changing trace configuration from application section.

Version syslink-02.00.06.87 (with many patches applied on top). Won't be able to move to latest syslink as customer is currently using this version.

Am I missing something?

Thanks,

Roopesh

  • 0
    TI__Guru 59700 points

    Are you compiling your application with SYSLINK_TRACE_ENABLE define enabled ? SYSLINK_TRACE_ENABLE  may be enabled at syslink driver build but not in your application build time

  • 0 in reply to Badri Narayanan
    TI__Expert 6860 points

    As Badri mentioned, SYSLINK_TRACE_ENABLE needs to be enabled in SysLink in both the knl and usr level.  In the 2.00.06.87 bydefault, both sides are have tracing enabled during compilation of SysLink (e.g make syslink_driver, make syslink_hlos).

    Beside building with trace enabled, the tracing must be also be enabled by turning on the flags in both the knl and usr space.

    For knl:

    insmod syslink.ko TRACE=1 TRACEFAILURE=1

    For usr side, you must export that variable before running the application:

    export TRACE=1
export TRACEFAILURE=1