Jump to content

Meir

Members
  • Content Count

    5
  • Joined

  • Last visited

  1. thank you very much. needless to say i did some readings, but i am guessing not with the appropriate sources.
  2. hey all. lets say i have the following SC_THREADS, with the sensitivity of rising clock edge. thread 1: takes a variable 'cur_address' and uses it to access a memory. thread 2: updates the value of 'cur_address' depending on a given logic. since i cant tell the order of which the threads execute, is it possible that thread 1 will be invoked twice (for example) before the 'cur_address' variable updates ? thank you in advance, Meir
  3. hey. any chance getting a reply ? thank you !!
  4. hey. thanks for replying. the code that i posted was a snippet. it did include the wait() statement. so my questions still remains: 1. what is the right use case for SC_CTHREAD ? 2. why in my give example the simulation gets "stuck" ? thanks
  5. Hey all. i am a novice user of SystemC, and couldn't find an answer to the following question? ive noticed that when ever i tried using SC_CTHREAD(proc_name, clk.pos()) -> the simulation time was increased significantly (to a level where it appeared to be stuck). what is the right use of SC_CTHREAD so that it doesnt jam the simulation? i am adding an example of what i did: SC_CTHREAD(monitor_intr_in, clk.pos()); ... void TMG_helper::monitor_intr_in() { while(true) { cout << "i am here" << endl; } } thank yo
×
×
  • Create New...