Clear Filters
Clear Filters

AUTOSAR Blocket SOME/IP Binding

36 views (last 30 days)
dahyun ko
dahyun ko on 5 Mar 2024
Answered: SACHIN KHANDELWAL on 15 Apr 2024
I created a simple model including the Event send and Event receiver Blocks from the AUTOSAR Blockset. Configure AUTOSAR Adaptive Software was performed through the Code Mappings editor and AUTOSAR Dictionary and code was generated using AUTOSAR Coder. (I will add a photo of the modeling. It is currently a simple model for communication and the LKAS algorithm will be added in the future)
My Matlab versiond is R2023b, and schema version is R19-03 (I also tried R20 and 21 versions). However, when the code is generated, there is a problem that ARXML is bound to DDS rather than SOME/IP. I understand that when generating code in Matlab, ARXML is read and CPP code is generated. However, ARXML does not include SOME/IP content and all interfaces are defined as DDS. Among the generated codes, files in the stub/aragen folder also have an interface defined using the eprosima_dds library.
So, is it not possible to develop SOME/IP ASW in Matlab? Or, I would like to ask if there is a configuration I set incorrectly.
  4 Comments
Pratheek
Pratheek on 21 Mar 2024
Starting in R2024a, the generated code for AUTOSAR Adaptive models supports SOME/IP binding for ara::com communication between adaptive applications. This feature is supported with the AUTOSAR Adaptive Linux Executable toolchain. The generated ServiceInstanceManifest.arxml file contains SOME/IP artifacts. For more information, see Additional XML Options.
Thanks
dahyun ko
dahyun ko on 22 Mar 2024
Finally, I successed someip binding!!
But What's VSomeIPConfig.json file?
I can get this file when I generated code binding someip.
Is it involved vsomeip library?

Sign in to comment.

Answers (1)

SACHIN KHANDELWAL
SACHIN KHANDELWAL on 15 Apr 2024
When the model is set up for SOME/IP network binding, a configuration file named VSOMEIPConfig.json is created during the code generation process.This file will be used by the executable when launched using Linux Runtime Manager.
Here’s a breakdown of the information contained in this file:
  1. "unicast" - This is the IP address of the device where the executable is running.
  2. "service" and "instance": Both of these fields are filled with the Instance ID, a unique identifier that is specified in the AUTOSAR dictionary.
  3. "unreliable" - This refers to the UDP port used by the service.
  4. "name" - Name of the application which is populated with the name of the executable.
  5. "id" - Unique ID of the application which is populated with the Application ID.
I hope this information helps answer your query.
Thanks.

Products


Release

R2023b

Community Treasure Hunt

Find the treasures in MATLAB Central and discover how the community can help you!

Start Hunting!