Changes between Version 32 and Version 33 of Writing Rules/Caba

Timestamp:

Sep 20, 2017, 11:34:58 AM (7 years ago)

Author:

alain

Comment:

--

Writing Rules/Caba

@@ -11 +11 @@
 This manual describes the modeling rules for writing "cycle-accurate / bit-accurate" SystemC simulation models for SoCLib. Models complying with those rules can be used with the "standard" OSCI simulation engine (SystemC 2.x), but can be used also with others simulation engines, such as SystemCASS, which is optimized for such models.
 
-Besides you may also want to follow the [WritingRules/General general SoCLib rules].
-
 Those CABA modeling rules are based on the "Synchronous Communicating Finite State Machines" theory. The idea is to force the "event driven" SystemC simulation engine to run as a cycle based simulator.
 
@@ -20 +18 @@
 
 If all internal register are clearly identified, any FSM can be described by three types of functions:
- * The '''transition function''' computes the next values of the register, depending on the current values of the register and the values of the input ports signals.
- * The '''genMoore function'''  computes the values of those output port signals that depend only on the internal registers.
- * The '''genMealy function(s)''' computes values of those output port signals that depend both on the internal registers AND the values of the input port signals.
-
-In this figure we represented a single FSM, but a SoCLib component contains generally several small FSMs running in parallel inside a single module. This internal parallelism should be properly described.
+ * The '''transition function''' computes the next values of the registers, depending on the current values of these registers and the values of the input signals.
+ * The '''genMoore function'''  computes the values of those output signals that depend only on the internal registers.
+ * The '''genMealy function(s)''' computes values of those output signals that depend both on the internal registers AND the values of the input signals.
+
+In this figure we represented a single FSM, but a SoCLib component contains generally several small FSMs running in parallel inside a single module. This internal parallelism must be properly described.
 
 = B) CABA rules =