• State Resolved
  • Locked Locked
  • Replies 7 replies
  • Subscribers 99 subscribers
  • Views 724 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.

UDP Logger

Damian Frick
Prodigy 120 points
Other Parts Discussed in Thread: TMS320C6678

Hi,

I want to create a simple logger that resides on one (any) of the cores and logs data sent to it (from other cores, by some means) to a PC connected with Ethernet using UDP datagrams. So far I have only been working on the sending of the UDP packets.

I ran into two problems:
Firstly, if the code is not running on core0 the NDK features are never initialized and the networkOpenHook is never called.
Secondly, if the code is running on core0 everything works fine until I call send(...), which throws an error (i.e. return that is not 0) every time I try.

I am using:
SYS/BIOS 6.33.2.31
MCSDK PDK TMS320C6678 1.0.0.18
NDK 2.20.6.35
IPC 1.24.2.27

I also put the code in a paste bin:
mheLogger.c : http://pastebin.com/jX1iThU2
mheLogger.h : http://pastebin.com/Z5rt9ZDt
mheLogger.cfg : http://pastebin.com/YxUVnWSv

  • 0
    TI__Guru* 96960 points

    Hi Damian,

    I have a couple questions.

    1. What is receiving the UDP packets on the PC? System Analyzer in CCS?

    2. Have you looked at the UIA product? The newest version (1.01.01) has a couple loggers (LoggerIdle and LoggerStreamer) that allows you to plug in a function (or two) that sends the data via any transport you want. UIA also has an example where core 0 sends data to CCS via UDP. The other cores data is routed through core 0.

    Todd

  • 0 in reply to ToddMullanix
    Prodigy 120 points

    1. I wrote a short python script that listens to the port and logs all the incoming UDP data.

    2. I have looked at UIA but it turns out that with JTAG I have not enough throughput and when I use Ethernet I loose a lot of packets as well, I suspect that CCS can't keep up with processing the data, since Ethernet should be fast enough and I selected a large enough buffer. Additionally having the logger on any core (specifically not on core0) would be a huge benefit for me if this is possible, since this makes it more modular.

  • 0 in reply to Damian Frick
    TI__Guru* 96960 points

    OK, I think I understand. You have your own logger and not using the Log module...correct?

    Regarding the first issue: I believe you can run the NDK on each core. I'll confirm this. If you are trying to use a single .out for all cores does complicate it though. Do you have the same for each core or do you have a different one for each core?

    Regarding the second issue: Can you try using sendto() instead?

    Todd

  • 0 in reply to ToddMullanix
    Prodigy 120 points

    Yes, I am not using the Log module. And separate .out files/projects for each core.

    I did try sendto, same issue. Everything up to the send command goes fine but send returns an error.

  • 0 in reply to Damian Frick
    TI__Guru* 96960 points

    Hi Damian,

    Use htonl instead of htons

    addr.s_addr = htons(0xc0a80265);

    should be

    addr.s_addr = htonl(0xc0a80265);

    Also use sendto() for connectionless-mode socket (e.g. UDP).

    Todd

  • 0 in reply to ToddMullanix
    Intellectual 380 points

    Hi Todd , 

         I try to use LoggerIdle .It seems  the LoggerIdle.transportFxn  is been execute after log_info been called !

         But the transportFxn   paramater1  is not right , I only log "hello world" , but the length is 96 byte(maybe include timestamps and other data , but how to parse?) !!! 

         Is the module LoggerIdle is only for system analyzer ? Can i just use a tera term to get log entry from uart just like LoggerSys output log to SysMin buffer?

    Brenden

    http://e2e.ti.com/cfs-file.ashx/__key/communityserver-discussions-components-files/355/4810.uart_5F00_logging.7z

  • 0 in reply to brenden lai
    TI__Guru* 96960 points

    Brenden,

    The data is not ASCII data. It is encoded Log data. System Analyzer knows how to decode it.

    Also, in the future can you start a new thread. When additional questions are added to an existing thread, it becomes hard to manage and track.

    Todd