【vsomeip】如何让vsomeip在双系统运行起来----(三)

最新推荐文章于 2024-07-08 22:09:55 发布
最新推荐文章于 2024-07-08 22:09:55 发布
阅读量284 收藏 3
点赞数 1
分类专栏： commonAPI 文章标签： linux 信息与通信 c++ ubuntu
版权声明：本文为博主原创文章，遵循 CC 4.0 BY-SA 版权协议，转载请附上原文出处链接和本声明。
本文链接：https://blog.csdn.net/wzc81614/article/details/134411935
版权

文章目录

前言

书接上文【vsomeip】如何让vsomeip在双系统运行起来----(二)，原计划是将这个topic能写完，无奈遇到的坑太多，要把一个一个多的问题以及解决方案 写清楚也太烧脑了。本文将争取完成这个topic的书写，后续将关注于commonAPI的验证。

本文继续先验证vsomeip可以在Host Linux和LXC 里面的Guest Linux之间进行通信。

验证vsomeip自带helloworld例程
创建helloworld的Service和client的配置文件
验证双机情况下vsomeip通信
验证LXC 内外系统的vsomeip通信

一、修改LXC网络设备节点名

ubuntu@will:/tmp/vsomeip/examples/hello_world/build$ ./hello_world_client
... ...
2023-11-13 08:23:18.324669 [info] Network interface "eth0" state changed: up
2023-11-13 08:23:18.325077 [info] Route "default route (0.0.0.0/0) if: eth0 gw: 10.0.3.1" state changed: up

Check the log, I don’t known why keyword “eth0” printed here but LXC default network device name is “lxcbr0”, so I want to try to modify current network device node name from lxcbr0 to eth0.

1. modify LXC_BRIDGE = "eth0"
will@will-OptiPlex-7050:~/work/vsomeip/examples/hello_world$ cat vi /etc/default/lxc-net 
... ...
# If you change the LXC_BRIDGE to something other than lxcbr0, then
# you will also need to update your /etc/lxc/default.conf as well as the
# configuration (/var/lib/lxc/<container>/config) for any containers
# already created using the default config to reflect the new bridge
# name.
# If you have the dnsmasq daemon installed, you'll also have to update
# /etc/dnsmasq.d/lxc and restart the system wide dnsmasq daemon.
LXC_BRIDGE="eth0"

2. modify lxc.net.0.link to eth0.
cat /etc/lxc/default.conf 
lxc.net.0.type = veth
lxc.net.0.link = eth0
lxc.net.0.flags = up
lxc.net.0.hwaddr = 00:16:3e:xx:xx:xx

3.modify lxc.net.0.link to eth0 as well.
will@will-OptiPlex-7050:~/work/vsomeip/examples/hello_world$ sudo cat /var/lib/lxc/will/config
... ...
lxc.net.0.link = eth0

4. after reboot, the modificaiton will take effect.

但是修改之后，对于这个问题的解决没帮助。。。

二、验证双机情况下vsomeip通信

Blocked basic communication issue several days, between HOST linux and GUEST linux. I have to settle for second best, refer to some sample on internet to verify vsomeip on two different physical PC, maybe easier for me.

  1. PC1, Ubuntu 18.04, as vsomeip service side
  2. PC2, Ubuntu 20.04, as vsomeip client side

1. Verify vsomeip on two physical PC1

helloworld-service.json

{
    "unicast":"192.168.168.121", //PC1 ip  add
    "netmask":"255.255.255.0",
    "logging":
    {
        "level":"debug",
        "console":"true"
    },

    "applications":
    [
        {
            "name":"hello_world_service",
            "id":"0x4444"
        },
		{
            "name":"hello_world_client",
            "id":"0x5555"
        }
    ],

    "services":
    [
        {
            "service":"0x1111",
            "instance":"0x2222",
            "unreliable": "30509"
        }
    ],

    "routing":"hello_world_service",
    "service-discovery":
    {
        "enable":"true",
        "multicast":"192.168.168.255",     //Set to gateway. Try to IP add randomly, vsomeip can't work!!!!!!!
        "port":"30490",
        "protocol":"udp",
        "initial_delay_min":"10",
        "initial_delay_max":"100",
        "repetitions_base_delay":"200",
        "repetitions_max":"3",
        "ttl":"3",
        "cyclic_offer_delay":"2000",
        "request_response_delay":"1500"
    }
}

