Transaction-level modeling: Difference between revisions

Revision as of 09:02, 17 August 2018

Revision as of 23:39, 29 March 2021

Line 4:

==History==

TLM was supposed to come out as TBM (= transaction-based modeling). In 2000, Thorsten Grötker, R&D Manager at [[Synopsys]] was preparing a presentation on the communication mechanism in what was to become the [[SystemC]] 2.0 standard, and referred to it as "transaction-based modeling:. Gilles Baillieu, then a corporate application engineer at [[Synopsys]], insisted that the new term had to contain "level", as in "[[register-transfer level]]" or "behavioral level". The fact that TLM does not denote a single level of abstraction but rather a modeling technique didn't make him change his mind. It had to be "level" in order to make it stick. So it became "TLM".{{Citation needed|date=March 2008}}

Roots of the term '''TLM''', or "'''Where is the Level in TLM?'''"

The Open SystemC Initiative was formed to standardize and proliferate the use of the SystemC language. That organization is sponsored by major [[Electronic design automation|EDA]] vendors and user customers sharing a common interest in facilitating tool development and IP interoperability. The organization developed the OSCI simulator for open use and distribution.

TLM was supposed to come out as TBM (= transaction-based modeling). In 2000, Thorsten Grötker, R&D Manager at [[Synopsys]] was preparing a presentation on the communication mechanism in what was to become the [[SystemC]] 2.0 standard. Gilles Baillieu, then a corporate application engineer at [[Synopsys]], insisted that the new term had to contain "level", as in "[[register-transfer level]]" or "behavioral level". The fact that TLM does not denote a single level of abstraction but rather a modeling technique didn't make him change his mind. It had to be "level" in order to make it stick. So it became "TLM".{{Citation needed|date=March 2008}}

The Open SystemC Initiative was formed to standardize and proliferate the use of the SystemC language. That organization is sponsored by major [[Electronic design automation|EDA]] vendors and user customers sharing a common interest in facilitating tool development and IP interoperability. The organization developed the OSCI simulator for open use and distribution.

Since those early days SystemC has been adopted as the language of choice for high level synthesis, connecting the design modeling and virtual prototype application domains with the functional verification and automated path gate level implementation. This offers project teams the ability to produce one model for multiple purposes. At the 2010 DVCon event, OSCI produced a specification of the first synthesizable subset of SystemC for industry standardization.