Each plug-in module of XPad has a compiler supporting a specific family of devices and comes with a large number of libraries.
For each family target-definitions can be developed (by GenerExe or by you), customizing the plug-in for specific device and/or (inhouse) platforms. Easy to understand script-files are used to add:
fully graphical hardware configuration editors
fully graphical simulation panels (traces)
wizards and platform-specific template models.
Target-family and/or device specific libraries can be easily added to extend XPad's library suite!
A loaded target adds the following target-specific functionality to XPad:
n environment/hardware configuration editor
, allowing you to specify the "physical" context of your software: hardware interfaces/protocols for embedded targets, but also Windowed user interfaces for Windows-CE and PalmOS targets; Most targets allow you to highly customize the configuration editor to match the look and feel you prefer and/or that fits the specific target-device of the family of devices supported.
Built-in libraries of functions which can be called from blocks in the flow-diagrams. These will show up when you use the function-editor to insert/edit an entry in a flow-block. With some knowledge of the target's native instruction-set it is easy to add your own libraries;
arget variables" in the data-browser, which represent global configuration/execution registers of the target. Most of the time you won't need to access these variables. I.e. you can find the status-register of a microcontroller here or some scheduler-option for a higher level environment (i.e. which comes with an Operating System API supported by XPad);
and control-windows to monitor and control the software's environment during simulation;
esource-editors for targets that support graphical user interfaces
arget specific help-files
explaining how to use the different features/functions of this target;
n optimizing compiler
generating either assembly (for micro controller targets) or runtime executables which can be loaded and executed on targets which come with built-in operating systems (i.e. for PalmOS).
any examples, templates
showing how to maximize the use of the different features;
For some targets, third party freeware tools may be included, you can use to assemble/load native target-files.