在这里插入图片描述
log at service side:

will@ubuntu:~/work/vsomeip/examples/hello_world/build$ sudo ./hello_world_service
2023-11-14 10:36:20.819646 [info] Using configuration file: "../helloworld-service.json".
2023-11-14 10:36:20.820545 [info] Parsed vsomeip configuration in 0ms
2023-11-14 10:36:20.820698 [info] Configuration module loaded.
2023-11-14 10:36:20.820780 [info] Security disabled!
2023-11-14 10:36:20.821017 [info] Initializing vsomeip (3.4.9.1) application "hello_world_service".
2023-11-14 10:36:20.821440 [info] Instantiating routing manager [Host].
2023-11-14 10:36:20.823177 [info] create_routing_root: Routing root @ /tmp/vsomeip-0
2023-11-14 10:36:20.823997 [info] Service Discovery enabled. Trying to load module.
2023-11-14 10:36:20.827612 [info] Service Discovery module loaded.
2023-11-14 10:36:20.828350 [info] Application(hello_world_service, 4444) is initialized (11, 100).
2023-11-14 10:36:20.828766 [info] Starting vsomeip application "hello_world_service" (4444) using 2 threads I/O nice 255
2023-11-14 10:36:20.830273 [info] Client [4444] routes unicast:192.168.168.121, netmask:255.255.255.0
2023-11-14 10:36:20.830174 [info] main dispatch thread id from application: 4444 (hello_world_service) is: 7f59bb55c700 TID: 26021
2023-11-14 10:36:20.830478 [info] shutdown thread id from application: 4444 (hello_world_service) is: 7f59bad5b700 TID: 26022
2023-11-14 10:36:20.832176 [info] Watchdog is disabled!
2023-11-14 10:36:20.833586 [info] io thread id from application: 4444 (hello_world_service) is: 7f59bf429800 TID: 26018
2023-11-14 10:36:20.833729 [info] io thread id from application: 4444 (hello_world_service) is: 7f59b9d59700 TID: 26024
2023-11-14 10:36:20.834122 [info] create_local_server: Listening @ /tmp/vsomeip-4444
2023-11-14 10:36:20.835427 [info] OFFER(4444): [1111.2222:0.0] (true)
2023-11-14 10:36:20.838927 [info] vSomeIP 3.4.9.1 | (default)
2023-11-14 10:36:20.840206 [info] Network interface "ens38" state changed: up
2023-11-14 10:36:20.841301 [info] Route "default route (0.0.0.0/0) if: ens38 gw: 192.168.168.254" state changed: up
2023-11-14 10:36:20.841966 [info] udp_server_endpoint_impl: SO_RCVBUFFORCE successful.
2023-11-14 10:36:20.842251 [info] udp_server_endpoint_impl: SO_RCVBUF is: 1703936 (1703936) local port:30490
2023-11-14 10:36:20.842482 [debug] Joining to multicast group 192.168.168.255 from 192.168.168.121
2023-11-14 10:36:20.843202 [info] udp_server_endpoint_impl: SO_RCVBUFFORCE successful.
2023-11-14 10:36:20.843489 [info] udp_server_endpoint_impl: SO_RCVBUF is: 1703936 (1703936) local port:30509
2023-11-14 10:36:20.843683 [info] udp_server_endpoint_impl<multicast>: SO_RCVBUFFORCE: successful.
2023-11-14 10:36:20.844417 [info] udp_server_endpoint_impl<multicast>: SO_RCVBUF is: 1703936 (1703936) local port:30490
2023-11-14 10:36:20.843837 [info] SOME/IP routing ready.
2023-11-14 10:36:20.846047 [warning] Route "192.168.168.0/24 if: ens38 gw: n/a" state changed: up
2023-11-14 10:36:20.847393 [warning] Route "192.168.168.255/32 if: ens38 gw: n/a" state changed: up
2023-11-14 10:36:30.846980 [info] vSomeIP 3.4.9.1 | (default)
2023-11-14 10:36:40.857364 [info] vSomeIP 3.4.9.1 | (default)
2023-11-14 10:36:41.974417 [info] STOP OFFER(4444): [1111.2222:0.0] (true)
2023-11-14 10:36:41.976012 [info] Stopping vsomeip application "hello_world_service" (4444).
will@ubuntu:~/work/vsomeip/examples/hello_world/build$ will@ubuntu:

