Difference between revisions of "LDRA Integration for Model References"

From T-VEC Wiki
Jump to: navigation, search
(Update Model Reference Names and Types)
(Start TBrun and Load New Test Sequence)
 
Line 31: Line 31:
 
[[Image:stoplight_sm_example.png|Model Reference Code Generation]]
 
[[Image:stoplight_sm_example.png|Model Reference Code Generation]]
  
The names extracted from the exported model information do not necessarily correspond with the different the code generation works. There is tool provided with the release called
+
The names extracted from the exported model information do not necessarily correspond to the names produced by the code generator. There is a tool provided with the release called
  
 
  get_rtw_types.bat --- Download it here [http://www.t-vec.com/download/get_rtw_types.bat get_rtw_types.bat]
 
  get_rtw_types.bat --- Download it here [http://www.t-vec.com/download/get_rtw_types.bat get_rtw_types.bat]
Line 112: Line 112:
 
In addition the corresponding variables rtu_0 and rtu_1 are replaced in their corresponding object mappings with the variables rtu_0_obj, and rtu_1_obj.
 
In addition the corresponding variables rtu_0 and rtu_1 are replaced in their corresponding object mappings with the variables rtu_0_obj, and rtu_1_obj.
  
Finally, the updated version of the program updates the following 5 variables to the other dependent object mappings files. These dependent files are defined in the user defined variable:
+
Finally, the updated version of the program updates the following 7 variables to the other dependent object mappings files. These dependent files are defined in the user defined variable:
  
 
  <dependencies> = '__triggerFallingB,signal_light__sf__a';
 
  <dependencies> = '__triggerFallingB,signal_light__sf__a';
Line 121: Line 121:
  
 
  <functionName>
 
  <functionName>
  <rtDWStruct>
+
  <isModelReference>
  <rtZCEStruct>
+
  <isReusable>
 
  <ldraExternalDeclarations>
 
  <ldraExternalDeclarations>
 
  <ldraParameterPointerInitialization>
 
  <ldraParameterPointerInitialization>
 +
<rtDWStruct>
 +
<rtZCEStruct>
  
 
If any of these variable do not exist, one is added just before the following line:
 
If any of these variable do not exist, one is added just before the following line:
Line 156: Line 158:
 
*Process Driver Output
 
*Process Driver Output
  
Note: during the Generate Driver process, you might see the following LDRA Question - Answer '''None'''.
+
Note: during the Generate Driver process, you might see the following LDRA Question
 +
 
 +
Dataflow analysis has detected that output parameter "rty_0" is used in the unit
 +
tested by test case 1.
 +
 +
Adding this value to the test case will result in the test case not running until
 +
an expected value is provided
 +
 +
Not adding this variable will add it to the removed variables list from which it
 +
can be restored at a later date if required. The test case will then be executed as
 +
previously, but may fail to compile.
 +
 +
Do you wish to automatically add this variable to the test case?
 +
 
 +
Answer '''None'''.
  
 
====Pre/Post Includes might be necessary====
 
====Pre/Post Includes might be necessary====

Latest revision as of 10:35, 30 June 2008