both I and sclive said that is possible, but giving a wrong readable example.

you have to use the instead of the ( and the )

sc_in(my_struct) packet_rx;

sc_in packet_rx;

Good point about the SC_CTHREADs. I did leave them out because they were deamed as deprecated since you could achieve much of the same with say an SC_THREAD and a sensitivity list that had something like clk.pos() inside it.
Nevertheless there is a lot of activity recently on SystemC synthesis and in this specific context SC_CTHREAD are the way ahead to model clocked logic. More so since the SC_THREAD are not supported in SystemC synthesis.

Thanks for your remark, I should put a little tutorial on the subject of SystemC synthesis and restore the SC_CTHREAD to its rightfull place.

As far as dont_initialize() is conserned, it’s purpose is to avoid processes to be executed at initialisation time ( straight after elaboration and just before simulation). Its often found when you may encouter undeterministic behaviour depending on the order of execution of your processes. In other work if one process starting first may block another process.
I hope that helps, I think I would need an example to better illustrate that.

Regards,

David Cabanis

But try to expand it a bit more and elaborate more on the software side of systemC coding. I am weak at that side.

A question, see the code:

class pv2rtl: public sc_module, trans_if {
public:

sc_in

pv2rtl(sc_module_name nm) : sc_module(nm),
tlm_slave(”tlm_slave”),

…..
….

so, How shall we write it in the VHDL type notation…I am more easy with that representation….. see U