2. Verify vsomeip on two physical PC2

helloworld-client.json

{
    "unicast":"192.168.168.117",  //PC2 IP address
    "netmask":"255.255.255.0",
    "logging":
    {
        "level":"trace",
        "console":"true"
    },

    "applications":
    [
        {
            "name":"hello_world_service",
            "id":"0x4444"
        },
        {
            "name":"hello_world_client",
            "id":"0x5555"
        }
    ],

    "services":
    [
        {
            "service":"0x1111",
            "instance":"0x2222",
            "unreliable":"30509"
        }
    ],

    "routing":"hello_world_client",
    "service-discovery":
    {
        "enable":"true",
        "multicast":"192.168.168.254",  //Set to gateway!!!!
        "port":"30490",
        "protocol":"udp",
        "initial_delay_min":"10",
        "initial_delay_max":"100",
        "repetitions_base_delay":"200",
        "repetitions_max":"3",
        "ttl":"3",
        "cyclic_offer_delay":"2000",
        "request_response_delay":"1500"

    }
}

在这里插入图片描述
log at client side:

will@will-OptiPlex-7050:~/work/vsomeip/examples/hello_world/build$ ./hello_world_client
2023-11-14 10:36:35.642991 [info] Using configuration file: "../helloworld-client.json".
2023-11-14 10:36:35.643753 [info] Parsed vsomeip configuration in 0ms
2023-11-14 10:36:35.643878 [info] Configuration module loaded.
2023-11-14 10:36:35.643962 [info] Security disabled!
2023-11-14 10:36:35.644019 [info] Initializing vsomeip (3.4.9.1) application "hello_world_client".
2023-11-14 10:36:35.644637 [info] Instantiating routing manager [Host].
2023-11-14 10:36:35.645606 [info] create_routing_root: Routing root @ /tmp/vsomeip-0
2023-11-14 10:36:35.646351 [info] Service Discovery enabled. Trying to load module.
2023-11-14 10:36:35.649029 [info] Service Discovery module loaded.
2023-11-14 10:36:35.649597 [info] Application(hello_world_client, 5555) is initialized (11, 100).
2023-11-14 10:36:35.649852 [info] Starting vsomeip application "hello_world_client" (5555) using 2 threads I/O nice 255
2023-11-14 10:36:35.650737 [info] Client [5555] routes unicast:192.168.168.117, netmask:255.255.255.0
2023-11-14 10:36:35.651048 [info] shutdown thread id from application: 5555 (hello_world_client) is: 7f3867521700 TID: 28569
2023-11-14 10:36:35.650975 [info] main dispatch thread id from application: 5555 (hello_world_client) is: 7f3867d22700 TID: 28568
2023-11-14 10:36:35.653783 [info] Watchdog is disabled!
2023-11-14 10:36:35.654696 [info] io thread id from application: 5555 (hello_world_client) is: 7f3868632000 TID: 28566
2023-11-14 10:36:35.654730 [info] io thread id from application: 5555 (hello_world_client) is: 7f386651f700 TID: 28571
2023-11-14 10:36:35.654744 [info] REQUEST(5555): [1111.2222:255.4294967295]
2023-11-14 10:36:35.655790 [info] Avoid trigger SD find-service message for local service/instance/major/minor: 1111/2222/255/4294967295
2023-11-14 10:36:35.656571 [info] create_local_server: Listening @ /tmp/vsomeip-5555
2023-11-14 10:36:35.656991 [info] vSomeIP 3.4.9.1 | (default)
2023-11-14 10:36:35.657906 [info] Network interface "enp0s31f6" state changed: up
2023-11-14 10:36:35.658878 [info] Route "default route (0.0.0.0/0) if: enp0s31f6 gw: 192.168.168.254" state changed: up
2023-11-14 10:36:35.659530 [info] udp_server_endpoint_impl: SO_RCVBUF is: 212992 (1703936) local port:30490
2023-11-14 10:36:35.659852 [debug] Joining to multicast group 192.168.168.254 from 192.168.168.117
2023-11-14 10:36:35.660206 [info] SOME/IP routing ready.
2023-11-14 10:36:35.660807 [warning] Route "192.168.168.0/24 if: enp0s31f6 gw: n/a" state changed: up
2023-11-14 10:36:35.661042 [info] udp_server_endpoint_impl<multicast>: SO_RCVBUF is: 212992 (1703936) local port:30490
2023-11-14 10:36:36.021447 [info] endpoint_manager_impl::create_remote_client: 192.168.168.121:30509 reliable: 0 using local port: 0
2023-11-14 10:36:36.022291 [info] udp_client_endpoint_impl::connect: SO_RCVBUF is: 212992 (1703936) local port:0 remote:192.168.168.121:30509
**Sending: World
Received: Hello World**
2023-11-14 10:36:36.137838 [info] RELEASE(5555): [1111.2222]
2023-11-14 10:36:36.138285 [info] Stopping vsomeip application "hello_world_client" (5555).
will@will-OptiPlex-7050:~/work/vsomeip/examples/hello_world/build$

