0
  • 聊天消息
  • 系统消息
  • 评论与回复
登录后你可以
  • 下载海量资料
  • 学习在线课程
  • 观看技术视频
  • 写文章/发帖/加入社区
会员中心
创作中心

完善资料让更多小伙伴认识你,还能领取20积分哦,立即完善>

3天内不再提示

硬核上车!RK3576基于Ubuntu部署ROS机器人系统详细攻略(下)

触觉智能 2025-07-11 18:34 次阅读
加入交流群
微信小助手二维码

扫码添加小助手

加入工程师交流群

本文介绍Ubuntu部署ROS常见编译报错的解决方法。对编译步骤感兴趣可以查看上篇文章https://www.elecfans.com/d/6788562.html

文章适用于瑞芯微旗下RK3562、RK3566、RK3568、RK3576、RK3588等Arm64位芯片平台,各型号触觉智能均配套核心板及开发板,实现了百分百全国产。

常见编译报错解决方法

编译主机内存不足
除了增加编译主机内存配置外,建议将可以开启交换空间,例如zram

sudo -i su # modprobe zram # echo 12G > /sys/block/zram0/disksize # echo 6G > /sys/block/zram0/mem_limit # mkswap /dev/zram0 # swapon /dev/zram0 # free -h total used free shared buff/cache available Mem: 14Gi 3.9Gi 5.5Gi 27Mi 5.4Gi 10Gi Swap: 11Gi 2.7Gi 9.3Gi


执行时报`GLIBCXX_3.4.30' not found 错误
在主板端执行以上报错,是因为RK Linux SDK版本较多, 工具链版本一直在更新,因此需要使用Linux SDK编译Rootfs的交叉工具来编译ROS2

root@rk3562-buildroot:/opt/ros-foxy# ros2 run demo_nodes_cpp talker /opt/ros-foxy/lib/demo_nodes_cpp/talker: /lib/libstdc++.so.6: version `GLIBCXX_3.4.30' not found (required by /opt/ros-foxy/lib/librclcpp.so) /opt/ros-foxy/lib/demo_nodes_cpp/talker: /lib/libstdc++.so.6: version `GLIBCXX_3.4.30' not found (required by /opt/ros-foxy/lib/libspdlog.so.1)

编译结果中出现x86_64动态库

ls /opt/ros/lib/python3.10/site-packages/rclpy/_rclpy_pybind11.cpython-310- x86_64-linux-gnu.so


pybind11在交叉编译的环境中, 确实是会有一些已知的问题。找到的python是HOST端的可执行文件,因此一系列参数也是根据HOST端生成,如:

PYTHON_MODULE_EXTENSION:INTERNAL=.cpython-310-x86_64-linux-gnu.so


在pybind11/tools/FindPythonLibsNew.cmake较新的代码中,建议若是Cross Compling,可在外部手动添加python的参数:

1. 修改src/ros2/pybind11_vendor中pybind11升级到v2.10.2。

2. 并在pybind11_verdor/CMakeLists.txt中设置以下2个参数,

指定具体的 PYTHON_MODULE_EXTENSION:

list(APPEND extra_cmake_args "-DPYBIND11_PYTHONLIBS_OVERWRITE=OFF") list(APPEND extra_cmake_args "-DPYTHON_MODULE_EXTENSION=.cpython-310- aarch64-linux-gnu.so")


3. 在cross-compile.mixin中,也声明:

- "-DPYBIND11_PYTHONLIBS_OVERWRITE=OFF" - "-DPYTHON_MODULE_EXTENSION=.cpython-310-aarch64-linux-gnu.so"


上述修改后, 仍然发现rclpy在编译时,其CMakeCache.txt文件中得到的

PYTHON_MODULE_EXTENSION仍指向"x86_64",但第二次再编译时,会被修改成预期的aarch64。有以下原因:

1. 在pybind11/tools/pybind11NewTools.cmake中, 若未设置过

PYBIND11_PYTHON_EXECUTABLE_LAST、或它值被修改了,会直接清空PYTHON_MODULE_EXTENSION。

76 if(NOT ${_Python}_EXECUTABLE STREQUAL PYBIND11_PYTHON_EXECUTABLE_LAST) 77 # Detect changes to the Python version/binary in subsequent CMake runs, and refresh config if needed 78 unset(PYTHON_IS_DEBUG CACHE) 79 unset(PYTHON_MODULE_EXTENSION CACHE) 80 set(PYBIND11_PYTHON_EXECUTABLE_LAST 81 "${${_Python}_EXECUTABLE}" 82 CACHE INTERNAL "Python executable during the last CMake run") 83 endif()


