Delphi User Guide for TargetLink - dSPACE

Why?• To generate efficient code.• To create interfaces for integration of generated code into asoftware application.How?• Replace User library blocks (subsystems) in original Model withcorresponding Delphi Simulink and Stateflow User library blocks(subsystems): Timers, Counters, Filters, PIDs. These library blocksassure efficient TargetLink code generation.• Follow Delphi structure of Component’s model.• Follow Delphi Procedures and Guidelines for Modeling andTargetLink code generation.16 May 2002 dSPACE Users Conference 5

Structure of Component’s ModelFunctionsUtility BlockTask ManagerProvides model structuresimilar to that of softwarefile:• File Task Manager defines function execution orderInterface Block• Function Blocks: Initialization Block, SL Block(s), SF Block(s) represent correspondingfunction in generated software• Utility Block models functions that already exist outside of current model but need to beimplemented in a component for proper model simulation ( like library functions ).• Interface Block models calls to functions that already exist outside of current model (likecalls to HWIO routines). These functions are not needed for proper model simulation.6

Delphi Procedures and Guidelinesfor Modeling and TargetLink code generationExecutable Specifications:1. Delphi Executable Specification Style Guidelines2. Delphi Simulink/Stateflow Reusable Libraries3. Delphi Guide for Modeling/Autocoding- How to do the initialization of the Model- How to work with OS- How create a model for efficient code generationAutocode:Delphi User Guide for TargetLink- How to work with TargetLink Property Manager for generation of efficient code.- How to generate code per Delphi C-language coding standards.- How to integrate auto-code with hand-written legacy codeSoftware Validation:Delphi Procedure for Code Verification vs. Executable Specifications.16 May 2002 dSPACE Users Conference 7

Delphi User Guide for TargetLink targets followingCriteria for Autocoding:• Model must comply with MAAB Style Guidelines andDelphi Executable Specification Guidelines.• No hand modifications in autocode s/w• Limited or no increase in Project budget(ROM/RAM/Throughput)• Usage of existing hand-written standard routines( Lookups, Timers, Filters, etc)• Straight forward integration process of Autocodeinto hand-written s/w16 May 2002 dSPACE Users Conference 8

Delphi User Guide for TargetLinkDetailed document walking through the process of applying TargetLink to aSimulink/Stateflow model to generate production-quality code.9

BenchmarksROM RAM Stack ThroughputHand-written files 1-8 KByte 50-200 Bytes 20-200 Bytes Machine cyclesRatio:TargetLink autocode /Hand-written code0.96 -1.1 0.97 - 1.2 1.2 - 1.25 0.98 - 1.2Comparison of TargetLink-generated code vs. hand-written production code for anumber of Delphi algorithms for CPU32 and HC12 target processors.16 May 2002 dSPACE Users Conference 10

Verification16 May 2002 dSPACE Users Conference 11

Summary• TargetLink proved to have technical ability to generate code per Delphisoftware standards.• TargetLink support group of dSPACE provides outstanding technicalsupport from offices in USA and Germany.• Delphi will continue use TargetLink as a code generator for productionsoftware.Area of TargetLink improvement:• Enable to work with Nested Data Structures and Bus Structures.• Modify TargetLink Property Manager graphical appearance.• Add new features for easy up-integration and reusability of autocode:– Ability to modify interfaces between model components without changes of TLproperties of individual components.– Ability to disable scaling for subsystems that represent subroutines.• Provide ability to develop autocode under Software ConfigurationManagement system (CM Synergy)• Add features for code validation: generation of Test Vectors and codecoverage.12