Overview of ECROS Initialization

The flow of execution control in an ECROS application is as follows:

• The client application provides start-up code and initializes the C language environment.
• API function OsInit() is called to allow ECROS to perform internal initialization.
• The application now performs its own initialization.  ECROS API functions are used to set up tasks, send events, create timers and message queues, etc.
• API function OsStart() is called to hand over control to ECROS.
• Task functions in the application are executed under control of the scheduler.
• The application may terminate execution using the normal C language exit mechanism from any task function.