20240601在飞凌的OK3588-C开发板上跑IPC的SDK确认eth0

2024-06-01 21:36

本文主要是介绍20240601在飞凌的OK3588-C开发板上跑IPC的SDK确认eth0,希望对大家解决编程问题提供一定的参考价值,需要的开发者们随着小编来一起学习吧!

20240601在飞凌的OK3588-C开发板上跑IPC的SDK确认eth0
2024/6/1 14:04


结论:IPC因为需要推流,默认配置了DHCP,插网线可以自动获取IP地址:192.168.3.142
可以PING通局域网服务器:192.168.3.85和百度。
Buildroot默认只能ping通局域网段内的IP地址。


rootroot@rootroot-ThinkBook-16-G5-IRH:~/RK3588_IPC_SDK$ ./build.sh lunch
Which would you like? [0]: 3
rootroot@rootroot-ThinkBook-16-G5-IRH:~/RK3588_IPC_SDK$ ./build.sh 


需要确认IPC方案的功能点(单PMIC EVB7的方案)
2024/5/27 16:09

1、DEBUG口       1.5Mbps N 8 1
ADB能用

2、USB2.0    IPC没有lsusb
3、USB3.00    IPC没有lsusb

????4、HDMI IN    没有HDMI IN 

????5、HDMI OUT    2024/5/27 15:08 IPC方案默认没有显示,修改/打开很复杂

6、MIPI摄像头1路 IPC方案肯定可以的!默认接4个IMX464   2024/5/27 14:59  OV5645+OV13850 取YUV图片,OV13855待确认

????7、TF卡    没有fdisk,busybox里面也可以

8、RJ45以太网   有ping ifconfig 无iperf


详细LOG:
#
#
#
# ifconfig
eth0      Link encap:Ethernet  HWaddr 82:DA:46:43:8E:B3
          inet addr:192.168.3.142  Bcast:192.168.3.255  Mask:255.255.255.0
          inet6 addr: fe80::80da:46ff:fe43:8eb3/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:368 errors:0 dropped:0 overruns:0 frame:0
          TX packets:12 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:56586 (55.2 KiB)  TX bytes:1480 (1.4 KiB)
          Interrupt:92

lo        Link encap:Local Loopback
          inet addr:127.0.0.1  Mask:255.0.0.0
          inet6 addr: ::1/128 Scope:Host
          UP LOOPBACK RUNNING  MTU:65536  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)

#
#
# ping 192.168.3.85
PING 192.168.3.85 (192.168.3.85): 56 data bytes
64 bytes from 192.168.3.85: seq=0 ttl=64 time=0.566 ms

64 bytes from 192.168.3.85: seq=1 ttl=64 time=0.294 ms
64 bytes from 192.168.3.85: seq=2 ttl=64 time=0.291 ms
64 bytes from 192.168.3.85: seq=3 ttl=64 time=0.290 ms
^C
--- 192.168.3.85 ping statistics ---
4 packets transmitted, 4 packets received, 0% packet loss
round-trip min/avg/max = 0.290/0.360/0.566 ms
#
#
# ping www.baidu.com
PING www.baidu.com (183.2.172.42): 56 data bytes
64 bytes from 183.2.172.42: seq=0 ttl=54 time=6.698 ms

64 bytes from 183.2.172.42: seq=1 ttl=54 time=6.781 ms
64 bytes from 183.2.172.42: seq=2 ttl=54 time=6.784 ms
64 bytes from 183.2.172.42: seq=3 ttl=54 time=6.786 ms
64 bytes from 183.2.172.42: seq=4 ttl=54 time=6.765 ms
64 bytes from 183.2.172.42: seq=5 ttl=54 time=6.742 ms
64 bytes from 183.2.172.42: seq=6 ttl=54 time=6.668 ms
64 bytes from 183.2.172.42: seq=7 ttl=54 time=6.745 ms
64 bytes from 183.2.172.42: seq=8 ttl=54 time=6.729 ms
64 bytes from 183.2.172.42: seq=9 ttl=54 time=6.760 ms
64 bytes from 183.2.172.42: seq=10 ttl=54 time=6.882 ms
64 bytes from 183.2.172.42: seq=11 ttl=54 time=6.395 ms
64 bytes from 183.2.172.42: seq=12 ttl=54 time=6.876 ms
64 bytes from 183.2.172.42: seq=13 ttl=54 time=6.968 ms
64 bytes from 183.2.172.42: seq=14 ttl=54 time=6.496 ms
64 bytes from 183.2.172.42: seq=15 ttl=54 time=6.734 ms
^C
--- www.baidu.com ping statistics ---
16 packets transmitted, 16 packets received, 0% packet loss
round-trip min/avg/max = 6.395/6.738/6.968 ms
#
#
# lsusb
/bin/sh: lsusb: not found
#
# busybox lsusb
lsusb: applet not found
#
#
# fdisk
/bin/sh: fdisk: not found
#
# busybox fdisk
fdisk: applet not found
#
# iperf
/bin/sh: iperf: not found
#
# busybox iperf
iperf: applet not found
#

