Jump to content

TLM_INCOMPLETE_RESPONSE


Recommended Posts

I build a constructor with the following {

tlm_utils::simple_initiator_socket<Init1> socket;

char buffer = A;
SC_THREAD(run);

}


run() {

        tlm::tlm_generic_payload trans;
        trans.set_command(TLM_READ_COMMAND);
        trans.set_data_ptr((unsigned char*)buffer);


        if ( trans.is_response_error() )
        {
          char txt[100];
          sprintf(txt, "Error from b_transport, response status = %s",
                  trans.get_response_string().c_str());
          SC_REPORT_ERROR("Error 1", txt);
        }

 

        socket->b_transport(trans, delay);

 

}

I usually got the error "TLM_INCOMPLETE_RESPONSE". Could you please support where can I find the issue?

Is the problem in the buffer?

Link to comment
Share on other sites

If you will read the SystemC standard, you will see that Initators are required to set the response initially to TLM_INCOMPLETE_RESPONSE. Targets are obliged to change this to either TLM_OK_RESPONSE or one of the valid error returns. Seems your downstream targets never saw the transaction. Perhaps the address decoding (in the interconnect) went wrong. You are obliged to set the command, address, data pointer, data length, streaming width, byte enable pointer, DMI hint and response. I suggest RTFM, then debug the interconnect andr targets for a receipt.

Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

×
×
  • Create New...