• State Resolved
  • Locked Locked
  • Replies 7 replies
  • Answers 1 answer
  • Subscribers 101 subscribers
  • Views 475 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

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.

DSP and ARM communication using ip

Kjetil Østerås
Intellectual 370 points
Other Parts Discussed in Thread: 66AK2H06

Hi

I would like to configure a Keystone II system in such a way that each DSP's have their own ip address. My goal is to be able to send ip packets between linux running on the ARM side and each of the DSP cores. I would also like to use standard sockets when sending/receiving packets on the linux side. What configurations are necessary to achieve this?

My initial thought is that I will need to configure the Packet Accelerator to forward the different DSP addresses to separate queues, but what configurations are necessary to do in the Gigabit Ethernet Switch. Would I need to add ALE entries for each DSP ip address? Does the Gigabit Ethernet Switch support the case where a packet arrives at Port 0 (Host Port) and should be routed back to the same port?

  • 0
    TI__Mastermind 20790 points

    Hi,

    Go through the below E2E discussion, this will help you,

    http://e2e.ti.com/support/dsp/c6000_multi-core_dsps/f/639/t/353392.aspx

  • 0 in reply to Pubesh
    Intellectual 370 points

    Hi,

    I have gone through the e2e discussion. That discussion talks about assigning different PHY's to the ARM and DSP. In my case I have one external PHY which is controlled by ARM. So from the outside the system has only a single mac and ip address.

    However on the inside of the system I want to use ip communication as the ipc mechanism. The reason for doing something like this is to leverage all the tools and standard libraries that work with standard sockets. I do not intend to use this link for high-speed high-throughput communication.

    So for instance let's say I have 4 dsp's and I give them 4 unique ip's

    DSP0 - 192.168.2.0
    DSP1 - 192.168.2.1
    DSP2 - 192.168.2.2
    DSP3 - 192.168.2.3

    The ARM will have an extern ip address that all the dsp's know about

    ARM - 192.168.3.0

  • 0 in reply to Kjetil Østerås
    TI__Mastermind 20790 points

    Hi,

    Please mention the hardware and software using by you. Our MCSDK 3.1 will support ability to address multiple ports. The MCSDK3.1 release will support multiple ports Ethernet (no switching between ports, so all Ethernet traffics from multiple ports will be forwarded to the Host side for SW / PA engine to process).

  • 0 in reply to Pubesh
    Intellectual 370 points

    Hi Pubesh

    I am using MCSDK 3.0.4.18 and the 66AK2H06 device. Does this mean that using MCSDK 3.1 I would be able to send packets from ARM into the Ethernet Switch on Port 0 and make the Switch send the packet right back to Port 0 and into the Packet Accelerator for packet filtering/processing?

  • 0 in reply to Kjetil Østerås
    TI__Mastermind 20790 points

    Yes, you can send the packets into the Ethernet switch on port0 for packet filtering/processing. Please find the latest MCSDK for Keystone II devices at: http://software-dl.ti.com/sdoemb/sdoemb_public_sw/mcsdk/latest/index_FDS.html

  • 0
    Intellectual 370 points

    Hi Pubesh,

    In which part of the MCSDK 3.1 can I configure the support for multiple ports ethernet as you mentioned (pdk/csl/pa/cppi/ndk)?

  • 0 in reply to Kjetil Østerås
    TI__Mastermind 20790 points

    Hi,

    You can find the support available in u-boot to enable an Ethernet Port.