+ Post New Thread
Results 1 to 6 of 6
  1. #1
    Junior Member level 3
    Points: 288, Level: 3

    Join Date
    Jul 2016
    Location
    India
    Posts
    25
    Helped
    0 / 0
    Points
    288
    Level
    3

    parallel interface for data transferring

    Dear All,

    Could you please suggest some simple parallel interfaces that can be used for data transfer between two inter IP with in FPGA (in terms of hardware design).


    Regards,
    Viya

    •   Alt12th April 2017, 09:05

      advertising

        
       

  2. #2
    Newbie level 2
    Points: 101, Level: 1

    Join Date
    Nov 2016
    Posts
    2
    Helped
    1 / 1
    Points
    101
    Level
    1

    Re: parallel interface for data transferring

    Hi,
    You could try:
    - AXI-lite
    - Wishbone
    - Avalon
    Kris



    •   Alt12th April 2017, 12:37

      advertising

        
       

  3. #3
    Advanced Member level 3
    Points: 6,279, Level: 18
    Achievements:
    7 years registered Created Blog entry
    dpaul's Avatar
    Join Date
    Jan 2008
    Location
    Germay
    Posts
    893
    Helped
    202 / 202
    Points
    6,279
    Level
    18
    Blog Entries
    1

    Re: parallel interface for data transferring

    AXI-S is better if you know that you will have a continuous steam of data which has a valid end (tlast signal).
    If not satisfied with AXI-S, then build your own. All you need to do is to implement the concept of handshaking.

    On the rising edge of the system clock, your device(Tx) will inform the other device(Rx) that it has data to send. So you just make a signal HIGH. The other device(Rx) will sample this signal and if HIGH, should send out another reply-signal driving it HIGH to indicate that it can accept the data. If the other device(Rx) cannot accept the data then let this reply-signal remain LOW. Now if the data sending device(Tx) samples this reply-signal as HIGH, just make your data available on the data bus on the next clock cycle.

    You are the architect, so you need to compare all available protocol and decide what suites best for your design!
    Sharing my ideas and knowledge + learning from the experiences of others is what I am looking for.
    Spoon feeding is not my cup of coffee, so I am ready to show you the path, but it is you who has to walk through it!


    1 members found this post helpful.

    •   Alt12th April 2017, 13:30

      advertising

        
       

  4. #4
    Junior Member level 3
    Points: 288, Level: 3

    Join Date
    Jul 2016
    Location
    India
    Posts
    25
    Helped
    0 / 0
    Points
    288
    Level
    3

    Re: parallel interface for data transferring

    Hi Dpaul,

    Thanks for your suggestion. If i am trying to build my own parallel interface, what are all the things that i need to concentrate. I used only available standard interfaces. while creating my own interface, whether it is needed to compliant to any standard protocol available in industry.


    Regards,
    viyaaloth



  5. #5
    Super Moderator
    Points: 43,936, Level: 51
    Awards:
    Most Frequent Poster

    Join Date
    Apr 2014
    Posts
    8,988
    Helped
    2169 / 2169
    Points
    43,936
    Level
    51

    Re: parallel interface for data transferring

    Hi,

    * n data lines (as much as you need)
    * one strobe signal to identify that the databits are valid
    (the strobe signal should show "invalid" when new data is appied until the data is considered as stable. It needs to toggle even if you send the same data value than before.)

    Klaus



    •   Alt13th April 2017, 12:47

      advertising

        
       

  6. #6
    Advanced Member level 3
    Points: 6,279, Level: 18
    Achievements:
    7 years registered Created Blog entry
    dpaul's Avatar
    Join Date
    Jan 2008
    Location
    Germay
    Posts
    893
    Helped
    202 / 202
    Points
    6,279
    Level
    18
    Blog Entries
    1

    Re: parallel interface for data transferring

    while creating my own interface, whether it is needed to compliant to any standard protocol available in industry.
    For intra-chip communication, you need not explain to your client what data transfer protocol is being followed (keep the protocol as an internal documentation).
    If you can transfer your desired data volume within the desired number of clock cycles, you are good to go.
    Sharing my ideas and knowledge + learning from the experiences of others is what I am looking for.
    Spoon feeding is not my cup of coffee, so I am ready to show you the path, but it is you who has to walk through it!



--[[ ]]--