Hello I am about to port our code base from SDK 5.1.6 to 5.2.0 using Driveworks 3.5.
The docs say: “The UDP protocol for CAN messages has been simplified […] The mapping values of the UPD pdu ID to CAN ID’s must match the security setup of the aurix firmware compilation.”
It is great that the protocol has been simplified. Unfortunately I am unable to find the documentation on how to compile the aurix firmware with the respective changes necessary.
The best would be to have an explanation e.g. an example of how to port the old EasyCAN configuration to the new aurix firmware. Is there anything like that?
Best regards
Richard
Software Version
DRIVE OS Linux 5.2.0 and DriveWorks 3.5
If that is all I need, that would be great. I would need for example read and write some messages from/to bus C but since only PDU IDs can be set I am a little lost how this is supposed to include CAN message IDs and the bus identifier.
Currently DRIVE-V5.2.0-E3550-AFW-Aurix-With3LSS-StepA-4.02.02.hex is installed as requested on the page you posted. As far as I understood this allows me to communicate the predefined messages 0x106, 0x107, etc.
But this is obviously not very useful as it is.
The next step would be to know how I can recompile my own version of DRIVE-V5.2.0-E3550-AFW-Aurix-With3LSS-StepA-4.02.02.hex to add my own PDU IDs to the PDUR Gateway.
Using and of the shelf firmware is probably not the way to go I assume.
Since the API was changed, I assume a new path on how to access the aurix.can protocoll was set, The documentation is unfortunately very shallow on these details. Please point me into the right direction on how to setup custom PDU IDs for the PDUR Gateway.
Dear @richard5,
how I can recompile my own version of DRIVE-V5.2.0-E3550-AFW-Aurix-With3LSS-StepA-4.02.02.hex to add my own PDU IDs to the PDUR Gateway?
Unfortunately, this is not supported via forum. You may need to have Vector AutoSAR BSW and tools to build for recompilation.