Minimum RTI

MotoHawk supports many different modules that use different processors. Below is the capabilities of how fast the modules can run a bare-minimum application* without watchdogging.

Module / Family	Processor	Freq.	FGND_RTI_PERIODIC (min.)
ECM-0555-048-xxxx	MPC555	40 MHz	200 usec
ECM-0555-080-xxxx	MPC555	40 MHz	(not tested)
ECM-0563-048-xxxx	MPC563	56 MHz	100 usec
G/HCM-0563-048-xxxx	MPC563	56 MHz	100 usec
GCM-0565-024-0602-F	MPC565	56 MHz	(not tested)
ECM-0565-128-xxxx-F	MPC565	56 MHz	(not tested)
ECM-0565-128-xxxx-C	MPC565	56 MHz	150 usec
ECM-5554-112-09xx	MPC5554	80 MHz	50 usec
ECM-0S12-024-xxxx	HCS12	24 MHz	256 usec
GCM-0S12-024-04xx-F	HCS12	24 MHz	256 usec
ECM-S12X-070-xxxx	HCS12XE	50 MHz	250 usec

* Application:  Target Definition block, CAN Definition block for CAN1 with MotoTune, MotoHawk Trigger Definition block, and a FGND_RTI_PERIODIC task.  
The task contains (1) a Data Definition, Data Read, Simulink Constant, Simulink Sum, and Data Write block to implement a uint32 counter, and  
(2) a Discrete Out block configured as EST or LSO to toggle an output, where a 1/Z block and NOT block are used to form a boolean toggling input to the Discrete Out block.

This info can be useful when using a Trigger Definition Block, more details can be found MotoHawk:Blocks:Function_Trigger_Block here.