Jump to content

Recommended Posts

Posted

Hey, guys

I found an example of AXI4 with TLM2 which only adapt to single socket. Now I wonder if I can use multi_passthrough_initiator_socket and multi_passthrough_target_socket to build AXI4 noc. 

And now I am stuck by the code. I really need your help.

Best wishes.

Posted

It depends on what level of abstraction you want to use to model AXI4. For LT level multi-socket should be ok. But to model at AT level you are better off using an sc_vector of sockets as each socket has its own timing and state.

But I'm wondering: why would you want to use multi passthrough sockets? What gainusing them would you expect?

Posted

To your orginal question: yes, you can use multi-passthrough sockets to model a NoC. You need to implement the AT protocol (depending on the socket id) and bind it to the sockets, there is no difference. There is one drawback you might encounter: if you need to hierarchically bind the sockets of your NoC and split the connections this will not be possible.This is because multi_passthrough_target_socket does not bind to tlm::target_socket, only to tlm::initialtor_socket.

Therefore my suggestion to use a sc_vector of TLM sockets...

Posted

It seems that you're right. I'm appriciate to have your suggustion of using sc_vector of TLM sockets to imple a NoC.

How can I approch with sc_vector instead of multi_socket. Is there any sample of NoC?

  • 2 weeks later...

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

×
×
  • Create New...