English subtitles

← Transaction level communication cs348 unit5new

Get Embed Code
1 Language

Showing Revision 1 created 04/12/2013 by Cogi-Admin.

  1. In previous units, we've looked at ports and we've analyzed how they enable you
  2. to write very modular programs. Because you can define your units, your
  3. monitors, and you can talk about this port without even knowing where it is
  4. connected to. And later when you bind it, you can send data to your hardware
  5. device or your hardware model. Or retrieve data back. So this port concept is
  6. very handy. we would like to extend this concept also to our test bench. So in
  7. our test bench we have transactions for example in the monitor, we recover a
  8. packet. And in the checker later, we want to look at this packet. So if we had
  9. a port to transfer the whole struct, that would be very helpful, and indeed we
  10. have two such ports. There is one called a Method port, and the other one is
  11. called the TLM port. Method ports are like remote procedure calls. So you can
  12. basically define locally a port, and when you call it you call actually a
  13. method in a different unit or component. TLM Ports are derived from the system
  14. C TLM standard. TLM stands for Transaction Level Modeling. So this is basically
  15. a standard for high level models and communication. One of the ports to finding
  16. TLM is called an Analysis Port. Analysis port is very handy for what we want to
  17. do. Because it enables you to connect one component to zero or more others.
  18. zero is very important, because it means you can leave it dangling. For
  19. example, in a monitor, you could say. Every time I find a packet, I'll stick it
  20. in the Analysis Port. And whether or not someone is connected, it doesn't
  21. matter. If no one is listening, fine. If someone is listening, then they can
  22. deal with the packet later. Also, it allows broadcasting, so zero or more than
  23. one are allowed. So you can have a multiple of these Analysis Ports connected
  24. to one single checker, for example. So in the next exercise we will look and
  25. play with Analysis Ports.