2. 在pybind11 issue #236 也有类似的现象。

3. 修改pybind11解决: 若是PYBIND11_PYTHONLIBS_OVERWRITE="OFF",则不重设上述参数:

commit f7f1f2a927dd785d109833e411325de4c248719f (HEAD -> v2.10.2-fix) Author: cross-build for rk-linux-sdk Date: Fri Sep 22 08:24:58 2023 +0000 Do not override the PYTHON_MODULE_EXTENSION if cross building As suggested in tools/FindPythonLibsNew.cmake, PYBIND11_PYTHONLIBS_OVERWRITE is a flag to indicate that we set python variables manually when cross building. In this case, do not override variables if PYBIND11_PYTHON_EXECUTABLE_LAST changed or is empty. diff --git a/tools/pybind11NewTools.cmake b/tools/pybind11NewTools.cmake index 7d7424a7..91980dad 100644 --- a/tools/pybind11NewTools.cmake +++ b/tools/pybind11NewTools.cmake @@ -73,7 +73,7 @@ if(NOT DEFINED ${_Python}_EXECUTABLE) endif() -if(NOT ${_Python}_EXECUTABLE STREQUAL PYBIND11_PYTHON_EXECUTABLE_LAST) 7.4 google_benchmark工程缺少limits头文件 编译foxy时会报如下错误, 原因是缺少头文件: 该修改在ROS2较新版本中已经修复; 补丁包也有包含 7.5 Linux SDK工具链中定义_FORTIFY_SOURCE +if(NOT ${_Python}_EXECUTABLE STREQUAL PYBIND11_PYTHON_EXECUTABLE_LAST AND NOT PYBIND11_PYTHONLIBS_OVERWRITE STREQUAL "OFF") # Detect changes to the Python version/binary in subsequent CMake runs, and refresh config if needed unset(PYTHON_IS_DEBUG CACHE) unset(PYTH


google_benchmark工程缺少limits头文件
编译foxy时会报如下错误:

In file included from /buildroot/build/ros/google_benchmark_vendor/benchmark- 1.5.2-prefix/src/benchmark-1.5.2/src/benchmark_register.cc:15: /buildroot/build/ros/google_benchmark_vendor/benchmark-1.5.2- prefix/src/benchmark-1.5.2/src/benchmark_register.h: In function ‘typename std::vector::iterator benchmark::internal::AddPowers(std::vector*, T, T, int)’: /buildroot/build/ros/google_benchmark_vendor/benchmark-1.5.2- prefix/src/benchmark-1.5.2/src/benchmark_register.h:22:30: error: ‘numeric_limits’ is not a member of ‘std’ 22 | static const T kmax = std::numeric_limits::max(); | ^~~~~~~~~~~~~~


原因是缺少头文件:

/buildroot/build/ros/google_benchmark_vendor/benchmark-1.5.2- prefix/src/benchmark-1.5.2/src/benchmark_register.h #include


Linux SDK工具链中定义_FORTIFY_SOURCE

