Simulink Supported Block Details
From UcgnWiki
(→Lookup) |
(→Signal Routing) |
||
Line 32: | Line 32: | ||
* The MultiportSwitch does not support the two-input usage as a selector, indexing into an array. Please use the Selector block instead | * The MultiportSwitch does not support the two-input usage as a selector, indexing into an array. Please use the Selector block instead | ||
+ | * The code generated from the MultiportSwitch will rely on a utility function (in GBL_Saturation.c, located in the Sources folder of the distribution) to guard the selecing input | ||
* Both the Switch and MultiportSwitch currently support only the switching of basic (and enumerated) types, not bus types | * Both the Switch and MultiportSwitch currently support only the switching of basic (and enumerated) types, not bus types | ||
* From/Goto block are useful tools to structure a complex design which would otherwise have many crossing signal lines. But, From/Goto blocks can only be used with a local scope. They are basically non-functional, simply hiding a signal line from view. From/Goto blocks with global scope would have to be represented by global variables. Such a concept is not supported by design, as this would open alternative data paths to the current paradigm that data flow across hierarchy levels will follow an equivalent procedure call hierarchy. | * From/Goto block are useful tools to structure a complex design which would otherwise have many crossing signal lines. But, From/Goto blocks can only be used with a local scope. They are basically non-functional, simply hiding a signal line from view. From/Goto blocks with global scope would have to be represented by global variables. Such a concept is not supported by design, as this would open alternative data paths to the current paradigm that data flow across hierarchy levels will follow an equivalent procedure call hierarchy. |