The R2015b Embedded Coder Support Package for AUTOSAR Standard, Version 15.2.3, includes the following bug fixes.
*Bug Fixes:*
* The imported model now correctly configures a Simulink Function block when the imported arxml contains runnable arguments. In arxml files, runnable arguments are described via RUNNABLE-ENTITY-ARGUMENT nodes. Previously, if the runnable description in the arxml file included runnable arguments, the importer incorrectly configured the Simulink Function block.
* Importing inlined array types from an arxml no longer results in model which fails to generate code. In arxml files, an inlined array type is an array type for which element's category is not a TYPE_REFERENCE. Previously, importing inlined array types resulted in invalid models which failed to generate code.
* Importing incomplete lookup table or axis descriptions in an arxml file no longer results in an incorrect model. For example, if the COM-AXIS node is missing description of the SW-BASE-TYPE node, it would be an incomplete axis. With the fix, the importer and the code generator deduces the incomplete information and proceeds successfully.
* Importing NvM_ReadBlock operation from arxml file now correctly configures the corresponding Simulink Function Caller block. Without the fix, in the created model, the block arguments were incorrectly configured.
* Importing LITERAL-PREFIX nodes now correctly creates Simulink enumeration type and literals. Without the fix, the enumeration literals were incorrect in the enumeration type.
* Importing incomplete DATA-TYPE-MAPPING-SET node no longer throws an error if neither the data type set nor the constituent data types are used in the model. Previously, importing incomplete nodes resulted in an importer error.
* Importing a COMPU-METHOD node that represents a linear scaling slope less than or equal to zero now results in an error. Previously, importer created an incorrect model. Linear scaling with slope less than or equal to zero is not supported for models configured for AUTOSAR code generation.
* Importing a SW-BASE-TYPE node that represents an integer type of size 64 no longer throws an error if the type is not used in created model. Previously, the importer threw an error, incorrectly assuming that the integer type is used in the created model. Integer types of size greater than 32 are not supported for models configured for AUTOSAR code generation.
