Configuration is an important part of using SYS/BIOS. When a designer builds an application, one of the files in the project will have a .cfg extension which is where the configuration information is kept. Configuration has a lot of use and benefits. It is used for specifying which BIOS modules will be used in the app. So for example, if an application uses the Clock module then this would be referenced in the config file to ensure that the Clock module code is linked in to an image. Also, the actual instances of each Clock can be specified at configuration time. A number of the SYS/BIOS modules are interdependent, so the configuration tool will make sure that any dependent code is brought in as well. As another example, by specifying the use of the Clock, the config tool will automatically bring in the Software Interrupts module as well and create a corresponding Swi object for the Clock’s use. Configuration can be used to specify a number of options for both the module and each instance. There are two basic ways that the config file gets edited. The first is direct just like any other source code file. In this case, the .cfg file is not implemented in C, but rather in a scripting language based on Javascript. The nice thing about this is that the user can use their favorite editor on the file and the scripting language provides a very rich way to implement it. In addition to the fundamental ways of creating objects and setting their parameters, the scripting language provides all the things that one would expect to control it, such as if statements and looping constructs. The second way to set up the config file is to use the visual editor that comes with the SYS/BIOS product. This tool is called “XGCONF” and provides an easier and more intuitive configuration technology. The results are presented in a visual way and it also has the additional benefit of doing a lot of error checking on the fly, the user will see errors almost immediately, rather than when the project is built.