Jump to content

TLM transport_dbg API

Recommended Posts

I read in duolos website that in TLM2 transport_dbg API is to read or write memory in the target without causing any side-effects and without simulation time passing.

My question are

1. Is without simulation time passing means we can not call wait inside that function ? Am I right ?


2. It says "without causing any side-effects" but there may be case when writing some data on target memory may trigger some target functionality. What happen in this case ? Will that functionality will not be triggered ? What "side effects" are not caused by calling transport_dbg ?


Thanks in Advance



Link to comment
Share on other sites

Hi, yes, obviously a transport_dbg write causes a side effect (the written data). So you're correct. However a read should have no effect on the system.


You can call transport_dbg from a function, however the transport_dbg call itself must not result in change of simulation time (it returns without calling wait() or notifiying any events). So yes it cannot call wait().




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.

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...