#


Microsoft Windows [版本 10.0.22621.3296]
(c) Microsoft Corporation。保留所有权利。

C:\Users\QQ>adb shell
#
# v4l2-ctl --list-devices
rkisp-statistics (platform: rkisp):
        /dev/video51
        /dev/video52
        /dev/video60
        /dev/video61
        /dev/video69
        /dev/video70
        /dev/video78
        /dev/video79

rkisp_mainpath (platform:rkisp0-vir0):
        /dev/video44
        /dev/video45
        /dev/video46
        /dev/video47
        /dev/video48
        /dev/video49
        /dev/video50

rkisp_mainpath (platform:rkisp0-vir1):
        /dev/video53
        /dev/video54
        /dev/video55
        /dev/video56
        /dev/video57
        /dev/video58
        /dev/video59

rkisp_mainpath (platform:rkisp1-vir0):
        /dev/video62
        /dev/video63
        /dev/video64
        /dev/video65
        /dev/video66
        /dev/video67
        /dev/video68

rkisp_mainpath (platform:rkisp1-vir1):
        /dev/video71
        /dev/video72
        /dev/video73
        /dev/video74
        /dev/video75
        /dev/video76
        /dev/video77

Failed to open /dev/video0: No such device
#


Xshell 7 (Build 0157)
Copyright (c) 2020 NetSarang Computer, Inc. All rights reserved.

