FAQ: How EHANDBOOK supports AUTOSAR (Classic)
Answer
EHANDBOOK supports AUTOSAR (Classic) in both EHANDBOOK Container-Build and EHANDBOOK-NAVIGATOR.
-
EHB-CB perspective: EHANDBOOK Container-Build supports processing AUTOSAR (Classic) `.arxml\` input. It derives the required AUTOSAR information for software components (instances), their ports, interface elements (for example signal- or service-related elements depending on interface type), and their connections, and stores this information in EHANDBOOK Container files.
When an AUTOSAR component type has multiple prototypes, EHANDBOOK-CB creates a corresponding Function Component Unit (FC Unit) for each prototype. Each prototype is represented as a separate entry in the Table of Contents (TOC), while using the same documentation as the corresponding component type.
For example, if an AUTOSAR component type has two prototypes, Prototype1 and Prototype2, the TOC contains separate entries for Prototype1 and Prototype2. Both prototype entries use the documentation of the component type, while model references are resolved using the respective prototype-specific paths. For additional info with demo example see ASAM-based EHB-CB with AUTOSAR Classic and ASCET demo.
For model references associated with these prototypes, the prototype-specific path is used for resolving the referenced model element. As a result, figure titles may contain the fully qualified model path. This is current behavior.
-
EHB-NAV perspective: EHANDBOOK-NAVIGATOR uses the AUTOSAR information stored in EHANDBOOK Containers to visualize software components in overview diagrams, including ports and their interface elements as well as connections between software components.
Interface elements can be shown or hidden in the Function Overview using the corresponding toolbar actions.
For additional information, see:
Support
Feel free to contact the ETAS Support if you have any questions or can’t find the information you need.