三、Important discovery in vsomeip

multicast in JSON file is determined by broadcast in ifconfig.!!!

四、验证LXC 内外系统的vsomeip通信

Actually I suspect the issue is caused by the wrong value of multicase, but no any clue found from internet. But I am glad to find the reason, and vsomeip can work between LXC internal and external after modify the multicase to correct one.

  1. HOST linux, LXC external OS, as vsomeip service side
  2. GUEST linux, LXC internal OS, as vsomeip client side
    配置文件修改对比：
    在这里插入图片描述
  3. unicast写入ifconfig里面的inet IP add，而multicast写入ifconfig里面broadcast的IP add。
  4. Client端的IP就写eth0那个就好，而Service端要写LXC bridge的IP信息，也就是default的lxcbr0，现在的eth0（被我前面修改过）。
    log at service side:
will@will-OptiPlex-7050:~/work/vsomeip/examples/hello_world/build$ ./hello_world_service 
2023-11-14 14:33:35.315366 [info] Using configuration file: "../helloworld-service.json".
2023-11-14 14:33:35.317193 [info] Parsed vsomeip configuration in 1ms
2023-11-14 14:33:35.317512 [info] Configuration module loaded.
2023-11-14 14:33:35.317750 [info] Security disabled!
2023-11-14 14:33:35.317927 [info] Initializing vsomeip (3.4.9.1) application "hello_world_service".
2023-11-14 14:33:35.318501 [info] Instantiating routing manager [Host].
2023-11-14 14:33:35.321988 [info] create_routing_root: Routing root @ /tmp/vsomeip-0
2023-11-14 14:33:35.324658 [info] Service Discovery enabled. Trying to load module.
2023-11-14 14:33:35.331264 [info] Service Discovery module loaded.
2023-11-14 14:33:35.332401 [info] Application(hello_world_service, 4444) is initialized (11, 100).
2023-11-14 14:33:35.332844 [info] Starting vsomeip application "hello_world_service" (4444) using 2 threads I/O nice 255
2023-11-14 14:33:35.334890 [info] Client [4444] routes unicast:10.0.3.1, netmask:255.255.255.0
2023-11-14 14:33:35.334977 [info] main dispatch thread id from application: 4444 (hello_world_service) is: 7fb3912f3700 TID: 31055
2023-11-14 14:33:35.335339 [info] shutdown thread id from application: 4444 (hello_world_service) is: 7fb390af2700 TID: 31056
2023-11-14 14:33:35.338993 [info] Watchdog is disabled!
2023-11-14 14:33:35.340629 [info] io thread id from application: 4444 (hello_world_service) is: 7fb392403ec0 TID: 31052
2023-11-14 14:33:35.341134 [info] io thread id from application: 4444 (hello_world_service) is: 7fb38b7fe700 TID: 31058
2023-11-14 14:33:35.343285 [info] create_local_server: Listening @ /tmp/vsomeip-4444
2023-11-14 14:33:35.344244 [info] OFFER(4444): [1111.2222:0.0] (true)
2023-11-14 14:33:35.344512 [info] vSomeIP 3.4.9.1 | (default)
2023-11-14 14:33:35.346158 [info] Network interface "eth0" state changed: up
2023-11-14 14:33:35.347912 [info] Route "10.0.3.0/24 if: eth0 gw: n/a" state changed: up
2023-11-14 14:33:35.349073 [info] udp_server_endpoint_impl: SO_RCVBUF is: 212992 (1703936) local port:30490
2023-11-14 14:33:35.349538 [debug] Joining to multicast group 10.0.3.255 from 10.0.3.1
2023-11-14 14:33:35.350794 [info] udp_server_endpoint_impl: SO_RCVBUF is: 212992 (1703936) local port:30509
2023-11-14 14:33:35.351177 [info] SOME/IP routing ready.
2023-11-14 14:33:35.352157 [info] udp_server_endpoint_impl<multicast>: SO_RCVBUF is: 212992 (1703936) local port:30490
2023-11-14 14:33:35.352698 [warning] Route "10.0.3.255/32 if: eth0 gw: n/a" state changed: up
2023-11-14 14:33:45.348377 [info] vSomeIP 3.4.9.1 | (default)
2023-11-14 14:33:48.426918 [info] STOP OFFER(4444): [1111.2222:0.0] (true)
2023-11-14 14:33:48.428843 [info] Stopping vsomeip application "hello_world_service" (4444).
will@will-OptiPlex-7050:~/work/vsomeip/examples/hello_world/build$

