Stats

  • Locked Locked
  • Replies 2
  • Subscribers 64
  • Views 1265
  • Members are here 0
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

multiple binding (star configuration) of method/event port

archive

Hi,
I started to use method/event port to sync e modules. I find some problems cadence implementation of the multiple binding of those ports.
 
For example:
We have a list of agent client. Each client has a monitor that reflects out event let say request.
This event is reflected by event port (out) , to this event connected the bfm of each client (in) +
There is in some other eVC arbiter that connected to the whole client events.
 
Now let’s test a scenario:
 
 One client agent monitored a request and reflects it out through the port,
Expected: the client BFM and the arbiter wake up.
Actually: all the clients bfm wake up + the arbiter.
 
I added a little presentation that demonstrate the problem
 
I would like to discuss with you if this implementation of the multiple binding is a bug or my concept of using those ports are wrong
Thanks
Ronen


Originally posted in cdnusers.org by ronenzb
event port problem.zip

  • Ronen,

    Is the eVC arbiter connected to the clients' events using an event port as well? If that's the case, then you are probably connecting all the event ports (monitor, bfm and arbiter ports) in the same port bound set. Take a look at the 'e' Language Reference, section 6.2.2 "Multiple Bindings" and you will see that the topology of a multiple binding is a star topology, with all ports connected via a common "channel". This means that for every event emitted, all the input ports in the bound set of the same type will get the event. You can check for that by passing the "trace bind" command to specman.

    This looks like one of the port limitations (please correct me if i'm wrong, i'm not 100% clear from the definition):

    Support for point-to-point connections is between ports only, in other words, each port can be connected to only one other port.

    A quick workaround would be to create a duplicate port in the monitor and have it emit the request event when the original port does. You can then bind the duplicate port to the arbiter and you will get the desired behavior. If anyone can suggest a better solution, please let us know.

    Hope that helps!


    Originally posted in cdnusers.org by iraklis

  • i agree with you ,

    i just don't understand why cadence don't change it so the buliding of the star will take into account the direction of the port..

    in this configuration when i design eVC i can't give the user port that i already used (because he might bind it in star configuration)


    Originally posted in cdnusers.org by ronenzb

Community Guidelines

The Cadence Design Communities support Cadence users and technologists interacting to exchange ideas, news, technical information, and best practices to solve problems and get the most from Cadence technology. The community is open to everyone, and to provide the most value, we require participants to follow our Community Guidelines that facilitate a quality exchange of ideas and information. By accessing, contributing, using or downloading any materials from the site, you agree to be bound by the full Community Guidelines.