leoeltipo

Hi Karsten, Thank you very much for your answer!!!! This line makes the difference: this->request_next_activation(max_timestep,inp->default_event()); As it allows me to maintain the resolution of the PWM module. I read about Dynamic TDF but did not know how to apply it here. Thank you again!!! Kind regards, Leandro

Hello all, I have been working with SystemC some time. I am entering the SystemC-AMS world. I have this system: Processing algorithm (SystemC DE) PWM generation (SystemC DE) LPF (SystemC AMS, ELN) I want to argument the selection. The processing part was already done and is almost digital, that's why DE is used for the modelling. PWM generation is crucial in this application, as errors or quantization of the pulse position would result in distortion after demodulation. Using SystemC DE allows to toggle the signal at exact moments in time, without adding any quantization t

Hello, I would like to be able to overload operator<< to be able to print transaction information (assuming tlm_generic_payload for transaction type). I think on two alternatives: 1) ostream& operator<<(ostream& os, tlm_generic_payload& trans): the problem is that operator<< should be declared a friend function inside the definition of class tlm_generic_payload, and that is not the case. 2) Define a new class derived from tlm_generic_payload with the friend declaration. The problem is that I sould change the transaction type all over the design, an

To continue with this topic a little bit, I understand that a socket has an sc_port and sc_export. However, what is confusing for me is that tlm_base_initiator_socket inherints from sc_port but instantiate an object of type sc_export. Otherwise, the "sc_port" part of the socket shoul also be bound with an interface... Correct me if i am wrong... Thanks

Hello, Thank you very much to both of you guys!!!! Now it is really clear for me. Thanks again!!! Leo

Hello, I am new in the SystemC-TLM world. I am reading the LRM and looking at an example (chapter 13, systemc LRM, page 462). In the module constructor it is written ... init_socket.bind(*this); // Initiator socket bound to initiator itself ... The rest of the code is of no use for the sake of the question. I don't understand why the socket must be bound to the module itself. The example continues and the socket is bound to a target socket, but I don't get this one... Thank you in advance. Leo