• Join
  • Sign In with my.TI Login
Texas Instruments
  • Products
  • Applications
  • Tools & Software
  • Support & Community
  • Sample & Buy
  • About TI
Sample & Purchase Cart Sample & Purchase Cart
  • Search
  • Advanced
TI E2E™ Community
  • Support Forums
  • Blogs
  • Groups
  • Videos
  • 简体中文
  • More ...
TI Home » TI E2E Community » Support Forums » Embedded Software » Linux » Linux forum » Codec Server does not print DEBUG message
Share
Linux
  • Forum
Options
  • Subscribe via RSS

Codec Server does not print DEBUG message

Codec Server does not print DEBUG message

This question is answered
Gaston Schelotto
Posted by Gaston Schelotto
on Jul 19 2012 09:10 AM
Expert2225 points

Hi,

I've added this line in the main.c of my codec server:

Log_print0(Diags_ENTRY, "Welcome to Server's main()");

However I cannot see the 'welcome' message in the output console after executing

CE_DEBUG=2 ./app_remote.xv5T -s xe674 | tee info.txt

What is missing?

Regards,
gaston

Report Abuse
  • Reply
You have posted to a forum that requires a moderator to approve posts before they are publicly available.
All Replies
  • janet
    Posted by janet
    on Jul 19 2012 11:32 AM
    Verified Answer
    Verified by Gaston Schelotto
    Expert5315 points

    Gaston,

    Do you have the following code in your server's .cfg file?

    // Set up logging for Servers.
    // By default, the server logs are circular buffers where
    // Log statements are written. The RMS server extracts the data from the
    // circular buffer, and passes it to the client upon request.
    var Diags = xdc.useModule('xdc.runtime.Diags');

    // Set up the System support proxy
    var System = xdc.useModule('xdc.runtime.System');
    System.SupportProxy = xdc.useModule('ti.sdo.ce.utils.syscbuf.SysCBuf');
    // ... else, if you want to see the trace in the server's CIO buf, uncomment this
    //System.SupportProxy = xdc.useModule('xdc.runtime.SysStd');

    // Choose the logger that prints thread ID
    var LoggerSys = xdc.useModule('ti.sdo.utils.loggers.LoggerSysTID');

    var LoggerSysParams = new LoggerSys.Params();

    // Set up the timestamp
    var Timestamp = xdc.useModule('xdc.runtime.Timestamp');

    var Defaults = xdc.useModule('xdc.runtime.Defaults');
    Defaults.common$.logger = LoggerSys.create(LoggerSysParams);

    // Set Main diags to RUNTIME_ON.
    xdc.useModule('xdc.runtime.Main');
    Diags.setMaskMeta('xdc.runtime.Main', Diags.ALL, Diags.RUNTIME_ON);

    // Enable logging for metaonly modules
    var Registry = xdc.useModule('xdc.runtime.Registry');
    Diags.setMaskMeta("xdc.runtime.Registry", Diags.ALL, Diags.RUNTIME_OFF);

    To get trace from the DSP, the server needs to be built with SysCBuf, which prints trace into a buffer whose contents are passed up to the Arm.  The codec engine server examples include the file ti/sdo/ce/examples/buildutils/server_log.cfg which contains the code above.

    If you have this code in your .cfg file, but you're still not getting trace, you can post the .cfg file so we can take a look at it.

    Best regards,

        Janet

    Report Abuse
    • Reply
    You have posted to a forum that requires a moderator to approve posts before they are publicly available.
  • Gaston Schelotto
    Posted by Gaston Schelotto
    on Jul 20 2012 04:36 AM
    Expert2225 points

    Janet.

    It works. I've modified the server .cfg file as you suggested and I can see the log messages from the remote (DSP) server side. Now I'd like to go further by adding trace prints in my codec rt3d.c file as follows:

    TRACE_6print(handle, TRACE_ENTER,
                "RT3D_DS_process> Enter (h=0x%x, inBufs=0x%x, "
                "outBufs=0x%x, inOutBufs=0x%x, inArgs=0x%x, outArgs=0x%x)\n", h,
                inBufs, outBufs, inOutBufs, inArgs, outArgs);

    What do I have to do to see this message?

    Regards,
    gaston

    Report Abuse
    • Reply
    You have posted to a forum that requires a moderator to approve posts before they are publicly available.
  • janet
    Posted by janet
    on Jul 20 2012 15:14 PM
    Verified Answer
    Verified by Gaston Schelotto
    Expert5315 points

    Gaston,

    I answered a similar question on the forum awhile back here:

    http://e2e.ti.com/support/embedded/bios/f/355/p/145079/592343.aspx#592343

    (start at about the 6th message in the post).  Basically you need to implement the functions:

        extern XDAIS_TRACE_AssertFxn XDAIS_TRACE_assert;
        extern XDAIS_TRACE_PrintFxn XDAIS_TRACE_print;

    defined in ti/xdais/trace.h.  You then link your implementation into your server.  Your implementation of would call System_printf(), which outputs to the circular trace buffer that is read by the host.  You can find the source code on the post I referred to.

    Best regards,

        Janet

    Report Abuse
    • Reply
    You have posted to a forum that requires a moderator to approve posts before they are publicly available.
TI E2E™ Community
  • Support Forums
  • Blogs
  • Videos
  • Groups
  • Site Support & Feedback
  • Settings
TI E2E™ Community Groups
  • TI University Program
  • Make the Switch
  • Microcontroller Projects
  • Motor Drive & Control
Other Communities
  • Deyisupport
  • Designsomething.org
  • beagleboard.org
  • TI on Element 14
  • TI on TechXchangeSM
Other Technical & Support Resources
  • WEBENCH® Design Center
  • Product Information Centers
  • Technical Documents
  • TI Design Network
  • TI Technical Articles
  • TI Training

All content and materials on this site are provided "as is". TI and its respective suppliers and providers of content make no representations about the suitability of these materials for any purpose and disclaim all warranties and conditions with regard to these materials, including but not limited to all implied warranties and conditions of merchantability, fitness for a particular purpose, title and non-infringement of any third party intellectual property right. TI and its respective suppliers and providers of content make no representations about the suitability of these materials for any purpose and disclaim all warranties and conditions with respect to these materials. No license, either express or implied, by estoppel or otherwise, is granted by TI. Use of the information on this site may require a license from a third party, or a license from TI.

Content on this site may contain or be subject to specific guidelines or limitations on use. All postings and use of the content on this site are subject to the Terms of Use of the site; third parties using this content agree to abide by any limitations or guidelines and to comply with the Terms of Use of this site. TI, its suppliers and providers of content reserve the right to make corrections, deletions, modifications, enhancements, improvements and other changes to the content and materials, its products, programs and services at any time or to move or discontinue any content, products, programs, or services without notice.

Follow Us Texas Instruments on Facebook Texas Instruments on Twitter Texas Instruments on LinkedIn Texas Instruments on Google+
TI Worldwide | Contact Us | my.TI Login | Site Map | Corporate Citizenship | mobile m.ti.com (Mobile Version)

TI is a global semiconductor design and manufacturing company. Innovate with 100,000+ analog ICs and
embedded processors, along with software, tools and the industry’s largest sales/support staff.

© Copyright 1995-2013 Texas Instruments Incorporated. All rights reserved.
Trademarks | Privacy Policy | Terms of Use