• Locked Locked
  • Replies 4 replies
  • Subscribers 53 subscribers
  • Views 518 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.

Can't get System Analyzer to work with LoggerSM (neither binary file nor UDP)

Martin Bober
Prodigy 240 points

Hello everybody,


I'm trying to get System Analyzer to work using the LoggerSM module. The DSPs (C674X) is configured to write log messages to a shared memory. I build an ARM application based upon the LoggerSM example shipped with UIA which reads the shared memory and writes the encoded log messages either to a binary file or to a UDP socket when demanded.


When opening the binary file with System Analyzer, I always see the exact same two logged messages in the "System Analyzer File: Logs" view. Even though my log file ist several hundred  kB in size. I even see the exact same log messages when I open log file created at different execution times. In all those cases, the info text at the lower right of the view states "Showing 2 records | Processing: 0%" and never seems to update.


When I start a System Analyzer live session, the "Logs" view stays empty even though I see heavy UDP traffic on the correct port using Wireshark.


I tested my DSP program using System Analyzer's JTAG stop mode transport and it worked fine (most of the time). Therefore I am pretty sure that this is either a problem with my ARM application or Code Composer itself. It is hard to tell if the output of my ARM application (either the binary file or the UDP stream) is valid because I don't have a clue on how to tell valid binary data from invalid binary data.


I would appreciate any help or hints on how to debug.


CCS Version: 5.1.0.09000

RTSC/XDCtools version: 3.22.04.46

OS: Ubuntu 10.04

  • TI__Expert 3745 points

    Hi Martin,

       Could you post the following so that I can get a better understanding of how System Analyzer is configured and what data you are receiving:

    • the UIA configuration file you are using (e.g. DefaultSession.usmxml)
    • the systemAnalyzerData.bin binary file that is captured by System Analyzer during one of these sessions (the file path is shown in the "save data to file also:" box in the Tools / System Analyzer / Live dialog box)
    • the UDP data going to port 1235 of the PC running System Analyzer, saved as an Ethereal xml file (Ethereal is a free network monitoring tool that provides more capture options that wireshark does - you can download it for free from www.ethereal.com/download.html )

     Regards,

         Brian

     

  • in reply to BrianC
    Prodigy 240 points

    Hi Brian,


    thank you for your reply. First of all, I would like to send you the requested files as a private message since they may contain confidential data. Even though I am not able to decode them, someone else may be.


    However, I looks to me, that am not able to send you a private message. On your profile page there is no "Start Conversation" which I see on other TI employee's profiles. Can you tell me how to fix this issue?

    Additionally, I've got two other problem providing the files you asked for.

    1. There is no systemAnalyzerData.bin after starting a Live session. This is consistent with System Analyzer's Log View which shows no incoming log messages.
    2. I am not able to get Ethereal running. There are no more Debian packages provided and the Windows installer seems broken. Wouldn't a Wireshark export to PDML do the trick? I mean, its plain IP/UDP. Everything looks fine on the Ethernet layer.

    Regards,

    Martin

  • in reply to Martin Bober
    TI__Expert 3745 points

    Hi Martin,

       I've changed my profile settings so you should be able to see the 'Start Conversation' option in my profile now. 

    The reason I asked for you to capture the files using Ethereal is that I've written a number of parsing utilities that can pull information from the xml file format that Ethereal writes UDP capture data in.  I haven't found a good / easy way to get access to the packet payload and header data from wireshark, and would like to re-use the utilities I've written if at all possible. 

    It does look like there is something wrong with the Ethereal 0.99 release.  You can access previous releases at ftp://ftp.ethereal.com/ethereal/win32/all-versions/ and I've verified that ftp://ftp.ethereal.com/ethereal/win32/all-versions/ethereal-setup-0.9.9.exe installs correctly.  Could you see if this works for you?

    Regards,

      Brian

  • in reply to BrianC
    TI__Expert 3745 points

    Hi Martin,

       Sorry, I gave you the wrong version of Ethereal to download.  Could you please download and install  version 0.10.14 ( ftp://ftp.ethereal.com/ethereal/win32/all-versions/ethereal-setup-0.10.14.exe )?

    Thanks

      Brian