• Join
  • Sign In with my.TI Login
Texas Instruments
  • Products
  • Applications
  • Tools & Software
  • Support & Community
  • Sample & Buy
  • About TI
Sample & Purchase Cart Sample & Purchase Cart
  • Search
  • Advanced
TI E2E™ Community
  • Support Forums
  • Blogs
  • Groups
  • Videos
  • 简体中文
  • More ...
TI Home » TI E2E Community » Support Forums » Digital Signal Processors (DSP) » C6000 Multicore DSP » Keystone Multicore Forum (C66, 66A, AM5) » question about ethernet Interface
Share
C6000 Multicore DSP
  • Forums
  • Announcements
Options
  • Subscribe via RSS
Training Available
TI provides self-paced online training that introduces the primary components of the KeyStone II family of SoC devices.

  • KeyStone II SoC Overview >
  • KeyStone II Software Overview >
  • KeyStone II ARM Cortex-A15 Corepac Overview >
  • More Information >
  • Check out
    Multicore Mix blog
    • $core_v2_blog.Current.Name

      It’s our second anniversary, but you get the present!

      Posted 4 days ago
      by Lindsey Bare
      It’s hard to believe it’s already been two years...
    • $core_v2_blog.Current.Name

      Limited time offer: Save $100 on Keystone-based EVM!

      Posted 17 days ago
      by tscheck
      Have you been thinking about ordering a TI Keystone-based EVM...
    • $core_v2_blog.Current.Name

      Imagine the impact…TI’s KeyStone SoC + HP Moonshot

      Posted 29 days ago
      by Sanjay35057
      Last week, market leader Hewlett Packard announced a huge change...

    question about ethernet Interface

    question about ethernet Interface

    This question is not answered
    zezo alex
    Posted by zezo alex
    on Aug 04 2012 11:21 AM
    Prodigy170 points

    hello 

    i want to use the  ethernet Interface in order to connect betwen 2 c6670L kits and transfer data from one kit to another .

    i already download the MCSDK , i want to know is there pdf that explain this interface and is there any examples that may i can use ?

    Report Abuse
    • Reply
    You have posted to a forum that requires a moderator to approve posts before they are publicly available.
    All Replies
    • HRi
      Posted by HRi
      on Aug 04 2012 13:01 PM
      Mastermind7240 points

      Hi Alex,

      Start with going over the documents - 

      - sprugz6-KeyStone Architecture Network Coprocessor (NETCP) User Guide

      - sprugv9b-KeyStone Architecture Gigabit Ethernet (GbE) Switch Subsystem User Guide

      - NDK documents under ndk_2_21_01_38\docs

      For example go over

      - mcsdk_2_00_09_21\examples\ndk\client

      OK, it's not exactly what you want but it can help you,

      HR

      Report Abuse
      • Reply
      You have posted to a forum that requires a moderator to approve posts before they are publicly available.
    • zezo alex
      Posted by zezo alex
      on Aug 04 2012 19:31 PM
      Prodigy170 points

      thanks for your reply

      but  i searched on this Forum  and found out that the hyperlink is the best to transmit at higher data rate so, i am reading the user guide about hyperlink and as i understood in the part of address Translation(from page 33)

      -there is a ingress address(the address of data to be sent) and egress address (the address that the data will put in certain segment) is that true ?

      -HyperLink supports up to 64 different memory regions so, is that segments in what memory location (DDR , ROM or FIFO) ? 

      Regards

      Report Abuse
      • Reply
      You have posted to a forum that requires a moderator to approve posts before they are publicly available.
    • HRi
      Posted by HRi
      on Aug 05 2012 01:01 AM
      Mastermind7240 points

      Hi Alex,

      Yes you are correct the Hyperlink interface has higher data throughput, You can see a window of 256MB of the other device and you should define the 64 memory segments which can be anywhere in the remote device,

      BR,

      HR

      Report Abuse
      • Reply
      You have posted to a forum that requires a moderator to approve posts before they are publicly available.
    • zezo alex
      Posted by zezo alex
      on Aug 05 2012 06:15 AM
      Prodigy170 points

      thank you for your reply but you didn't answer to my questions 

      -there is a ingress address(the address of data to be sent) and egress address (the address that the data will put in certain segment) is that true ?

      -HyperLink supports up to 64 different memory regions so, is that segments in what memory location (DDR , ROM or FIFO) ?

      Regardes

      Report Abuse
      • Reply
      You have posted to a forum that requires a moderator to approve posts before they are publicly available.
    • HRi
      Posted by HRi
      on Aug 05 2012 15:50 PM
      Mastermind7240 points

      Hi Alex,

      After setting the memory regions than you are writing reading from the other device as memory map, so there is the egress memory translation and the ingress memory translation, the memory can sit whenever you want's it to be (DDR, MSMC, ...)

      HR

      Report Abuse
      • Reply
      You have posted to a forum that requires a moderator to approve posts before they are publicly available.
    • zezo alex
      Posted by zezo alex
      on Aug 08 2012 11:13 AM
      Prodigy170 points

      Thank you HRi for your reply

      it's seem that from hyplnkexampleaddrmap() that responsible for address translation  that the address of remote device is in L2SRAM as 

      /* Make one segment which can see dataBuffer */
      if ((globalAddr >= 0x800000) && (globalAddr < 0xa00000)) {                                                                                                                                                                                                       /* Address is in L2 */                                                                                                                                                                                                                                                                    globalAddr |= 0x10000000 | (DNUM << 24); }

      but where is the address of local DSP (the address of the data to be transfered to the remote DSP) ?

      And as i understood from the example the hyperlink transfer data which is in L2SRAM (but i can't find the specified address) and apply Address Translation on the TX Side then send it to the remote device and in the remote device , applying Address Translation on the RX Side then put the data in L2SRAM (0x10800000 - 0x10a00000) segment of 4MB ,so is that true ?

      thanks , 

      Alex

      Report Abuse
      • Reply
      You have posted to a forum that requires a moderator to approve posts before they are publicly available.
    • zezo alex
      Posted by zezo alex
      on Aug 13 2012 20:48 PM
      Prodigy170 points

      any help there , please

      Report Abuse
      • Reply
      You have posted to a forum that requires a moderator to approve posts before they are publicly available.
    • HRi
      Posted by HRi
      on Sep 02 2012 03:43 AM
      Mastermind7240 points

      Hi Alex,

      Have you solved the issue?

      HR

      Report Abuse
      • Reply
      You have posted to a forum that requires a moderator to approve posts before they are publicly available.
    • zezo alex
      Posted by zezo alex
      on Sep 03 2012 19:25 PM
      Prodigy170 points

      yes

      Report Abuse
      • Reply
      You have posted to a forum that requires a moderator to approve posts before they are publicly available.
    • HRi
      Posted by HRi
      on Sep 04 2012 03:58 AM
      Mastermind7240 points

      Great ! Good-Luck,

      HR

      Report Abuse
      • Reply
      You have posted to a forum that requires a moderator to approve posts before they are publicly available.
    TI E2E™ Community
    • Support Forums
    • Blogs
    • Videos
    • Groups
    • Site Support & Feedback
    • Settings
    TI E2E™ Community Groups
    • TI University Program
    • Make the Switch
    • Microcontroller Projects
    • Motor Drive & Control
    Other Communities
    • Deyisupport
    • Designsomething.org
    • beagleboard.org
    • TI on Element 14
    • TI on TechXchangeSM
    Other Technical & Support Resources
    • WEBENCH® Design Center
    • Product Information Centers
    • Technical Documents
    • TI Design Network
    • TI Technical Articles
    • TI Training

    All content and materials on this site are provided "as is". TI and its respective suppliers and providers of content make no representations about the suitability of these materials for any purpose and disclaim all warranties and conditions with regard to these materials, including but not limited to all implied warranties and conditions of merchantability, fitness for a particular purpose, title and non-infringement of any third party intellectual property right. TI and its respective suppliers and providers of content make no representations about the suitability of these materials for any purpose and disclaim all warranties and conditions with respect to these materials. No license, either express or implied, by estoppel or otherwise, is granted by TI. Use of the information on this site may require a license from a third party, or a license from TI.

    Content on this site may contain or be subject to specific guidelines or limitations on use. All postings and use of the content on this site are subject to the Terms of Use of the site; third parties using this content agree to abide by any limitations or guidelines and to comply with the Terms of Use of this site. TI, its suppliers and providers of content reserve the right to make corrections, deletions, modifications, enhancements, improvements and other changes to the content and materials, its products, programs and services at any time or to move or discontinue any content, products, programs, or services without notice.

    Follow Us Texas Instruments on Facebook Texas Instruments on Twitter Texas Instruments on LinkedIn Texas Instruments on Google+
    TI Worldwide | Contact Us | my.TI Login | Site Map | Corporate Citizenship | mobile m.ti.com (Mobile Version)

    TI is a global semiconductor design and manufacturing company. Innovate with 100,000+ analog ICs and
    embedded processors, along with software, tools and the industry’s largest sales/support staff.

    © Copyright 1995-2013 Texas Instruments Incorporated. All rights reserved.
    Trademarks | Privacy Policy | Terms of Use