I noticed in the last versions of AUTOSAR that the standard does not provide the file structure to follow for BSW modules. Before, the *.c, *.h files and the different interactions between them were clearly defined, here is an example from the CAN Driver:
AUTOSAR is restricted to automotive field while CANDBC is not. AUTOSAR toolchains that I've worked with all support the export and import of CAN network design between the file formats ARXML and CANDBC.
I'm new to CAPL programming and trying to create a node which can send an message with Checksum (CRC 8 SAE-J1850) and message counter to my ECU via CAN bus. The polynomial used is P = x^8 + x^4 + x...
In AUTOSAR, SenderReceiverInterface can have multiple data elements as shown below snippet. Is there any advantage or implementation difference when multiple data elements are used in a single software port compared to multiple software ports and each having single data elemment in the respective SenderReceiverInterface?
How a concrete AUTOSAR project gets tested depends type of product being developed and what your AUTOSAR toolchain and hardware stack providers support. If I was you, I would try to draw a detailed "V" model of the project.
But my understanding from Autosar documents was that Manifest is supposed to be an arxml file. So does Execution Manager in the platform need this .json file to parse ? How are these .json files created and how does it fit into the Adaptive Autosar platform. And what exact information is there inside these .json and .arxml files?
I am trying to delete diagnostic information but I am strugling to find the configuration in Tresos which would enable ClearDTC interface. What would be the right way to clear all DTC's internally ...
I have been reading the autosar documentation to better understand the autosar architecture. So, in the implementation of autosar classic, I have doubts regarding the construction of the code, as I am not able to understand the clear difference between Port Driver and Dio Driver.
AUTOSAR RTE to COM Data Transfer supports only UINT8_N type of Array ISignal. Software Components does support ARRAY type of Port Interfaces with UINT32/UINT16 Data type of Array Element.
