MATLAB: What is new in the Embedded Coder® Support Package for AUTOSAR in R2015b (15.2.6)

autosarEmbedded Coder

What is new in the Embedded Coder® Support Package for AUTOSAR in R2015b (15.2.6)?

Best Answer

The R2015b Embedded Coder Support Package for AUTOSAR Standard, Version 15.2.6, includes the following bug fixes.
Bug Fixes:
  • ARXML export now round-trips the initial values that were imported on Ports ComSpecs. Previously, export created default initial values on the Ports ComSpecs, replacing the imported initial values.
  • AUTOSAR validation no longer errors out when a model includes both nonvolatile (NV) data ports and a mode receiver port.
  • ARXML importer no longer errors out when the ARXML code contains PORT-API-OPTIONS. Previously, the importer threw the following error: "Element {} of type Simulink.metamodel.arplatform.behavior.PortAPIOption has no property named {}InitValue".
  • ARXML importer now throws a warning when the ARXML code specifies a ModeSwitchEvent TARGET-MODE-DECLARATION-REF reference that does not exist. Previously, the importer threw an error for this case.
  • AUTOSAR code generation now generates correct typedefs for void types in Rte_Type.h. Previously, the code generator generated the wrong typedef, which could cause compilation errors during software-in-the-loop (SIL) simulations.
  • ARXML export now correctly handles rounding errors when writing out CompuMethod coefficients. Previously, export could write coefficient values that looked like 0.99999999999999989.
  • ARXML importer now correctly imports runnables with self-feedback inter-runnable variables (IRVs) that is, IRVs that are only read and written by the same runnable. Previously, the importer threw the following error: Cannot map data transfer signal signalName because it does not exist.
  • ARXML importer now correctly handles ARXML code that produces merged array signals in Simulink. Previously, the importer created an uncompilable Simulink model.
  • AUTOSAR function autosar.api.syncModel now automatically maps unmapped Function Caller blocks for existing client-server operations to the same mapping as existing mapped function callers. Previously, the function did not complete the mapping and validation subsequently errored out. The issue affected only the function and not the Synchronize icon in the Configure AUTOSAR Interface dialog box.
  • AUTOSAR code generation now generates the return type of RTE function Rte_Mode_<p>_<o> as ShortName of ImplementationDataType of ModeDeclarationGroup. Previously, the code generator generated the return type as ShortName of ModeDeclarationGroup, which could cause compilation errors in the contract phase.
  • ARXML export now correctly generates only Internal DataConstr for enumeration data types, for both ApplicationDataType and ImplementationDataType. Previously, export generated duplicate DataConstr for enumeration data types because it tried to export Physical DataConstr for the enumeration ApplicationDataType.
  • ARXML importer now correctly ignores DataConstr for Structure members of category TYPE_REFERENCE, which Simulink does not support. Previously, the importer tried to read DataConstr for Structure members of category TYPE_REFERENCE, which could generate an unhelpful importer error message.
  • With modular XML file packaging selected, ARXML export no longer generates empty packages for DataConstrs and SystemConstants in the _datatype.arxml file. Previously, export generated empty packages, resulting in a round-trip ARXML mismatch.
  • ARXML importer now correctly creates internal data type names, without double underscores, for ApplicationDataTypes of category VAL_BLK, CURVE, MAPS, etc. Previously, if a data type already had underscore as the last character in its ShortName, the importer added a second underscore, which caused a validation error.
  • ARXML importer now correctly creates an AUTOSAR.Parameter with data type boolean for ApplicationDataTypes of category VAL_BLK. Previously, the importer created an AUTOSAR.Parameter with data type logical, which caused a compilation error.
  • ARXML importer now throws an informative error message when an ApplicationDataType of category CURVE, COM_AXIS, etc., for a lookup table uses an initial value that is scalar rather than nonscalar. Previously, the importer threw an unhelpful error message.
  • ARXML export no longer generates INVALID-VALUEs with invalid or empty CONSTANT-REFERENCEs. Previously, exporting an imported INVALID-VALUE with an empty CONSTANT-REFERENCE could crash Simulink.
  • ARXML export now throws a warning if two common axis lookup tables use the same parameter for table data and different parameters for axis data. The warning informs the user that the COM_AXIS parameter is not shared. Previously, export threw an error.
  • ARXML importer no longer creates unnecessary and unused Simulink data types in the workspace when importing ApplicationDataTypes of category VAL_BLK.
Related Question