log at client side:

ubuntu@will:/tmp/vsomeip/examples/hello_world/build$ ./hello_world_client 
2023-11-14 06:33:42.321164 [info] Using configuration file: "../helloworld-client.json".
2023-11-14 06:33:42.321709 [info] Parsed vsomeip configuration in 0ms
2023-11-14 06:33:42.321769 [info] Configuration module loaded.
2023-11-14 06:33:42.321876 [info] Security disabled!
2023-11-14 06:33:42.321957 [info] Initializing vsomeip (3.4.9.1) application "hello_world_client".
2023-11-14 06:33:42.322747 [info] Instantiating routing manager [Host].
2023-11-14 06:33:42.323814 [info] create_routing_root: Routing root @ /tmp/vsomeip-0
2023-11-14 06:33:42.324808 [info] Service Discovery enabled. Trying to load module.
2023-11-14 06:33:42.326452 [info] Service Discovery module loaded.
2023-11-14 06:33:42.326745 [info] Application(hello_world_client, 5555) is initialized (11, 100).
2023-11-14 06:33:42.326935 [info] Starting vsomeip application "hello_world_client" (5555) using 2 threads I/O nice 255
2023-11-14 06:33:42.327611 [info] Client [5555] routes unicast:10.0.3.105, netmask:255.255.255.0
2023-11-14 06:33:42.327360 [info] main dispatch thread id from application: 5555 (hello_world_client) is: 7fe5a3a40700 TID: 2438
2023-11-14 06:33:42.327681 [info] shutdown thread id from application: 5555 (hello_world_client) is: 7fe5a323f700 TID: 2439
2023-11-14 06:33:42.329164 [info] Watchdog is disabled!
2023-11-14 06:33:42.329547 [info] REQUEST(5555): [1111.2222:255.4294967295]
2023-11-14 06:33:42.329803 [info] io thread id from application: 5555 (hello_world_client) is: 7fe5a4350000 TID: 2436
2023-11-14 06:33:42.329928 [info] Avoid trigger SD find-service message for local service/instance/major/minor: 1111/2222/255/4294967295
2023-11-14 06:33:42.329916 [info] io thread id from application: 5555 (hello_world_client) is: 7fe5a223d700 TID: 2441
2023-11-14 06:33:42.330474 [info] vSomeIP 3.4.9.1 | (default)
2023-11-14 06:33:42.330685 [info] create_local_server: Listening @ /tmp/vsomeip-5555
2023-11-14 06:33:42.331457 [info] Network interface "eth0" state changed: up
2023-11-14 06:33:42.332254 [info] Route "default route (0.0.0.0/0) if: eth0 gw: 10.0.3.1" state changed: up
2023-11-14 06:33:42.332977 [info] udp_server_endpoint_impl: SO_RCVBUF is: 212992 (1703936) local port:30490
2023-11-14 06:33:42.333297 [debug] Joining to multicast group 10.0.3.255 from 10.0.3.105
2023-11-14 06:33:42.333640 [info] SOME/IP routing ready.
2023-11-14 06:33:42.333884 [warning] Route "10.0.3.0/24 if: eth0 gw: n/a" state changed: up
2023-11-14 06:33:42.333944 [info] udp_server_endpoint_impl<multicast>: SO_RCVBUF is: 212992 (1703936) local port:30490
2023-11-14 06:33:42.334205 [warning] Route "10.0.3.255/32 if: eth0 gw: n/a" state changed: up
2023-11-14 06:33:43.365849 [info] endpoint_manager_impl::create_remote_client: 10.0.3.1:30509 reliable: 0 using local port: 0
2023-11-14 06:33:43.367132 [info] udp_client_endpoint_impl::connect: SO_RCVBUF is: 212992 (1703936) local port:0 remote:10.0.3.1:30509
Sending: World
Received: Hello World
2023-11-14 06:33:43.479656 [info] RELEASE(5555): [1111.2222]
2023-11-14 06:33:43.480653 [info] Stopping vsomeip application "hello_world_client" (5555).
ubuntu@will:/tmp/vsomeip/examples/hello_world/build$

