• 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 » BIOS » BIOS forum » [BIOS6] Adding ti.sysbios.rta.Agent and assignment something.common$.logger confict
Share
BIOS
  • Forum
  • Announcements
Options
  • Subscribe via RSS

[BIOS6] Adding ti.sysbios.rta.Agent and assignment something.common$.logger confict

[BIOS6] Adding ti.sysbios.rta.Agent and assignment something.common$.logger confict

This question is answered
Yokoyama, Atsushi
Posted by Yokoyama, Atsushi
on Mar 12 2010 00:58 AM
Expert5665 points

Champs,

I found an example for Logger module as following in Bios_User_Guide.pdf.  It works well.

var LoggerBuf = xdc.useModule('xdc.runtime.LoggerBuf');
var Load = xdc.useModule('ti.sysbios.utils.Load');
var Diags = xdc.useModule('xdc.runtime.Diags');
var loggerBuf = LoggerBuf.create();
Load.common$.logger = loggerBuf;
Load.common$.diags_USER4 = Diags.ALWAYS_ON;

However, when I added the following at top of the above, validator output a warning.

var ti_sysbios_rta_Agent = xdc.useModule('ti.sysbios.rta.Agent');

The warning message is as following.

ti.sysbios.utils.Load.common$.logger has already been assigned, Agent reassigning logger to RTALoadLog

Could you please let me know what I mistook?  Isn't this avoidable or illegal usage?  The reproducing environment is as following.

CCS v4.1.1.00014
DSP/BIOS: 6.21.0.13
XDCtools: 3.16.2.32
RTSC Target: ti.targets.C64P
RTSC Platform: ti.platforms.sim64Pxx

Any suggestion would be helpful.

Regards,
Atsushi

Yokoyama, Atsushi (Tokyo JAPAN) Communications Infrastructure, Marketing, Texas Instruments Japan Limited

DSP/BIOS CCS 4 BIOS6 CCS v4
Report Abuse
  • Reply
You have posted to a forum that requires a moderator to approve posts before they are publicly available.
All Replies
  • Chris McCormick
    Posted by Chris McCormick
    on Mar 17 2010 11:13 AM
    Verified Answer
    Verified by David Friedland
    Expert4095 points

    The way you configured the logger for the Load module looks good.

    You're getting the warning because, by default, the RTA Agent will configure the Load module's log for you. The Agent automatically configures BIOS logging to support the RTA tools in CCS 4. The RTA Agent is giving you that warning because it is replacing the Load logger you configured with one it has created.

    I would recommend simply removing the lines you have there to configure the logger for the Load module. The RTA Agent will take care of this for you. If you want to change the size of the Load log, you can set Agent.numLoadRecords, the default is 64.

    If you really want to configure the Load module's logger yourself, you can set Agent.configureLoadLog = false.

    I should also point out that the Agent automatically configures logging for all of the important modules in BIOS. See the RTA Agent CDOC for more details on that.

    Thanks,

    Chris

     

    BIOS 6 RTA RTA Agent
    Report Abuse
    • Reply
    You have posted to a forum that requires a moderator to approve posts before they are publicly available.
  • Yokoyama, Atsushi
    Posted by Yokoyama, Atsushi
    on Mar 17 2010 20:22 PM
    Expert5665 points

    Chris,

    Thank you for replying.  I understood that we don't need rta.Agent declaration (or reference) to use Load module simply.

    However, I actually wanted to do was, using another LoggerBuf instance with RtdxModule, in parallel with Load graph.  Exactly speaking, the essential objective of mine was the following.  I wanted RTDX transport with PROTOCOL.SIMULATION.

    Program.global.logger0 = xdc_runtime_LoggerBuf.create(...);
    xdc_runtime_Main.common$.logger = Program.global.logger0;
    // snip
    ti_rtdx_RtdxModule.protocol = ti_rtdx_RtdxModule.PROTOCOL_SIMULATION;
    ti_sysbios_rta_Agent.transport = ti_sysbios_rta_Agent.Transport_RTDX;
    

    For this reason, I considered we need to refer rta.Agent, so I had added the following.

    var ti_sysbios_rta_Agent = xdc.useModule('ti.sysbios.rta.Agent');
    

    Can we avoid the warning?  Or do we have a better solution?

    Thank you for your suggestion.

    Regards,
    Atsushi

    Yokoyama, Atsushi (Tokyo JAPAN) Communications Infrastructure, Marketing, Texas Instruments Japan Limited

    Report Abuse
    • Reply
    You have posted to a forum that requires a moderator to approve posts before they are publicly available.
  • Chris McCormick
    Posted by Chris McCormick
    on Mar 18 2010 11:16 AM
    Expert4095 points

    I guess I'm not clear on what you're trying to achieve here.

    The five lines you've listed above are enough, on their own, to get RTA working in CCS 4. You'll get all of the load, execution, and printf views available. Pulling in the RTA Agent sets all of the logging up for Load and BIOS, and you don't need to configure the logger for the Load module on your own.

    To stop the warning, just remove the code you had to configure the logger for the Load module, and that should do it.

    Chris

    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