Type `help' to learn how to use Xshell prompt.
[C:\~]$ 

Connecting to 192.168.3.85:22...
Connection established.
To escape to local shell, press 'Ctrl+Alt+]'.

Welcome to Ubuntu 20.04.6 LTS (GNU/Linux 5.15.0-107-generic x86_64)

 * Documentation:  https://help.ubuntu.com
 * Management:     https://landscape.canonical.com
 * Support:        https://ubuntu.com/advantage

Expanded Security Maintenance for Applications is not enabled.

27 updates can be applied immediately.
To see these additional updates run: apt list --upgradable

20 additional security updates can be applied with ESM Apps.
Learn more about enabling ESM Apps service at https://ubuntu.com/esm

New release '22.04.3 LTS' available.
Run 'do-release-upgrade' to upgrade to it.

Your Hardware Enablement Stack (HWE) is supported until April 2025.
Last login: Sat Jun  1 11:39:43 2024 from 192.168.3.97
viewpro@viewpro-ThinkBook-16-G5-IRH:~$ 
viewpro@viewpro-ThinkBook-16-G5-IRH:~$ 
viewpro@viewpro-ThinkBook-16-G5-IRH:~$ ping www.192.168.3.142
^[[D^[[D^C
viewpro@viewpro-ThinkBook-16-G5-IRH:~$ ping 192.168.3.142
PING 192.168.3.142 (192.168.3.142) 56(84) bytes of data.
64 bytes from 192.168.3.142: icmp_seq=1 ttl=64 time=0.247 ms
64 bytes from 192.168.3.142: icmp_seq=2 ttl=64 time=0.290 ms
c^C
--- 192.168.3.142 ping statistics ---
2 packets transmitted, 2 received, 0% packet loss, time 1002ms
rtt min/avg/max/mdev = 0.247/0.268/0.290/0.021 ms
viewpro@viewpro-ThinkBook-16-G5-IRH:~$ 
viewpro@viewpro-ThinkBook-16-G5-IRH:~$ 
viewpro@viewpro-ThinkBook-16-G5-IRH:~$ 
viewpro@viewpro-ThinkBook-16-G5-IRH:~$ 
viewpro@viewpro-ThinkBook-16-G5-IRH:~$ ping 192.168.3.142
PING 192.168.3.142 (192.168.3.142) 56(84) bytes of data.
64 bytes from 192.168.3.142: icmp_seq=1 ttl=64 time=0.217 ms

64 bytes from 192.168.3.142: icmp_seq=2 ttl=64 time=0.230 ms
64 bytes from 192.168.3.142: icmp_seq=3 ttl=64 time=0.301 ms
64 bytes from 192.168.3.142: icmp_seq=4 ttl=64 time=0.232 ms
64 bytes from 192.168.3.142: icmp_seq=5 ttl=64 time=0.283 ms
64 bytes from 192.168.3.142: icmp_seq=6 ttl=64 time=0.230 ms
64 bytes from 192.168.3.142: icmp_seq=7 ttl=64 time=0.294 ms
64 bytes from 192.168.3.142: icmp_seq=8 ttl=64 time=0.294 ms
64 bytes from 192.168.3.142: icmp_seq=9 ttl=64 time=0.229 ms
64 bytes from 192.168.3.142: icmp_seq=10 ttl=64 time=0.230 ms
64 bytes from 192.168.3.142: icmp_seq=11 ttl=64 time=0.226 ms
64 bytes from 192.168.3.142: icmp_seq=12 ttl=64 time=0.239 ms
64 bytes from 192.168.3.142: icmp_seq=13 ttl=64 time=0.222 ms
64 bytes from 192.168.3.142: icmp_seq=14 ttl=64 time=0.228 ms
64 bytes from 192.168.3.142: icmp_seq=15 ttl=64 time=0.289 ms
64 bytes from 192.168.3.142: icmp_seq=16 ttl=64 time=0.279 ms
64 bytes from 192.168.3.142: icmp_seq=17 ttl=64 time=0.291 ms
64 bytes from 192.168.3.142: icmp_seq=18 ttl=64 time=0.222 ms
64 bytes from 192.168.3.142: icmp_seq=19 ttl=64 time=0.300 ms
64 bytes from 192.168.3.142: icmp_seq=20 ttl=64 time=0.216 ms
64 bytes from 192.168.3.142: icmp_seq=21 ttl=64 time=0.283 ms
64 bytes from 192.168.3.142: icmp_seq=22 ttl=64 time=0.280 ms
64 bytes from 192.168.3.142: icmp_seq=23 ttl=64 time=0.281 ms
64 bytes from 192.168.3.142: icmp_seq=24 ttl=64 time=0.286 ms
64 bytes from 192.168.3.142: icmp_seq=25 ttl=64 time=0.245 ms
64 bytes from 192.168.3.142: icmp_seq=26 ttl=64 time=0.238 ms
64 bytes from 192.168.3.142: icmp_seq=27 ttl=64 time=0.236 ms
64 bytes from 192.168.3.142: icmp_seq=28 ttl=64 time=0.239 ms
64 bytes from 192.168.3.142: icmp_seq=29 ttl=64 time=0.239 ms
64 bytes from 192.168.3.142: icmp_seq=30 ttl=64 time=0.239 ms
64 bytes from 192.168.3.142: icmp_seq=31 ttl=64 time=0.249 ms
64 bytes from 192.168.3.142: icmp_seq=32 ttl=64 time=0.280 ms
64 bytes from 192.168.3.142: icmp_seq=33 ttl=64 time=0.236 ms
64 bytes from 192.168.3.142: icmp_seq=34 ttl=64 time=0.291 ms
64 bytes from 192.168.3.142: icmp_seq=35 ttl=64 time=0.279 ms
64 bytes from 192.168.3.142: icmp_seq=36 ttl=64 time=0.276 ms
64 bytes from 192.168.3.142: icmp_seq=37 ttl=64 time=0.276 ms
64 bytes from 192.168.3.142: icmp_seq=38 ttl=64 time=0.231 ms
64 bytes from 192.168.3.142: icmp_seq=39 ttl=64 time=0.289 ms
64 bytes from 192.168.3.142: icmp_seq=40 ttl=64 time=0.303 ms
64 bytes from 192.168.3.142: icmp_seq=41 ttl=64 time=0.290 ms
64 bytes from 192.168.3.142: icmp_seq=42 ttl=64 time=0.237 ms
64 bytes from 192.168.3.142: icmp_seq=43 ttl=64 time=0.225 ms
64 bytes from 192.168.3.142: icmp_seq=44 ttl=64 time=0.347 ms
64 bytes from 192.168.3.142: icmp_seq=45 ttl=64 time=0.260 ms
64 bytes from 192.168.3.142: icmp_seq=46 ttl=64 time=0.230 ms
64 bytes from 192.168.3.142: icmp_seq=47 ttl=64 time=0.223 ms
^C
--- 192.168.3.142 ping statistics ---
47 packets transmitted, 47 received, 0% packet loss, time 47082ms
rtt min/avg/max/mdev = 0.216/0.258/0.347/0.031 ms
viewpro@viewpro-ThinkBook-16-G5-IRH:~$ 

这篇关于20240601在飞凌的OK3588-C开发板上跑IPC的SDK确认eth0的文章就介绍到这儿,希望我们推荐的文章对编程师们有所帮助!



http://www.chinasem.cn/article/1022173

相关文章

消除安卓SDK更新时的“https://dl-ssl.google.com refused”异常的方法

消除安卓SDK更新时的“https://dl-ssl.google.com refused”异常的方法   消除安卓SDK更新时的“https://dl-ssl.google.com refused”异常的方法 [转载]原地址:http://blog.csdn.net/x605940745/article/details/17911115 消除SDK更新时的“

开发板NFS挂载文件目录

文章目录 序NFS1. 安装 NFS 服务器和客户端在服务器上(NFS 服务器端)在客户端上(NFS 客户端) 2. 配置 NFS 服务器创建共享目录编辑 `/etc/exports` 文件启动 NFS 服务 3. 在客户端挂载 NFS 共享创建挂载点挂载 NFS 共享验证挂载 4. 设置开机自动挂载5. 解决权限问题 序 本节主要实现虚拟机(服务器)与开发板(客户端)通过N

安卓开发板_联发科MTK开发评估套件串口调试

串口调试 如果正在进行lk(little kernel ) 或内核开发,USB 串口适配器( USB 转串口 TTL 适配器的简称)对于检查系统启动日志非常有用,特别是在没有图形桌面显示的情况下。 1.选购适配器 常用的许多 USB 转串口的适配器,按芯片来分,有以下几种: CH340PL2303CP2104FT232 一般来说,采用 CH340 芯片的适配器,性能比较稳定,价

理解C++全局对象析构顺序与 IPC 资源管理:避免 coredump

文章目录 0. 概述1. 问题背景2. 问题分析3. 解决方案:手动释放资源4. 深入剖析:为什么手动调用 `reset()` 有效?5. 延伸思考:如何避免全局对象带来的问题?6. 总结 0. 概述 在编写 C++ 程序时,使用全局或静态对象有时可能会导致不可预期的崩溃(如 coredump)。这类崩溃通常源于对象的析构顺序、资源的管理方式,以及底层资源(如 IPC 通道或共

企业网银登录提示请确认您已插入工商银行U盾证书的解决方法

昨天受人之托帮小企业财务解决上网银的问题 因为不是专业做这个的,所以只能安装“常识”行事,但结果实在是令人意想不到。 排错的步骤: 同一台电脑上尝试不同浏览器,发现360浏览器的接受度相当普遍;给U盾换不同的连接线;在不同的电脑上安装银行的插件,再重复上面的步骤1和步骤2;最终的结果,在一台电脑上可以走到下一步,但时好时坏,无法解决问题;到知乎上找答案,在一篇说明里有提到定制的qq浏览器,最后

android sdk 设置

android sdk 设置 http://www.androiddevtools.cn/

序列号SYN+确认号ACK

处于对于wireshark中的SYN和ACK如何计算出来的疑惑 找的这篇译文! From:  http://blog.csdn.net/a19881029/article/details/38091243 原文见:http://packetlife.net/blog/2010/jun/7/understanding-tcp-sequence-acknowledgment-numbers/

Linux IPC 1 之 概述

Linux IPC 1 之 概述 Linux IPC 1 之 概述 背景进程的含义IPC的含义三个名词IPC的6种方式 背景: 以前学习研究的Linux进程间通信,经常不用都要忘了,而且发现写的博客也有些不够完整,所以干脆推倒重来,温故知新而已:) 进程的含义 进程是操作系统的概念,每当我们执行一个程序时,对于操作系统来讲就创建了一个进程,在这个过程中,伴随着

unable to access android sdk add-on list解决办法

mac环境,由于不小心删掉了sdk文件夹的内容,拷贝别人的文件内容过来后,发现sdkmanager不见了。 慌乱中重装了Android Studio。 打开app后发现如下提示:unable to access android sdk add-on list 解决办法: 在 Android Studio 安装目录 bin/idea.properties 文件最后追加一句 disabl

兔子--SDK,ADT,AVD,IDE,ADB

a:SDK(Software Development Kit):开发android应用所需要的开发工具的集合,包括库文件及工具。 b:ADT(Android Developer Tools):在Eclipse下开发工具的升级下载工具。adt只是一个eclipse的插件,里面可以设置 sdk路径. c:IDE:集成开发环境。IDE通常包括编程语言编辑器、自动建立工具、通常还包括调试