--- stderr: mimick_vendor Cloning into 'mimick-f171450b5ebaa3d2538c762a059dfc6ab7a01039'... fatal: unable to access 'https://github.com/ros2/Mimick.git/': gnutls_handshake() failed: Error in the pull function. Cloning into 'mimick-f171450b5ebaa3d2538c762a059dfc6ab7a01039'... HEAD is now at f171450 Add armv7l as a 32-bit ARM architecture. (#16) In file included from /opt/aarch64-buildroot-linux-gnu_sdk-buildroot/aarch64- buildroot-linux-gnu/sysroot/usr/include/errno.h:25, from /buildroot/build/ros/mimick_vendor/mimickf171450b5ebaa3d2538c762a059dfc6ab7a01039-prefix/src/mimickf171450b5ebaa3d2538c762a059dfc6ab7a01039/include/mimick/mock.h:27, from /buildroot/build/ros/mimick_vendor/mimickf171450b5ebaa3d2538c762a059dfc6ab7a01039-prefix/src/mimickf171450b5ebaa3d2538c762a059dfc6ab7a01039/include/mimick/mimick.h:401, from /buildroot/build/ros/mimick_vendor/mimickf171450b5ebaa3d2538c762a059dfc6ab7a01039-prefix/src/mimickf171450b5ebaa3d2538c762a059dfc6ab7a01039/sample/strdup/test.c:1: 报错仅在指定了-DCMAKE_TOOLCHAIN_FILE="/opt/aarch64-buildroot-linux-gnu_sdkbuildroot/share/buildroot/toolchainfile.cmake"交叉工具链,且该cmake定义了_FORTIFY_SOURCE 可不指定CMAKE_TOOLCHAIN_FILE,或删除_FORTIFY_SOURCE 7.6 CMake找不到exlibConfig.cmake 编译ament_cmake_vendor_package报找不到exlib,但实际该exlib库都被正确指定了。 /opt/aarch64-buildroot-linux-gnu_sdk-buildroot/aarch64-buildroot-linuxgnu/sysroot/usr/include/features.h:412:4: error: #warning _FORTIFY_SOURCE requires compiling with optimization (-O) [-Werror=cpp] 412 | # warning _FORTIFY_SOURCE requires compiling with optimization (-O) | ^~~~~~~ cc1: all warnings being treated as errors make[5]: *** [sample/strdup/CMakeFiles/strdup_test.dir/build.make:63: sample/strdup/CMakeFiles/strdup_test.dir/test.c.o] Error 1 make[4]: *** [CMakeFiles/Makefile2:302: sample/strdup/CMakeFiles/strdup_test.dir/all] Error 2 make[4]: *** Waiting for unfinished jobs.... In file included from /opt/aarch64-buildroot-linux-gnu_sdk-buildroot/aarch64- buildroot-linux-gnu/sysroot/usr/include/errno.h:25, from /buildroot/build/ros/mimick_vendor/mimickf171450b5ebaa3d2538c762a059dfc6ab7a01039-prefix/src/mimickf171450b5ebaa3d2538c762a059dfc6ab7a01039/include/mimick/mock.h:27, from /buildroot/build/ros/mimick_vendor/mimickf171450b5ebaa3d2538c762a059dfc6ab7a01039-prefix/src/mimickf171450b5ebaa3d2538c762a059dfc6ab7a01039/include/mimick/mimick.h:401, from /buildroot/build/ros/mimick_vendor/mimickf171450b5ebaa3d2538c762a059dfc6ab7a01039-prefix/src/mimickf171450b5ebaa3d2538c762a059dfc6ab7a01039/test/test.c:1: /opt/aarch64-buildroot-linux-gnu_sdk-buildroot/aarch64-buildroot-linuxgnu/sysroot/usr/include/features.h:412:4: error: #warning _FORTIFY_SOURCE requires compiling with optimization (-O) [-Werror=cpp] 412 | # warning _FORTIFY_SOURCE requires compiling with optimization (-O) | ^~~~~~~ cc1: all warnings being treated as errors


报错仅指定了

-DCMAKE_TOOLCHAIN_FILE="/opt/aarch64-buildroot-linux-gnu_sdkbuildroot/share/buildroot/toolchainfile.cmake"交叉工具链,且该cmake定义了_FORTIFY_SOURCE。

可不指定CMAKE_TOOLCHAIN_FILE,或删除_FORTIFY_SOURCE。

CMake找不到exlibConfig.cmake
编译ament_cmake_vendor_package报找不到exlib,但实际该exlib库都被正确指定了。

root@db4be0cd3eca:/buildroot/build/ros/ament_cmake_vendor_package/test# make [ 33%] Built target exlib_bad [ 66%] Built target exlib_good [ 71%] Performing configure step for 'depender' loading initial cache file /buildroot/build/ros/ament_cmake_vendor_package/test/depender-config.cmake CMake Error at CMakeLists.txt:4 (find_package): By not providing "Findexlib.cmake" in CMAKE_MODULE_PATH this project has asked CMake to find a package configuration file provided by "exlib", but CMake did not find one. Could not find a package configuration file provided by "exlib" with any of the following names: exlibConfig.cmake exlib-config.cmake Add the installation prefix of "exlib" to CMAKE_PREFIX_PATH or set "exlib_DIR" to a directory containing one of the above files. If "exlib" provides a separate development package or SDK, be sure it has been installed. # strace make 可以看到: [pid 458018] newfstatat(AT_FDCWD, "/opt/aarch64-buildroot-linux-gnu_sdkbuildroot/aarch64-buildroot-linuxgnu/sysroot/buildroot/build/ros/ament_cmake_vendor_package/test/exlib_badprefix/install", 0x7ffca495cf50, 0) = -1 ENOENT (No such file or directory) # : # grep CMAKE_PREFIX_PATH depender-config.cmake set(CMAKE_PREFIX_PATH [= [/buildroot/build/ros/ament_cmake_vendor_package/test/exlib_badprefix/install;/buildroot/build/ros/ament_cmake_vendor_package/test/exlib_goodprefix/install;/buildroot/build/ros/ament_cmake_vendor_package/test/dependerprefix/install]=] CACHE INTERNAL "") 它去找了Toolchain目录下的sysroot/$CMAKE_PREFIX_PATH,所以找不到。


CMAKE_PREFIX_PATH设置是正确的,有包含exlib库的路径。

通过strace make 可以看到工具链实际去找的路径不正确,多加了

/opt/aarch64-buildroot-linuxgnu_sdk-buildroot/aarch64-buildroot-linux-gnu/sysroot/

原因: colcon命令中指定了参数

--cmake-args -DCMAKE_TOOLCHAIN_FILE="/opt/aarch64-buildroot-linux-gnu_sdk-buildroot/share/buildroot/toolchainfile.cmake" ,该设置与export环境变量mimix中设置的编译工具链不同导致。


pkg-config找不到

Starting >>> tracetools --- stderr: tracetools CMake Error at /usr/share/cmake- 3.22/Modules/FindPackageHandleStandardArgs.cmake:230(message): Could NOT find PkgConfig (missing: PKG_CONFIG_EXECUTABLE) Reason given by package: The command "/usr/bin/pkg-config" --version failed with output: stderr: /usr/bin/pkg-config: symbol lookup error: /usr/bin/pkg-config: undefined symbol: pkgconf_cross_personality_deinit result: 127 Call Stack (most recent call first): /usr/share/cmake-3.22/Modules/FindPackageHandleStandardArgs.cmake:594 (_FPHSA_FAILURE_MESSAGE) /usr/share/cmake-3.22/Modules/FindPkgConfig.cmake:99 (find_package_handle_standard_args) CMakeLists.txt:35 (find_package)

首先docker中应该有安装pkgconf(不是pkg-config),cmake中pkg_check_modules()会使用到。
Linux SDK中如果也编译了pkgconf,也会编译host-pkgconf,因为与docker的pkgconf版本不同, 在pkgconf.so动态库搜索时, 找到的是buildroot 编译的host pkgconf.so,所以失败。

需要设置PKG_CONFIG_PATH
在编译src/ros2/ros2_tracing/tracetools/时, 其CMakeLists.txt中指定:

pkg_check_modules(LTTNG REQUIRED lttng-ust)

编译报错:

Starting >>> tracetools --- stderr: tracetools CMake Error at /usr/share/cmake-3.22/Modules/FindPkgConfig.cmake:611 (message): A required package was not found Call Stack (most recent call first): /usr/share/cmake-3.22/Modules/FindPkgConfig.cmake:833 (_pkg_check_modules_internal) CMakeLists.txt:36 (pkg_check_modules)

通过strace -f 去抓取log, 发现并未在Linux SDK的sysroot中去查找,因此报错。

需要设置以下环境变量:

export PKG_CONFIG_PATH=/buildroot/host/aarch64-buildroot-linuxgnu/sysroot/usr/lib/pkgconfig

另一种情况是pkg-config找到了docker中的lttng,而不是target目标的,并报错如下:

Starting >>> tracetools --- stderr: tracetools /usr/lib/gcc-cross/aarch64-linux-gnu/11/../../../../aarch64-linux-gnu/bin/ld: cannot find -llttng-ust-common: No such file or directory collect2: error: ld returned 1 exit status gmake[2]: *** [CMakeFiles/tracetools.dir/build.make:129: libtracetools.so] Error 1 gmake[1]: *** [CMakeFiles/Makefile2:161: CMakeFiles/tracetools.dir/all] Error 2 gmake[1]: *** Waiting for unfinished jobs.... gmake: *** [Makefile:146: all] Error 2 --- Failed <<< tracetools [4.72s, exited with code 2]

因为找到的是docker的lttng,它的版本与buildroot不同, 前者lttng-ust.pc声明需要链接lttng-ustcommon,但buildroot中缺少lttng-ust-common这个库。

同样需要设置环境变量:

export PKG_CONFIG_PATH=/buildroot/host/aarch64-buildroot-linuxgnu/sysroot/usr/lib/pkgconfig

该参数已经在编译脚本中指定

Docker中可以不安装lttng包

需要设置CMAKE_INCLUDE_PATH

Starting >>> orocos_kdl_vendor --- stderr: orocos_kdl_vendor Cloning into 'orocos_kdl-507de66'... done. HEAD is now at 507de66 Fix CMake warning on Windows (#392) Submodule 'python_orocos_kdl/pybind11' (https://github.com/pybind/pybind11.git) registered for path 'python_orocos_kdl/pybind11' Cloning into '/buildroot/build/ros/orocos_kdl_vendor/orocos_kdl-507de66- prefix/src/orocos_kdl-507de66/python_orocos_kdl/pybind11'... CMake Error: The following variables are used in this project, but they are set to NOTFOUND. Please set them or make sure they are set and tested correctly in the CMake files: EIGEN3_INCLUDE_DIR (ADVANCED)

因为Linux SDK编译过程中生成的include文件路径需要单独指定, 否则cmake无法搜索得到,如下:

export CMAKE_INCLUDE_PATH='/buildroot/host/aarch64-buildroot-linuxgnu/sysroot/usr/include/'
该参数已经在编译脚本中指定

unsafe header/library used in cross-compilation --- stderr: action_msgs aarch64-buildroot-linux-gnu-gcc: WARNING: unsafe header/library path used in cross-compilation: '-isystem' '/usr/local/lib/python3.10/distpackages/numpy/core/include' 在交叉编译过程中, python使用的是host端的/usr/bin/python,当numpy/numpyconfig.h查找不到时, 下列 的获取include dir无法正确得到目标板子的路径: # Check if numpy is in the include path find_file(_numpy_h numpy/numpyconfig.h PATHS ${PythonExtra_INCLUDE_DIRS} ) if(APPLE OR WIN32 OR NOT _numpy_h) # add include directory for numpy headers set(_python_code "import numpy" "print(numpy.get_include())" )


明确是由PythonExtra_INCLUDE_DIRS定义查找路径后, 在pybind11中查找该参数的定义是来自PYTHON_INCLUDE_DIR,因为我们是交叉编译,可在cross_compile.mimix中预设好该值。该参数已经在编译脚本中指定,可以指定多个目录。

END

声明:本文内容及配图由入驻作者撰写或者入驻合作网站授权转载。文章观点仅代表作者本人,不代表电子发烧友网立场。文章及其配图仅供工程师学习之用,如有内容侵权或者其他违规问题,请联系本站处理。 举报投诉
  • Ubuntu
    +关注

    关注

    5

    文章

    603

    浏览量

    32881
  • 瑞芯微
    +关注

    关注

    27

    文章

    699

    浏览量

    53482
  • ROS
    ROS
    +关注

    关注

    1

    文章

    290

    浏览量

    18474
  • rk3576
    +关注

    关注

    1

    文章

    228

    浏览量

    1371
  • RK3562
    +关注

    关注

    0

    文章

    88

    浏览量

    603
收藏 人收藏
加入交流群
微信小助手二维码

扫码添加小助手

加入工程师交流群

    评论

    相关推荐
    热点推荐

    ROS机器人开发更便捷,基于RK3568J+Debian系统发布!

    、路线控制偏离、系统通信异常等严重后果。而ROS系统凭借其优势,已成为AGV开发利器,广泛应用于各种机器人开发,并逐渐成为主流。 RK35
    发表于 07-09 11:38

    米尔瑞芯微RK3576实测轻松搞定三屏八摄像头

    约为65度。正面了高负载的低功耗和低发热特性。 RK3576将为多屏多摄像头应用场景带来更高性价比的选择 RK3576的多屏多摄像头能力使其适用于多种应用场景,包括机器人、工程
    发表于 01-17 11:33

    Mpp支持RK3576

    想问下,https://github.com/rockchip-linux/mpp这里面支持RK3576么,看介绍没有提到说支持RK3576 目前是买了个rk3576的机顶盒,搭载了安卓14,想做安卓视频硬解。
    发表于 06-13 15:35

    米尔RK3576核心板,让360环视技术开发更简单

    RK3576核心板集成了4路摄像头输入接口,非常适合小型智能设备或轻型机器人应用场景。在自动泊车、无人配送小车等项目中,只需4个摄像头即可覆盖车身四周,完成全景拼接和实时影像显示,大大降低了成本和部署难度
    发表于 08-06 18:13

    【作品合集】米尔RK3576开发板测评

    】米尔RK3576开发板免费试用 作者:EPTmachine【米尔RK3576开发板免费体验】1、开发环境、镜像烧录、QT开发环境搭建以及应用部署 【米尔RK3576开发板免费体验】2
    发表于 09-11 10:19

    巡检机器人落地攻略RK3576驱动12路低延迟视觉

    ,边走边看、实时回传、异常即告警。周三,机器人上电跑通:前后左右与顶部共 10~12路1080P 摄像头接入,基于米尔 RK3576开发板 完成 硬件编解码 + RTSP/SRT 低延迟推流;端到端延迟
    发表于 10-24 16:53

    RK3576机器人核心:三屏异显+八路摄像头,重塑机器人交互与感知

    瑞芯微RK3576 AIoT处理器处理器凭借其卓越的多屏异显与8路摄像头接入能力,为机器人领域带来革新。米尔电子MYD-LR3576开发板实测数据显示,在高负载CPU占用仅34%,完
    发表于 10-29 16:41

    ROS RIKIBOT基础--使用系列 第一章节】ROS机器人硬件系统 精选资料分享

    主控制器ROS控制器采用树莓派4B或者Jetson Nano,运行运行Ubuntu Mate18.04或Ubuntu18.04系统,具体型号有差异。
    发表于 07-30 06:59

    ROS机器人开发更便捷,基于RK3568J+Debian系统发布!

    ROS系统是什么 ROS(Robot Operating System)是一个适用于机器人的开源的元操作系统。它提供了操作
    发表于 11-30 16:01

    新品体验 | RK3576开发板

    前言:RK3576作为瑞芯微第二代8nm高性能AIOT平台,一经推出便获得了极大的关注。广州眺望电子科技有限公司是一家专注于嵌入式处理器模组研发与应用的国家高新技术企业,目前公司已推出的相关型号有
    的头像 发表于 11-01 08:08 2783次阅读
    新品体验 | <b class='flag-5'>RK3576</b>开发板

    RK3576单板发布倒计时:RK3399与RK3576对比

    好多人说RK3576RK3399的升级版,某种程度上也可以这么说,RK3576在强大的多媒体功能的基础上,性能和接口都进行了升级 一、工艺 性能 rk3576采用 Rockchip
    的头像 发表于 12-03 16:59 2111次阅读
    <b class='flag-5'>RK3576</b>单板发布倒计时:<b class='flag-5'>RK</b>3399与<b class='flag-5'>RK3576</b>对比

    硬核上车RK3576基于Ubuntu部署ROS机器人系统详细攻略(上)

    本文适用于瑞芯微RK3562、RK3566、RK3568、RK3576RK3588等Arm64位SoC,适配开发
    的头像 发表于 07-03 18:45 2090次阅读
    <b class='flag-5'>硬核</b><b class='flag-5'>上车</b>!<b class='flag-5'>RK3576</b>基于<b class='flag-5'>Ubuntu</b><b class='flag-5'>部署</b><b class='flag-5'>ROS</b><b class='flag-5'>机器人</b><b class='flag-5'>系统</b><b class='flag-5'>详细</b><b class='flag-5'>攻略</b>(上)

    系统适配 | RK3576适配Ubuntu20.04正式发布

    前言:为了满足广大开发者与嵌入式爱好者的需求!眺望电子正式宣布,已完成基于瑞芯微RK3576的开发板对Ubuntu20.04LTS操作系统的深度适配与优化。此次适配不仅成功移植了
    的头像 发表于 07-31 08:32 1463次阅读
    <b class='flag-5'>系统</b>适配 | <b class='flag-5'>RK3576</b>适配<b class='flag-5'>Ubuntu</b>20.04正式发布

    瑞芯微RK3576RK3576S有什么区别,性能参数配置与型号差异解析

    瑞芯微第二代8nm高性能AIOT平台RK3576家族再添新成员-RK3576S,先说结论:相较主型号的RK3576/RK3576J,性能略有缩减,而功耗有所降低。主要应用于商显终端、智
    的头像 发表于 08-14 23:57 1753次阅读
    瑞芯微<b class='flag-5'>RK3576</b>与<b class='flag-5'>RK3576</b>S有什么区别,性能参数配置与型号差异解析

    迅为如何在RK3576部署YOLOv5;基于RK3576构建智能门禁系统

    迅为如何在RK3576开发板上部署YOLOv5;基于RK3576构建智能门禁系统
    的头像 发表于 11-25 14:06 1063次阅读
    迅为如何在<b class='flag-5'>RK3576</b>上<b class='flag-5'>部署</b>YOLOv5;基于<b class='flag-5'>RK3576</b>构建智能门禁<b class='flag-5'>系统</b>