bsipl_h

Hi all, A question on AT (Approximately Timed) style which we’re using. Section 4.1.2.1 of TLM Ref says: We plan to build AXI4 Initiator and Target, but we’ve some other entities that interact with these two, to communicate trace messages. Does the above excerpt from the Reference mean that these “other” entities (which are not directly participating in AMBA bus communication) are exempted from having to use non-blocking transport interface? Even if they’re not, we feel that one can’t avoid calls (even in a Thread process) that potentially must block/wait (wait for an event/signal or a FIFO msg). So, the question is, for such “other” entities, is it OK, for example, to use a read call (not nb_read) from a sc_fifo (while still qualifying for “AT” style)?

Hi all, this question is about having interoperability between AXI4 Initiator and Target, Say, we’ve the AXI4 Initiator in the Top; this is our deliverable. We’ll also provide a reference AXI4 Target in Test Bench that we test our AXI4 Initiator with. We think that our AXI4 Initiator should be able to interop with a Customer’s AXI4 Target. Is that a fair expectation, or could there be issues arising from the different underlying TLM libraries that the Initiator and Target are built with?

Thank you for the provided link; it offered valuable information. However, the examples presented feature modules that share a common parent. The specific requirement in question involves scenarios where processes exist in separate modules without a shared parent. The query revolves around whether it's feasible for a process in one module to signal an sc_event or write to an sc_fifo intended for another process located in a distinct module, without any hierarchical connection.

Hello, We recently started working with SystemC and TLM. We’ve a question around the inter-process communication/synchronization mechanism used in SystemC. Is it possible for a process in a module to notify an sc_event (or write to a sc_fifo) to another process in a different module that’s not part of the earlier module’s hierarchy (no common parent)? To the little we read so far, we couldn’t see how this would be possible if the sending and receiving processes are in two disparate modules, (here by sending we mean: event-notification or sc_fifo in the SystemC). Similarly, will such cross-module communication be possible using TLM sockets (when the modules don’t share a common parent)?