ARI

Hi Eyck, Thanks for your reply. As you said libqt.a will be part of libsystemc lib. can we generate it separately? Best Regards, ARI

Hello Everyone, I hope this msg finds you all well. I am currently working on a project that requires building and generating the `libqt.a` library using the `qt` package available at `systemc-2.3.3/src/syscsysc/packages/qt`. As I'm relatively new to this process, I am reaching out to seek your assistance and guidance. I have already set up the necessary development tools and dependencies on my system. However, I am unsure about the specific steps required to build the library successfully. I would greatly appreciate it if you could provide me with some simple instructions or pointers on how to proceed. If you could kindly share the relevant build commands or any essential tips, it would be of immense help in completing this task. I want to make sure I can utilize the `libqt.a` library effectively for my project. Thank you for considering my request, and I'm looking forward to your valuable assistance. Please let me know if you require any further information from my end. Thanks and Regards, ARI

Hello Everyone, Could anyone please help me to understand the use cases of transport_dbg and when to use it. Is it mandatory to have implementation of tranport_dbg in target side? How to bypass transport_dbg and use only b_transport. Thanks ARI

Hi David, Thanks for your reply. First, why the focus on a DLL? -> I can only use DLL in my project, I can't use static SystemC lib. where did you define sc_main? -> For the moment, I wants to use SystemC DLL in the simple hello world example. But I am unable to create the DLL first. any suggestions on how to resolve the errors? Thanks.

I want to create the SystemC DLL but failed, while building the SystemC 2.3.2 I get the following errors: --sc_main_main.obj : error LNK2019: unresolved external symbol sc_main referenced in function sc_elab_and_sim --x64\DebugDLL\SystemC.dll : fatal error LNK1120: 1 unresolved externals. How to resolve this error, any help will be appreciated. Please find the project properties setting. Thanks, ARI

Hello Everyone, Could anyone please let me know what is the difference between Axi and TLM2.0. Which one is better, and where we can use both. Thanks

Hi @Andy Goodrich Thanks for your reply, why I am not using SC_CTHREAD, the reason behind it, I don't want the FSMMethod call again and again at every posedge of clock. In SystemC we generally design a model at higher abstraction, if we use clock then simulation would be slow, that's why I have to prefer next_trigger.

Thanks @karthickg for your reply and valuable suggestion, it really help me a lot.

Hello Everyone, I was trying to implement FSM in SystemC using SC_METHOD and next_trigger(). In the requirement it is mentioned i can't use SC_THREAD and static sensitivity (except reset_input). I am facing one problem here, which mentioned in screen-shot. In the attached screen-shot, whenever the current_state is FIRST then next_state could be SECOND, THIRED, and FOURTH (the priority of next_state is SECOND > THIRED > FOURTH). I am able to write a code using next_trigger when next_state is only one and not many. Here is the raw code: sc_in<bool> Reset_in; sc_in<bool> First_in ; sc_in<bool> Common_in; sc_in<bool> Second_in; sc_in<bool> Third_In; sc_in<bool> Fourth_in; SC_METHOD(FSMMethod) sensitive << Reset_in; async_reset_signal_is(Reset_in, false); dont_initialize(); void FSMMethod() { if (Reset_in == false) { current_state = RESET; next_trigger(); } else { switch (current_state) { case RESET: next_state = FIRST; next_trigger(First_in.posedge_event()); // now you can see when FSM is in RESET state then if First_in signal value become one //then FSM method will call again due to next_trigger and that time the next_state would be FIRST. break; case FIRST: // I am stuck here, if Common_in and Second_in signal true then next_state should be SECOND but the problem // is during the execution it will go inside the if block, if block not executed then next_trigger condtion // will not trigger the sc_method again and FSM will not in next_state. if (Common_in && Second_in) { next_state = SECOND; next_trigger(Common_in.value_changed_event() & Second_in.value_changed_event()); } else if (Common_in && Third_in) { next_state = THIRD; next_trigger(Common_in.value_changed_event() & Third_in.value_changed_event()); } else if (Common_in && Fourth_in) { next_state = FOURTH; next_trigger(Common_in.value_changed_event() & Fourth_in.value_changed_event()); } break } current_state = next_state; } } Hope i am able to put my question but if you guys need more clarification then please let me know. ultimatly i am not able to call FSMMethod beacuse next_trigger not executed in FIRST state, first we to have evalaute the transition condition then only next_trigger will execute. if in FIRST state if next_state were only one then it would be easy to use next_trigger (just in case we used in RESET to FIEST state) Please give me your valauble suggestions so it help to implement this FSM design. Thanks and Regards, ARI