![]() |
![]() |
![]() |
![]() |
![]() |
Interactive Mode
You can use the Targeting Expert interactive mode to achieve different targets to:
- Build an un-configured or optimized target executable by following the steps described in Targeting Work Flow.
- Configure the distributed SDL Suite release and handle the already done settings. Please see below.
Although most of the steps in targeting are supported in the Targeting Work Flow you sometimes need access to other functionality, for example:
- Compiler Definition for Compilation to the target library's known compilers.
- Communications Link Definition for Compilation (for the inter-communication with the SDL Target Tester's host application).
- Handling of Settings
- Customization
Compiler Definition for Compilation
All the modifications that can be done here are only valid for the current system, i.e. all the information will be stored into the system's target directory.
Add
The following is applicable only if using the Cmicro SDL to C compiler:
Select Add a new Compiler from the Edit menu. The Add compiler dialog is displayed.
- Compiler Name
- The text you enter here will be used to identify the compiler in the Compiler Flag list.
- Compiler Macro
When you click Add the compiler is added to the c*_conf.def file. Please see Configuration Files for information about the file's syntax and duty.
Edit
For each compiler that is supported by a target library there is a specific section in
- scttypes.h (Cadvanced), see Compiler Definition Section in scttypes.h.
- ml_typ.h (Cmicro), see Adaptation to Compilers
- extreme_kern.h (Cextreme), see Compile and Link an Application.
Whenever there is a compiler flag defined, not known by the library, a file called user_cc.h (for Cadvanced and Cmicro) or comphdef.h (for Cextreme) will be included which has to contain the compiler specific settings.
The dialogs shown below are input masks that request all the needed information to generate such a file. Select Edit Compiler Section from the Edit Menu.
Cadvanced
For Cadvanced the following is requested:
Cmicro
For Cmicro the following is requested:
- #define xptrint
- #define xint32
- The compiler is able to handle function prototypes as in ANSI C
- The micro controller/processor is faster in accessing characters than integer values.
- The compiler supports variables stored in registers
- The compiler is able to handle the C keyword <const> in the correct way
- Target platform offers OS functions
- Critical paths
All the commands you enter will be copied in to user_cc.h. If there is more than one line of source code, each line must end with a '\' because the compiler's preprocessor depends on it.
- "no more memory" action
- Kernel exit
- Include paths
- User definitions
Remove
The following is applicable only if using the Cmicro SDL to C compiler:
To remove a compiler from the private c*_conf.def file, select Remove an Unused Compiler from the Edit Menu
The file user_cc.h will not be affected by removing a compiler from the c*_conf.def file.
Communications Link Definition for Compilation
The following is only applicable if using the Cmicro SDL to C compiler.
All the modifications that can be done here are only valid for the current system, i.e. all the information will be stored into the system's target directory.
Add
To allow the selection of a new communications link in the Targeting Expert user interface the appropriate macros should be given in the Targeting Expert.
Select Add a User Defined Communications Link from the Edit Menu.
- CommLink Name
- The text will be shown in the Targeting Expert UI to identify it in the dialog described in Configure the SDL Target Tester (Cmicro only).
- CommLink Macro
- CommLink Group
- Dependent Flags
- Add List
- A dialog where you enter a Value List is displayed.
- Add Text
- A dialog where you enter a Text Value Flag is displayed.
- Remove
When you click Add the communications link is added to the c*_conf.def file. Please see Configuration Files for information about the file's syntax and duty.
The communications link source code has to be set up by the user.
Value List
When you click Add this value list is added to the communications link you entered in the dialog in Figure 520.
Text Value Flag
When you click Add this value list is added to the communications link you entered in the dialog shown in Figure 520.
Remove
To remove a communications link from the private c_conf.def file, select Remove a communications link from the Edit Menu.
Handling of Settings
General
The integration tool bar on the main window offers four buttons to handle the settings, i.e. the way settings are stored and where they are taken from can be influenced.
The settings addressed in this section are only compiler, linker and make settings. The configuration of the SDL to C compiler library is not touched!
After selecting pre-defined integration settings the Targeting Expert automatically creates a file called <integration_name>.uis in the according component directory. (Please see Target Sub-Directory Structure).
For some reasons it is sometimes useful to modify this way of saving the user done settings. E.g.
- After doing an adaptation for a specific target the manually modified settings can be exported as new pre-defined integration settings. Please see Export.
Estimated there is an integration 'A' and there are modified settings on this integration on application, node and component level. Then there are three different files A.uis saved in the correspondent application, node and component directories.
Figure 525 shows where the settings can be done and where they are taken from when the component is selected.Export
The settings of the currently selected integration will be exported as new Pre-defined Integration Settings with the name given in the first dialog that pops up.
All the integrations must have unique names, i.e. it is not possible to export settings with an already known name.
In the second dialog a list of template files which have to be copied into the target directory can be specified. As default, the list of files from the "parent" settings will be given. Modify the list to your needs. Directly after exporting the settings they can be used for further configurations.
The sections Configuration Settings to Be Set and Configuration Settings to Be Reset are not exported.
Customization
The Targeting Expert interactive mode can be customized. After selecting the Customize entry in the Tools Menu the dialog shown in Figure 527 pops up.
Text Editor
The text editor which should be opened to edit or view text files can be selected here. The list of supported editors depends on the platform the Targeting Expert is running on (Windows/UNIX). It can be modified or extended in the file sdttaex.par. Please see Parameter File sdttaex.par.
Advanced Mode
The advanced mode allows you to:
- do more configurations than possible in the non-advanced mode. See More Configurations for more information.
- switch between different dialogs without using the Cancel or Save button
- start the code generation automatically when selecting a new integration
- configure all compilers. Even the ones that are not available on the used platform.
More Configurations
- Normally there is no need to modify the compiler flag if using a pre-defined integration, but in the advanced mode the Compiler Flag can be modified.
- The standard pre-defined integrations do not allow you to use all the configuration options in the Configure and Scale the Target Library dialog (disabled). If the advanced mode is switched on, it is possible to switch on and off all the options supported by the SDL to C compiler library.
The pre-defined integrations distributed are tested only with the given library configuration. It is not guaranteed that it will work for all kinds of modifications!
http://www.ibm.com/rational |
![]() |
![]() |
![]() |
![]() |