--- Quote Start ---
Hmm, please let me understand if I got what you are saying, so if I want to use this HDL Import block the "connecting chain" would be like:
Simulink Input -> In blocks (IO&bus) -> GPin , HDL Import , GPout -> HDL Input -> ? , Scope
The arrow means going deeper as level of subsystem, the coma means that those blocks are living in the same subsystem.
Im sure there is something wrong in that chain :D , could you please write down to me the right one?
--- Quote End ---
No if anything it should be:
Simulink Input, In blocks (IO&bus), HDL Import -> HDL Input -> GPin, <datapath> , GPout -> HDL Output -> Out blocks (IO&bus) , Scope
--- Quote Start ---
You could design an FSM with Advanced blockset but it can be quite tricky. It really depeds how complicated it is.
1- I would love to know how to do that!
2- Could it be possible to use StateFlow blocks in Advanced systems to design FSM?
3- At the end if one must use an FSM how do you advice to do that?
--- Quote End ---
1. To build a state machine out of advanced blocks, you would have to use the primitive blocks that are there. This means managing the state transitions yourself. It's not something I've done much on.
2. StateFlow blocks are not supported by either Standard or Advanced blockset.
3. If your FSM is only controlled by the inputs to the top level system and have no direct feedback from your datapath, then it probably easiest to build the statemachine. If you want lots of feedback into your state machine from your datapath then it may be easier to build it using advanced blocks.
Honored Contributor
