Bart,
just a quick response to your comment on sc_writer_policy below.
On 22/12/10 11:24, Bart Vanthournout wrote:
>
> Section 7:
>
> 7.4.4: why limit the sc_many_writers policy to different delta cycles?
To guarantee a well-defined, deterministic behaviour.
> If I have 2 TLM2 initiators it’s likely that they will evaluate in the
> same delta cycle so I still cannot write to a signal from the TLM2
> initiators (although there is a simple workaround, but that one is
> rather silly…)
I think, conflicting writes to a single signal within the same delta are
most probably unwanted. One of the (two) writes will just vanish into
the void.
Which one of the two initiators should win, if both perform a write
within the same delta? The behaviour would depend on the internal
scheduling of the simulator.
In the usual case (and in the final system), incoming transactions
would be arbitrated somehow to avoid such races. Technically, you can
still have multiple writers (e.g. from different TLM initiators), but if
writes are performed in distinct deltas at least no write is silently lost.
Greetings from Oldenburg,
Philipp
-- Philipp A. Hartmann Hardware/Software Design Methodology Group OFFIS Institute for Information Technology R&D Division Transportation · FuE-Bereich Verkehr Escherweg 2 · 26121 Oldenburg · Germany · http://www.offis.de/ Phone/Fax: +49-441-9722-420/282 · PGP: 0x9161A5C0 · Skype: phi.har -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean.Received on Wed Dec 22 07:38:01 2010
This archive was generated by hypermail 2.1.8 : Wed Dec 22 2010 - 07:38:04 PST