总结

至此，这个topic就完成了。
这个topoic从开工到结束，大概用了5天时间，主要原因

  1. 开始用aliyun作为source list，会发现vsomeip前装lib会出现问题所以光切换Ubunt系统就花了不少时间
  2. LXC console卡住问题，找了很久原因也没解决
  3. vsomeip的一些error信息，以为是bug，但实际不影响
  4. JSON配置文件里面的IP，包含unicast和multicast的IP，不知道如何填写，后来经过摸索确认
wzc81614
关注
  • 1
    点赞
  • 踩
  • 3
    收藏
    觉得还不错? 一键收藏
  • 1
    评论
专栏目录
【vsomeip】如何让vsomeip在双系统运行起来----(一)
wzc81614的博客
11-14 368
验证vsomeip可以在Host Linux和LXC 里面的Guest Linux之间进行通信。验证vsomeip自带helloworld例程创建helloworld的Service和client的配置文件验证双机情况下vsomeip通信验证LXC 内外系统的vsomeip通信vsomeip的学习，只能靠自己在网上搜集一些资料，由于对于配置的说明不够详细，或者说很难解释我的困惑，所以花了很多时间研究和尝试。由于篇幅有限，决定把学习过程一分为二写成两篇文章来分享给大家。
vsomeip3 双机通信文件配置
m0_37132481的博客
06-22 4474
验证环境 vsomeip地址Android运行命令，红色的地方需要和配置文件一样Linux运行命令，红色的地方需要和配置文件一样Linux service配置文件 ，红色的地方需要更改Android client配置文件，红色的地方需要更改，蓝色的地方可不要 ...
vsomeip片内源码分析
liuxunwei1的博客
04-25 1772
vsomeip 是 GENIVI 实现的开源 SOME/IP 库，由 C++ 编写，目前主要实现了 SOME/IP 的通信和服务发现功能，并在此基础上增加了少许的安全机制。如图所示，vsomeip 不仅涵盖了设备之间的 SOME/IP 通信（外部通信），还涵盖了内部进程间通信。两个设备通过communication endpoints（通信端点）进行通信，endpoints 确定传输使用的协议（TCP 或 UDP）及端口号或其他参数。
译：vsomeip 10 分钟阅读
bluebird_shao的专栏
09-18 3398
SOME/IP 是 “SOEoverIP” 的缩写，中文翻译为：基于 IP 的可扩展面向服务中间件。该中间件设计用于典型的汽车用例，并与 AUTOSAR 兼容（至少在有线格式级别上）。公众可访问的规范可从以下站点获取。在本 wiki 中，我们不想进一步探讨另一个中间件规范的原因，但想大致概述一下 SOME/IP 规范及其开源实现 vsomeip 的基本结构，而不要求完整性。
vsomeip简介
xiaoxiaozengz的博客
04-08 7677
本文主要是开源的vsomeip项目的<<vsomeip in 10 minutes >>进行简单的翻译，原文网址：https://github.com/GENIVI/vsomeip/wiki/vsomeip-in-10-minutes 文章目录1.SOME/IP Introduction1.1SOME/IP Short Introduction1.1.1.SOME/IP On-Wire Format1.1.2.SOME/IP ProtocolSOME/IP On-Wire Forma
SOME/IP开源库Vsomeip分析3-hello_world_client分析
热门推荐
w5678912345的专栏
03-21 1万+
前言 前一章我们主要分析了hello_world_service的运行过程进行了简单的分析，这一章我们会对client进行更深层次的分析。 init 这里初始化其实和之前service端类似，也是注册了几个回调函数，其中比service端多注册了一个回调函数就是on_availability_cbk这个函数，这个函数在上一章也提到了，service端在offer server操作成功后，会通知client端，最终就调用到了这个函数。 // Get the vSomeIP runtime
vsomeip双机通信
dukedududu的博客
07-20 643
vsomeip在两台虚拟机上通信
vsomeip环境搭建及helloworld测试例跑通
weixiao的博客
08-07 4149
vsomeip环境搭建及helloworld测试例跑通
vsomeip如何让vsomeip在双系统运行起来-(三)
11-15
vsomeip 配置文件
基于CommonAPI，CommonAPI-SOMEIP，VSomeIP开源代码基础上构建AutoSAR中SOMEIP的Demo
03-20
该压缩包提供的内容可以参考博客：https://blog.csdn.net/qq_30391343/article/details/123568915 主要提供SOMEIP中Demo演示，侧重Method和Event的客户端和服务端代码实现。 提供一个比较综合的典型场景应用。
vsomeip:IP上可扩展的面向服务的MiddlewarE的实现
05-07
用于SOME / IP服务发现的第二个共享库（ libvsomeip3-sd.so ），如果启用了服务发现，则会在运行时加载该库。 Linux的构建说明 依存关系 需要启用C ++ 11的编译器，例如gcc> = 4.8。 vsomeip使用CMake作为构建系统...
AUTOSAR-SWS-ServiceDiscovery-4.2.1\CommonAPICppAMMSeoul\
05-04
vSomeIP是一种在AUTOSAR系统中广泛使用的高效、可靠和可扩展的网络协议，用于ECU之间的服务交互。 vSomeIP（Virtual Scalable Efficient Inter-Processor communication）是SOME/IP（Scalable Service-Oriented ...
VSOMEIP编译包，包含boost，vsomeip源码以及自动编译脚本
10-19
VSOMEIP（Virtual Software-defined Onboard Middleware for Embedded Platforms）是一种开放源码的中间件，专为嵌入式系统设计，特别是在汽车电子领域有着广泛应用。它提供了服务发现、消息路由和服务接口定义等...
入门vsomeip
CharmingSun的博客
03-31 5024
一、前言 SOME/IP是一套可伸缩的基于IP协议的面向服务的中间件的规范，可以在车载以太网上实现RPC功能（Remote Procedure Call，远程过程调用），这样一个ECU可以通过车载以太网调用另一个ECU上提供的函数。vsomip是由宝马开发的开源SOME/IP协议栈。 SOME/IP官网：Scalable service-Oriented MiddlewarE over IP (SOME/IP) vsomeip代码仓库：GitHub - COVESA/vsomeip: An implemen
VSOMEIP中自带helloWoeld代码编译及代码解析
merrycherrytree的博客
10-19 1394
vsomeip自带helloworld代码编译及解析
vsomeip源码梳理 -- Event订阅流程
变
10-09 4729
vsomeip request_event subscribe
【车载以太网】【SOME/IP】(七)调试GENIVI的SOME/IP--vsomeip
专注汽车软件开发、AutoSAR、车载以太网、SOA、EE架构。
01-27 2848
前言： 调试GENIVI的SOME/IP--vsomeip，该代码工程实现了someip的通信和发现服务功能；本调试是hello_world工程；从github上获取，网址https://github.com/GENIVI/vsomeip； 正文： 一、调试步骤： 1. Build whole project at first: ________________________________ cd <root directory of vSomeIP-Lib>$: mkdir b
vssomeip user manual
AgingMoon的博客
12-11 1557
SOME/IP Short Introduction SOME/IP is an abbreviation for "Scalable service-Oriented middlewarE over IP". This middleware was designed for typical automotive use cases and for being compatible with AUTOSAR (at least on the wire-format level). A publicly a
【Linux】进程间通信——匿名管道
最新发布
2201_76024104的博客
07-08 1146
1.：一个进程需要将它的数据发送给另一个进程，比如我们有两个进程，一个负责获取数据，另一个负责处理数据，这时第一个进程就要将获取到的数据交给第二个进程2.：多个进程间共享同样的资源3.：一个进程需要给其他进程发送消息，通知他们发生了某种事件4.：有些事件需要完全控制另一个进程，比如我们在使用gdb调试时，gdb就是一个进程，它控制了我们要调试的进程进程之前是有互相传递信息的需求，但是，一个进程不可能去另一个进程的地址空间中取信息，所以这就要求操作系统去提供一块交换数据的空间来供进程之间使用。
VSomeip协议栈
08-15
通过解析SOME/IP-SD消息，Vsomeip协议栈可以实现服务实例的位置获取、服务实例的运行状态检测以及发布/订阅功能。Vsomeip协议栈的实现代码中使用了异步接收网络数据的方法，通过UDP客户端来接收和发送消息。...

“相关推荐”对你有帮助么？

  • 非常没帮助
  • 没帮助
  • 一般
  • 有帮助
  • 非常有帮助
提交
评论 1
添加红包

请填写红包祝福语或标题

个

红包个数最小为10个

元

红包金额最低5元

当前余额3.43元 前往充值 >
需支付：10.00元
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付元
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明：

1.余额是钱包充值的虚拟货币，按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载，可以购买VIP、付费专栏及课程。

余额充值