Shown here is a very simple sample of a config file. The first few lines are declarations that load specific modules and marks them as being used on the target. Each of these declarations are assigned to a script variable that can then be referenced later on. Once the user has declared a module as being used, they can modify config parameters associated with that module – in this case the user is setting the Swi modules number of priority levels to one, enabling Swis and Tasks and setting the power mode. Then lastly they are creating some kernel object instances, specifically two Swi software interrupt instances. One big question many users have is how objects that are created in the configuration world can be referenced by the application. The answer is that an application will pound include a header file called global.h that is created at configuration time. In this case, by doing so, the application will then be able to reference the Swi objects that were created here.