• State TI Thinks Resolved
  • Locked Locked
  • Replies 5 replies
  • Answers 1 answer
  • Subscribers 98 subscribers
  • Views 558 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.

RTA logs messed up

one and zero
Mastermind 18136 points
Other Parts Discussed in Thread: SYSBIOS

Hi Champs,

 

I am using settings for ELF (Transport_STOP_MODE_ONLY ), I have the same issue with unreadable formatted messages in Raw and Print Logs (see screenshot). CCS Veriosn is 4.2.3

In the Cfg file I have:
 

System.SupportProxy = SysStd;

/********* RTA START *******/

/* Create and install Main's loggerBuf */

 

var LoggerBufParams=new LoggerBuf.Params();

LoggerBufParams.exitFlush=true;

LoggerBufParams.numEntries = 32;

var logger0=LoggerBuf.create(LoggerBufParams);

Main.common$.logger = logger0;

 

/*Turn on USER3 logs in Main module (all non-module functions)*/

Main.common$.diags_USER3 = Diags.ALWAYS_ON;

/*  Enable RTA  */

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

Agent.transport=Agent.Transport_STOP_MODE_ONLY;



Any hint is welcome ...

Kind regards,

one and zero

  • 0
    TI__Expert 4095 points

    When you do a Log_print in your code, what gets logged is the address of the string that you pass (plus any arguments). On the host, we take this String address and parse the ELF file to find the target string.

    For this to work, the target string must be a constant. Is it possible you're passing dynamic strings?

    Thanks,

    Chris

  • 0 in reply to Chris McCormick
    TI__Mastermind 18136 points

    Hi Chris,

    the call is 

    Log_print0(Diags_USER1, "hello");

     I found is this:
    
        
    
      
      Log_print0(), etc. will not work in code like the following which is legal 'C':

    if (0) 
        Log_print0(Diags_USER1, "hello");
    else
        Log_print0(Diags_USER1, "world"); 
      
    
      
    
      see https://bugs.eclipse.org/bugs/show_bug.cgi?format=multiple&id=290003
    
      

    But we use XDC tools version 3.20 so it should not be an issue. Despite that we tried the suggested workaound as above but the issue is still there ...

    Kind regards,
    one and zero
  • 0 in reply to one and zero
    TI__Expert 4095 points

    If you right click on the Raw Logs view, and select "column settings...", you can check a box to have it display arg1. This will show you the address of the string. You can compare this address to your map file to see if it's in a .const section or not. (Note: The display has some issues with sign-extending the argument values... If your arg1 value has a bunch of leading 'F's, just ignore those).

    One way this could get screwed up is if you load your application, then modify it and rebuild it. RTA will parse the ELF file for the strings and they may not be in the same spot as they were in the running application. That's unlikely, though; I imagine you've tried reloading this app a number of times.

    Chris

  • 0 in reply to Chris McCormick
    TI__Mastermind 18136 points

    Hi Chris,

    thanks. We verified that the arg1 is in section .const

    So that shouldn't be the issue. Any other ideas?

    Thanks,

    one and zero

  • 0 in reply to one and zero
    TI__Expert 4095 points

    I assume you also verified that the data pointed to by arg1 was the string you were expecting?

    I'm off on vacation starting tomorrow, I'll be back in the office next Wednesday. I'm sorry we weren't able to get farther on this--I think we'll probably need to do a WebEx to look closer when I get back.

    You could also try building the stairstep example for elf (maybe add a few Log_prints in main), and verify that everything looks good there. Then maybe try and see what's different about your application?

    Thanks,

    Chris