• State Resolved
  • Locked Locked
  • Replies 5 replies
  • Answers 2 answers
  • Subscribers 54 subscribers
  • Views 743 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.

DSS and Reading stdout

Greg Warner
Prodigy 40 points


From a DSS Javascript script, I'm trying to capture what I see in the CCS console when the board boots, e.g.:

"MSP430: Loading complete. Code Size - Text: 7052 bytes Data: 26 bytes."

It is possible to capture this from within DSS?  I've tried session.stdOut(), but it returns nothing.  Thanks in advance.

  • 0
    TI__Guru**** 472291 points

    Hello,

    This message is not from stdout but a message from the debugger. You can increase the console and log verbosity to get this message in the console and logs. When I crack both up to "TraceLevel.ALL" I see the message:

    Thanks

    ki

  • 0 in reply to Ki
    Prodigy 40 points

    Is there a way I can extract that message from within my DSS script so I can, for example, verify that a certain number of bytes were loaded?  

    Looking at the logs, I can see that it's using a DebuggerInfoListener.  Can I register my own DebuggerInfoListener and handle the debug output myself?

  • 0 in reply to Greg Warner
    TI__Guru**** 472291 points

    Ok I see what you are looking to do. I'm not sure you can listen for that message in the script yourself. There is a way to get that information by running some utility on the out file but of course this doesn't tell you exactly how many byes where loaded by the debugger itself. I'm not sure if you are looking for the information to very the program load or to know how big the code and data sections are.

  • 0 in reply to Ki
    Prodigy 40 points

    Mostly looking to verify that the program loaded correctly and that the correct program was loaded.  I was hoping to do so by verifying the number of bytes loaded.  Not so important which are code and data.

  • 0 in reply to Greg Warner
    Prodigy 40 points

    I ended up just have the script close and read its own log.