C
comp.arch.fpga
Guest
Hmm. Your definition of a state machine differs from established FSM
theory.
You focus only on the textual description.
With your definition a CPU-core and its ROM is not a state machine.
Also a shift register used to control other logic would not be a state
machine.
Any script generated state machines also do not count.
Self resetting state machine (JTAG controller anyone?) are also no
state machines because there is no reset signal.
The definition of a state machine that I am used to is:
A set of storage elements that are connected in a way that the
following state of the elements depends on the previous state.
State machines can be arbitrarily partitionend and merged. The whole
chip can be analyzed as one big state machine (usually not a big idea)
or each individual flip-flop can be interpreted as a state machine
(also often a bad idea).
But to give you the benefit of doubt and return to your orginal
question:
Smith-Waterman hardware implementations instantiate tens of thousands
of identical state machines.
Oh, wait, the implentation that we used had not reset. Damn.
Kolja Sulimma
On 17 Sep., 21:43, Weng Tianxiang <wtx...@gmail.com> wrote:
theory.
You focus only on the textual description.
With your definition a CPU-core and its ROM is not a state machine.
Also a shift register used to control other logic would not be a state
machine.
Any script generated state machines also do not count.
Self resetting state machine (JTAG controller anyone?) are also no
state machines because there is no reset signal.
The definition of a state machine that I am used to is:
A set of storage elements that are connected in a way that the
following state of the elements depends on the previous state.
State machines can be arbitrarily partitionend and merged. The whole
chip can be analyzed as one big state machine (usually not a big idea)
or each individual flip-flop can be interpreted as a state machine
(also often a bad idea).
But to give you the benefit of doubt and return to your orginal
question:
Smith-Waterman hardware implementations instantiate tens of thousands
of identical state machines.
Oh, wait, the implentation that we used had not reset. Damn.
Kolja Sulimma
On 17 Sep., 21:43, Weng Tianxiang <wtx...@gmail.com> wrote:
Hi Glen,
There is a theory behind to resolve the problem.
A state machine can be defined in such a scentific way:
1. All states in a state machine have their own names;
2. All states in a state machine are mutually exclusive;
3. Only one state is active in any cycle;
4. The number of states in a state machine must be 2 or more;
5. There must have either asynchronous or a synchronous reset signal
for the state machine and after their assertion, the state machine
must be in initial state.
I guess there are less than 27 engineers in the world who have the
experiences to do the designs.
If your experiences are fully in FPGA and VHDL worlds, you may never
have a chance to get a right guess with any possible wildest
imagination,
Any more question?
Weng