Jump to content


  • Content Count

  • Joined

  • Last visited

About johnmac

  • Rank

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Thanks for all the comments. Will using a std::mutex lock() and unlock() around the critical section help when accessing the struct help ?
  2. Thanks for the response @Eyck I followed your suggestions, and did something like this. Pls bear with me if I am being thick ? I am running into an error that looks like this: SystemC 2.3.1-Accellera --- Sep 7 2015 10:55:18 Copyright (c) 1996-2014 by all Contributors, ALL RIGHTS RESERVED Initator started Waiting Responder started Error: (E115) sc_signal<T> cannot have more than one driver: signal `signal_0' (sc_signal) first driver `init.func1' (sc_thread_process) second driver `resp.func2' (sc_thread_process) first conflicting write in delta cycle
  3. I am using sc_inout<struct T> to emulate a handshake flow of 'ready' and 'valid'. 'ready' flows in Responder --> Initiator and 'valid' flows in Initiator --> Responder. The setup doesnt work and causes the simulation to hang at 'Waiting'. I don't get a waveform because the simulation never completes. I suspect Can someone tell me if there are things I am overlooking: Can struct contain signals that flow in different directions? Can sc_inout<struct T> also map directly to another module with the same sc_inout<struct T>? Am I also setting t
  • Create New...