This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

[参考译文] TDA4VM:加载模块时出现 Remoteproc 错误

Guru**** 2466550 points


请注意,本文内容源自机器翻译,可能存在语法或其它翻译错误,仅供参考。如需获取准确内容,请参阅链接中的英语原文或自行翻译。

https://e2e.ti.com/support/processors-group/processors/f/processors-forum/1471438/tda4vm-remoteproc-errors-when-loading-module

器件型号:TDA4VM

工具与软件:

1.在 SDK10中、REMOTEPROC=y、RPMSG_NS=y 和 RPMSG_virtiio=y 中、正确吗?

2.这意味着我需要构建和加载的模块是:

* TI_K3_R5_REMOTEPROC

* RPMSG_CTRL

* RPMSG_CHAR

3.我按以下顺序加载它们:

ROOT@AS-P-3-340009:~# insmod /lib/modules/6.6.58-ti-01614-g52c7243d3aa4/kernel/drivers/rpmsg/rpmsg_char.ko

ROOT@AS-P-3-340009:~# insmod /lib/modules/6.6.58-ti-01614-g52c7243d3aa4/kernel/drivers/rpmsg/rpmsg_ctrl.ko

ROOT@AS-P-3-340009:~# insmod /lib/modules/6.6.58-ti-01614-g52c7243d3aa4/kernel/drivers/remoteproc/ti_k3_r5_remoteproc.ko

[ 114.739842] k3_r5_rproc bus@100000:bus@28380000:r5fss@41000000:k3_r5_cluster_rproc_init 失败、ret =-517

[114.756315] remoteproc remoteproc0:正在释放41000000.r5f

[ 114.768334] k3_r5_rproc bus@100000:r5fss@5c00000:k3_r5_cluster_rproc_init 失败、ret =-517

[ 114.782663] remoteproc remoteproc0:正在释放5c0000.r5f

[ 114.791826] k3_r5_rproc bus@100000:r5fss@5e00000:k3_r5_cluster_rproc_init 失败、ret =-517

[ 114.803325] remoteproc remoteproc0:正在释放5e0000.r5f

正如您所看到的,我仍然收到这些集群错误,现在我没有在/sys/class/remoteproc 下得到任何 remoteproc*

当我 至少有 TI_K3_R5_REMOTEPROC=y 时、我得到了 remoteproc*条目、并且可以加载和运行固件。

我在做什么错?

/Bo

  • 请注意,本文内容源自机器翻译,可能存在语法或其它翻译错误,仅供参考。如需获取准确内容,请参阅链接中的英语原文或自行翻译。

    尊敬的 Bo:

    Unknown 说:
    1. 在 SDK10中、REMOTEPROC=y、RPMSG_Ns=y 和 RPMSG_virtio=y、这是正确的吗?[/QUOT]

    是的、正确。 这些来自上游默认值 默认配置 非常重要。

    [报价用户 id="551261" url="~/support/processors-group/processors/f/processors-forum/1471438/tda4vm-remoteproc-errors-when-loading-module "]

    ROOT@AS-P-3-340009:~# insmod /lib/modules/6.6.58-ti-01614-g52c7243d3aa4/kernel/drivers/rpmsg/rpmsg_char.ko

    ROOT@AS-P-3-340009:~# insmod /lib/modules/6.6.58-ti-01614-g52c7243d3aa4/kernel/drivers/rpmsg/rpmsg_ctrl.ko

    ROOT@AS-P-3-340009:~# insmod /lib/modules/6.6.58-ti-01614-g52c7243d3aa4/kernel/drivers/remoteproc/ti_k3_r5_remoteproc.ko

    [报价]

    这种顺序是可以的。  加载前两个模块时不应出现任何行为变化、因为在初始化 Remoteproc 平台驱动程序之前不会创建 rpmsg 设备。

    [报价 userid="551261" url="~/support/processors-group/processors/f/processors-forum/1471438/tda4vm-remoteproc-errors-when-loading-module "[114.739842] k3_r5_rproc bus@100000:bus@28380000:r5fss@41000000:k3_r5_cluster_rproc_init 失败、ret =-517

    517是探头延迟的错误代码。 请检查邮箱配置一次。

    此致

    Suman

  • 请注意,本文内容源自机器翻译,可能存在语法或其它翻译错误,仅供参考。如需获取准确内容,请参阅链接中的英语原文或自行翻译。

    谢谢苏曼

    正如你所想的那样、它被证明是邮箱 DTS 设置。 在最后一个 SDK 中、它们在主 DTS 中以隐式方式启用。 在 SDK 10中、已在多个位置以及 MCU-WAKEUP DTS 中添加了 status ="已禁用"。

    以上操作使我的邮箱无法加载。 添加 status ="正常";成功了。

    谢谢!

    /Bo

  • 请注意,本文内容源自机器翻译,可能存在语法或其它翻译错误,仅供参考。如需获取准确内容,请参阅链接中的英语原文或自行翻译。

    很抱歉、我们很快就会联系到。

      内置 ti_k3_r5_remoteproc 仍然显示了上述情况。 这会使 Remoteproc*目录出现、但加载时间比我之前提到的要长2秒。

    将 ti_k3_r5_remoteproc 编译为模块:

    root@AS-P-3-340009:~# depmod
    root@AS-P-3-340009:~# modprobe rpmsg_char
    root@AS-P-3-340009:~# modprobe rpmsg_ctrl
    root@AS-P-3-340009:~# modprobe ti_k3_r5_remoteproc
    [ 134.351145] k3_r5_rproc bus@100000:bus@28380000:r5fss@41000000: k3_r5_cluster_rproc_init failed, ret = -517
    [ 134.363988] remoteproc remoteproc0: releasing 41000000.r5f
    [ 134.375151] k3_r5_rproc bus@100000:r5fss@5c00000: k3_r5_cluster_rproc_init failed, ret = -517
    [ 134.387868] remoteproc remoteproc0: releasing 5c00000.r5f
    [ 134.398446] k3_r5_rproc bus@100000:r5fss@5e00000: k3_r5_cluster_rproc_init failed, ret = -517
    [ 134.410214] remoteproc remoteproc0: releasing 5e00000.r5f

    没有 remoteproc*目录。

    我已经检查邮箱配置、没有什么与 common-proc-board dts 不同的地方。

    请提供建议。

    /Bo

  • 请注意,本文内容源自机器翻译,可能存在语法或其它翻译错误,仅供参考。如需获取准确内容,请参阅链接中的英语原文或自行翻译。

    尊敬的 Bo:

    以下是我的 config 中用于 remoteprocs 和 rpmsg 的设置:

    #                                       
    # Remoteproc drivers        
    #                           
    CONFIG_REMOTEPROC=y                     
    CONFIG_REMOTEPROC_CDEV=y    
    CONFIG_PRU_REMOTEPROC=m         
    CONFIG_TI_K3_DSP_REMOTEPROC=m           
    CONFIG_TI_K3_M4_REMOTEPROC=m      
    CONFIG_TI_K3_R5_REMOTEPROC=m 
    # end of Remoteproc drivers             
                                           
    #                               
    # Rpmsg drivers                         
    #                                      
    CONFIG_RPMSG=y         
    CONFIG_RPMSG_CHAR=m                     
    CONFIG_RPMSG_CTRL=m                    
    CONFIG_RPMSG_NS=y              
    # CONFIG_RPMSG_QCOM_GLINK_RPM is not set
    CONFIG_RPMSG_VIRTIO=y                  
    CONFIG_RPMSG_PRU=m                      
    # end of Rpmsg drivers

    我的/etc/modprobe.d/blacklist.conf

    blacklist ti_k3_r5_remoteproc

    终端:

    root@j721e-evm:~# lsmod | grep proc
    pru_rproc              20480  0
    pruss                  16384  1 pru_rproc
    ti_k3_dsp_remoteproc    16384  0
    root@j721e-evm:~# modprobe ti_k3_r5_remoteproc
    [   44.463135] platform 41000000.r5f: R5F core may have been powered on by a different host, programmed state (0) != actual state (1)
    [   44.479006] platform 41000000.r5f: configured R5F for IPC-only mode
    [   44.485473] platform 41000000.r5f: assigned reserved memory node vision-apps-r5f-dma-memory@a0000000
    [   44.495317] remoteproc remoteproc15: 41000000.r5f is available
    [   44.501221] remoteproc remoteproc15: attaching to 41000000.r5f
    [   44.508004] platform 41000000.r5f: R5F core initialized in IPC-only mode
    [   44.514745] rproc-virtio rproc-virtio.17.auto: assigned reserved memory node vision-apps-r5f-dma-memory@a0000000
    [   44.525461] virtio_rpmsg_bus virtio3: rpmsg host is online
    [   44.532629] rproc-virtio rproc-virtio.17.auto: registered virtio3 (type 7)
    [   44.539571] virtio_rpmsg_bus virtio3: creating channel ti.ipc4.ping-pong addr 0xd
    [   44.541754] remoteproc remoteproc15: remote processor 41000000.r5f is now attached
    [   44.547222] virtio_rpmsg_bus virtio3: creating channel rpmsg_chrdev addr 0xe
    [   44.573286] platform 5c00000.r5f: configured R5F for remoteproc mode
    [   44.580146] platform 5c00000.r5f: assigned reserved memory node vision-apps-r5f-dma-memory@a2000000
    [   44.590801] remoteproc remoteproc16: 5c00000.r5f is available
    [   44.634637] remoteproc remoteproc16: powering up 5c00000.r5f
    [   44.640338] remoteproc remoteproc16: Booting fw image j7-main-r5f0_0-fw, size 1572544
    [   44.653044] rproc-virtio rproc-virtio.18.auto: assigned reserved memory node vision-apps-r5f-dma-memory@a2000000
    [   44.655663] platform 5d00000.r5f: configured R5F for remoteproc mode
    [   44.664365] virtio_rpmsg_bus virtio4: rpmsg host is online
    [   44.676788] rproc-virtio rproc-virtio.18.auto: registered virtio4 (type 7)
    [   44.677649] platform 5d00000.r5f: assigned reserved memory node vision-apps-r5f-dma-memory@a4000000
    [   44.683697] remoteproc remoteproc16: remote processor 5c00000.r5f is now up
    [   44.698534] remoteproc remoteproc17: 5d00000.r5f is available
    [   44.714650] remoteproc remoteproc17: powering up 5d00000.r5f
    [   44.720519] remoteproc remoteproc17: Booting fw image j7-main-r5f0_1-fw, size 322804
    [   44.730501] rproc-virtio rproc-virtio.19.auto: assigned reserved memory node vision-apps-r5f-dma-memory@a4000000
    [   44.743143] virtio_rpmsg_bus virtio5: rpmsg host is online
    [   44.749307] rproc-virtio rproc-virtio.19.auto: registered virtio5 (type 7)
    [   44.756212] platform 5e00000.r5f: configured R5F for remoteproc mode
    [   44.762657] virtio_rpmsg_bus virtio5: creating channel rpmsg_chrdev addr 0xd
    [   44.770053] platform 5e00000.r5f: assigned reserved memory node vision-apps-r5f-dma-memory@a6000000
    [   44.770484] remoteproc remoteproc17: remote processor 5d00000.r5f is now up
    [   44.786153] remoteproc remoteproc18: 5e00000.r5f is available
    [   44.792556] remoteproc remoteproc18: loading /lib/firmware/j7-main-r5f1_0-fw failed with error -22
    [   44.801515] remoteproc remoteproc18: Direct firmware load for j7-main-r5f1_0-fw failed with error -22
    [   44.810732] remoteproc remoteproc18: powering up 5e00000.r5f
    [   44.816407] remoteproc remoteproc18: loading /lib/firmware/j7-main-r5f1_0-fw failed with error -22
    [   44.825353] remoteproc remoteproc18: Direct firmware load for j7-main-r5f1_0-fw failed with error -22
    [   44.834556] remoteproc remoteproc18: request_firmware failed: -22
    ...

    您的所有配置是否都反映了 SDK 中的默认配置?

    此致!
    Jared

  • 请注意,本文内容源自机器翻译,可能存在语法或其它翻译错误,仅供参考。如需获取准确内容,请参阅链接中的英语原文或自行翻译。

    尊敬的 Jared:

    我的设置与您的设置类似、但我们的芯片上没有任何 DSP:s、因此我没有加载任何 ti_k3_dsp_remoteproc 模块。 我也没有加载 PRU remoteproc 模块。

    我将 ti_k3_r5_remoteproc 列入黑名单、但 modpro探测 会提供另一个结果:

    root@AS-P-3-340009:~# lsmod
    Module                  Size  Used by
    
    root@AS-P-3-340009:~# modprobe ti_k3_r5_remoteproc
    [  153.675255] k3_r5_rproc bus@100000:bus@28380000:r5fss@41000000: k3_r5_cluster_rproc_init failed, ret = -517
    [  153.689119] remoteproc remoteproc0: releasing 41000000.r5f
    [  153.703415] k3_r5_rproc bus@100000:r5fss@5c00000: k3_r5_cluster_rproc_init failed, ret = -517
    [  153.715401] remoteproc remoteproc0: releasing 5c00000.r5f
    [  153.725780] k3_r5_rproc bus@100000:r5fss@5e00000: k3_r5_cluster_rproc_init failed, ret = -517
    [  153.738330] remoteproc remoteproc0: releasing 5e00000.r5f
    

    此外、即使我也得到错误-517、如果我将其构建为"ti_k3_r5_remoteproc=y"、remoteproc 是否正常工作呢? 当构建它并作为模块加载它时,我得到相同的错误,但所有 remoteproc*目录都丢失了:

    root@AS-P-3-340009:~# ls /sys/class/remoteproc/ -al
    total 0
    drwxr-xr-x 2 root root 0 Feb 11 08:41 .
    drwxr-xr-x 76 root root 0 Feb 11 08:41 ..

    我想到的一个问题是 U-Boot 的版本。 我们仍在发布版本2023-04、这会是问题吗?

    此致、

    /Bo

  • 请注意,本文内容源自机器翻译,可能存在语法或其它翻译错误,仅供参考。如需获取准确内容,请参阅链接中的英语原文或自行翻译。

    尊敬的 Bo:

    您正在使用哪个版本的 ti-sysfw? 此外、您是否能够迁移到更新版本的 u-boot、以防万一?

    此致!
    Jared

  • 请注意,本文内容源自机器翻译,可能存在语法或其它翻译错误,仅供参考。如需获取准确内容,请参阅链接中的英语原文或自行翻译。

    尊敬的 Jared:

    U-Boot SPL 2023.04-ti-g500dd8824a78 (Feb 10 2025 - 09:48:27 +0000)
    SYSFW ABI: 3.1 (firmware rev 0x000a '10.0.1--v10.00.01 (Fiery Fox)')

    我们目前正在迁移到更新的 U-Boot、即2024.04。 我们最近从内核6.1.112迁移到了6.6.58。

    此致、

    /Bo

  • 请注意,本文内容源自机器翻译,可能存在语法或其它翻译错误,仅供参考。如需获取准确内容,请参阅链接中的英语原文或自行翻译。

    尊敬的 Bo:

    我将测试 u-boot 2023.04并查看结果。

    我当前的设置使用:

    U-Boot SPL 2024.04-ti-g818c76aed67f (Aug 01 2024 - 19:19:47 +0000)
    SYSFW ABI: 4.0 (firmware rev 0x000a '10.0.8--v10.00.08 (Fiery Fox)')

    此致!
    Jared

  • 请注意,本文内容源自机器翻译,可能存在语法或其它翻译错误,仅供参考。如需获取准确内容,请参阅链接中的英语原文或自行翻译。

    尊敬的 Jared:

    我刚尝试了 SYSFW 的更新版本:

    U-Boot SPL 2023.04-ti-g500dd8824a78 (Feb 12 2025 - 11:44:14 +0000)
    SYSFW ABI: 4.0 (firmware rev 0x000a '10.1.6--v10.01.06 (Fiery Fox)')


    没有变化。

    此致、

    /Bo

  • 请注意,本文内容源自机器翻译,可能存在语法或其它翻译错误,仅供参考。如需获取准确内容,请参阅链接中的英语原文或自行翻译。

    尊敬的 Bo:

    我使用 u-boot 2023.04进行了测试、发现没有问题:

    U-Boot SPL 2023.04 (Feb 11 2025 - 17:49:02 -0600)
    SYSFW ABI: 4.0 (firmware rev 0x000a '10.1.6--v10.01.06 (Fiery Fox)')

    运行 ls /sys/class/remoteproc 时、我还看到目录正确出现:

    root@j721e-evm:~# ls /sys/class/remoteproc/ -al
    total 0
    drwxr-xr-x  2 root root 0 Feb 27 21:09 .
    drwxr-xr-x 76 root root 0 Feb 27 21:08 ..
    lrwxrwxrwx  1 root root 0 Feb 27 21:09 remoteproc0 -> ../../devices/platform/bus@100000/4d80800000.dsp/remoteproc/remoteproc0
    lrwxrwxrwx  1 root root 0 Feb 27 21:09 remoteproc1 -> ../../devices/platform/bus@100000/4d81800000.dsp/remoteproc/remoteproc1
    lrwxrwxrwx  1 root root 0 Feb 27 21:09 remoteproc10 -> ../../devices/platform/bus@100000/b100000.icssg/b104000.rtu/remoteproc/remoteproc10
    lrwxrwxrwx  1 root root 0 Feb 27 21:09 remoteproc11 -> ../../devices/platform/bus@100000/b100000.icssg/b10a000.txpru/remoteproc/remoteproc11
    lrwxrwxrwx  1 root root 0 Feb 27 21:09 remoteproc12 -> ../../devices/platform/bus@100000/b100000.icssg/b138000.pru/remoteproc/remoteproc12
    lrwxrwxrwx  1 root root 0 Feb 27 21:09 remoteproc13 -> ../../devices/platform/bus@100000/b100000.icssg/b106000.rtu/remoteproc/remoteproc13
    lrwxrwxrwx  1 root root 0 Feb 27 21:09 remoteproc14 -> ../../devices/platform/bus@100000/b100000.icssg/b10c000.txpru/remoteproc/remoteproc14
    lrwxrwxrwx  1 root root 0 Feb 27 21:09 remoteproc2 -> ../../devices/platform/bus@100000/64800000.dsp/remoteproc/remoteproc2
    lrwxrwxrwx  1 root root 0 Feb 27 21:09 remoteproc3 -> ../../devices/platform/bus@100000/b000000.icssg/b034000.pru/remoteproc/remoteproc3
    lrwxrwxrwx  1 root root 0 Feb 27 21:09 remoteproc4 -> ../../devices/platform/bus@100000/b000000.icssg/b004000.rtu/remoteproc/remoteproc4
    lrwxrwxrwx  1 root root 0 Feb 27 21:09 remoteproc5 -> ../../devices/platform/bus@100000/b000000.icssg/b00a000.txpru/remoteproc/remoteproc5
    lrwxrwxrwx  1 root root 0 Feb 27 21:09 remoteproc6 -> ../../devices/platform/bus@100000/b000000.icssg/b038000.pru/remoteproc/remoteproc6
    lrwxrwxrwx  1 root root 0 Feb 27 21:09 remoteproc7 -> ../../devices/platform/bus@100000/b000000.icssg/b006000.rtu/remoteproc/remoteproc7
    lrwxrwxrwx  1 root root 0 Feb 27 21:09 remoteproc8 -> ../../devices/platform/bus@100000/b000000.icssg/b00c000.txpru/remoteproc/remoteproc8
    lrwxrwxrwx  1 root root 0 Feb 27 21:09 remoteproc9 -> ../../devices/platform/bus@100000/b100000.icssg/b134000.pru/remoteproc/remoteproc9

    我怀疑您的设备树有问题、无论是在内核中还是 u-boot 中。

    此致!
    Jared

  • 请注意,本文内容源自机器翻译,可能存在语法或其它翻译错误,仅供参考。如需获取准确内容,请参阅链接中的英语原文或自行翻译。

    尊敬的 Jared:

    我离得越来越近了。 CONFIG_OMAP2PLUS_MBOX 被设置为"m"但我没有加载该模块。 如果我选择将 ti_k3_r5_remoteproc 构建为"y"、我猜该模块将是"y"、这就是我在执行该操作时它如何工作的原因。

    现在加载 remoteproc 模块会加载并启动所有主 r5f:s、并且 ping 正在运行:

    root@AS-P-3-340009:~# modprobe ti_k3_r5_remoteproc
    [   29.583410] k3_r5_rproc bus@100000:bus@28380000:r5fss@41000000: k3_r5_cluster_rproc_init entered.
    [   29.596484] platform 41000000.r5f: R5F core may have been powered on by a different host, programmed state (0) != actual state (1)
    [   29.608535] platform 41000000.r5f: configured R5F for IPC-only mode
    [   29.615122] platform 41000000.r5f: assigned reserved memory node r5f-dma-memory@a0000000
    [   29.624026] remoteproc remoteproc0: 41000000.r5f is available
    [   29.629933] remoteproc remoteproc0: attaching to 41000000.r5f
    [   29.636219] rproc-virtio rproc-virtio.12.auto: assigned reserved memory node r5f-dma-memory@a0000000
    [   29.647219] virtio_rpmsg_bus virtio0: rpmsg host is online
    [   29.652870] rproc-virtio rproc-virtio.12.auto: registered virtio0 (type 7)
    [   29.659808] remoteproc remoteproc0: remote processor 41000000.r5f is now attached
    [   29.661256] virtio_rpmsg_bus virtio0: creating channel ti.ipc4.ping-pong addr 0xd
    [   29.675232] virtio_rpmsg_bus virtio0: creating channel rpmsg_chrdev addr 0xe
    [   29.684590] k3_r5_rproc bus@100000:r5fss@5c00000: k3_r5_cluster_rproc_init entered.
    [   29.695747] platform 5c00000.r5f: configured R5F for remoteproc mode
    [   29.704541] platform 5c00000.r5f: assigned reserved memory node r5f-dma-memory@a2000000
    [   29.717104] remoteproc remoteproc1: 5c00000.r5f is available
    [   29.726612] remoteproc remoteproc1: powering up 5c00000.r5f
    [   29.732532] remoteproc remoteproc1: Booting fw image j7-main-r5f0_0-fw, size 90328
    [   29.747088] rproc-virtio rproc-virtio.13.auto: assigned reserved memory node r5f-dma-memory@a2000000
    [   29.757233] platform 5d00000.r5f: configured R5F for remoteproc mode
    [   29.763973] virtio_rpmsg_bus virtio1: rpmsg host is online
    [   29.769605] rproc-virtio rproc-virtio.13.auto: registered virtio1 (type 7)
    [   29.776847] remoteproc remoteproc1: remote processor 5c00000.r5f is now up
    [   29.783842] virtio_rpmsg_bus virtio1: creating channel ti.ipc4.ping-pong addr 0xd
    [   29.791537] virtio_rpmsg_bus virtio1: creating channel rpmsg_chrdev addr 0xe
    [   29.791665] platform 5d00000.r5f: assigned reserved memory node r5f-dma-memory@a3000000
    [   29.811195] remoteproc remoteproc2: 5d00000.r5f is available
    [   29.818410] remoteproc remoteproc2: powering up 5d00000.r5f
    [   29.824271] remoteproc remoteproc2: Booting fw image j7-main-r5f0_1-fw, size 90328
    [   29.835984] rproc-virtio rproc-virtio.14.auto: assigned reserved memory node r5f-dma-memory@a3000000
    [   29.842366] k3_r5_rproc bus@100000:r5fss@5e00000: k3_r5_cluster_rproc_init entered.
    [   29.851470] virtio_rpmsg_bus virtio2: rpmsg host is online
    [   29.861595] virtio_rpmsg_bus virtio2: creating channel ti.ipc4.ping-pong addr 0xd
    [   29.862783] rproc-virtio rproc-virtio.14.auto: registered virtio2 (type 7)
    [   29.869312] virtio_rpmsg_bus virtio2: creating channel rpmsg_chrdev addr 0xe
    [   29.877007] remoteproc remoteproc2: remote processor 5d00000.r5f is now up
    [   29.890872] platform 5e00000.r5f: configured R5F for remoteproc mode
    [   29.899202] platform 5e00000.r5f: assigned reserved memory node r5f-dma-memory@a4000000
    [   29.910849] remoteproc remoteproc3: 5e00000.r5f is available
    [   29.918241] remoteproc remoteproc3: powering up 5e00000.r5f
    [   29.924121] remoteproc remoteproc3: Booting fw image j7-main-r5f1_0-fw, size 90328
    [   29.941876] rproc-virtio rproc-virtio.15.auto: assigned reserved memory node r5f-dma-memory@a4000000
    [   29.952318] platform 5f00000.r5f: configured R5F for remoteproc mode
    [   29.952323] virtio_rpmsg_bus virtio3: rpmsg host is online
    [   29.952373] rproc-virtio rproc-virtio.15.auto: registered virtio3 (type 7)
    [   29.971246] virtio_rpmsg_bus virtio3: creating channel ti.ipc4.ping-pong addr 0xd
    [   29.979189] virtio_rpmsg_bus virtio3: creating channel rpmsg_chrdev addr 0xe
    [   29.979238] platform 5f00000.r5f: assigned reserved memory node r5f-dma-memory@a5000000
    [   29.986642] remoteproc remoteproc3: remote processor 5e00000.r5f is now up
    [   30.002820] remoteproc remoteproc4: 5f00000.r5f is available
    [   30.011453] remoteproc remoteproc4: powering up 5f00000.r5f
    [   30.017447] remoteproc remoteproc4: Booting fw image j7-main-r5f1_1-fw, size 90328
    [   30.033657] rproc-virtio rproc-virtio.16.auto: assigned reserved memory node r5f-dma-memory@a5000000
    [   30.045686] virtio_rpmsg_bus virtio4: rpmsg host is online
    [   30.051325] rproc-virtio rproc-virtio.16.auto: registered virtio4 (type 7)
    [   30.058332] virtio_rpmsg_bus virtio4: creating channel ti.ipc4.ping-pong addr 0xd
    [   30.066241] virtio_rpmsg_bus virtio4: creating channel rpmsg_chrdev addr 0xe
    [   30.073981] remoteproc remoteproc4: remote processor 5f00000.r5f is now up
    
    root@AS-P-3-340009:~# cat /sys/class/remoteproc/remoteproc*/state
    attached
    running
    running
    running
    running
    root@AS-P-3-340009:~# ./rpmsg_char_simple -r 2 -n 2
    Created endpt device rpmsg-char-2-604, fd = 4 port = 1025
    Exchanging 2 messages with rpmsg device rpmsg-char-2-604 on rproc id 2 ...
    
    Sending message #0: hello there 0!
    Received message #0: round trip delay(usecs) = 185270
    hello there 0!
    Sending message #1: hello there 1!
    Received message #1: round trip delay(usecs) = 118680
    hello there 1!
    
    Communicated 2 messages successfully on rpmsg-char-2-604
    
    TEST STATUS: PASSED
    root@AS-P-3-340009:~# ./rpmsg_char_simple -r 3 -n 2
    Created endpt device rpmsg-char-3-610, fd = 4 port = 1025
    Exchanging 2 messages with rpmsg device rpmsg-char-3-610 on rproc id 3 ...
    
    Sending message #0: hello there 0!
    Received message #0: round trip delay(usecs) = 178250
    hello there 0!
    Sending message #1: hello there 1!
    Received message #1: round trip delay(usecs) = 111815
    hello there 1!
    
    Communicated 2 messages successfully on rpmsg-char-3-610
    
    TEST STATUS: PASSED
    root@AS-P-3-340009:~# ./rpmsg_char_simple -r 4 -n 2
    Created endpt device rpmsg-char-4-612, fd = 4 port = 1025
    Exchanging 2 messages with rpmsg device rpmsg-char-4-612 on rproc id 4 ...
    
    Sending message #0: hello there 0!
    Received message #0: round trip delay(usecs) = 190190
    hello there 0!
    Sending message #1: hello there 1!
    Received message #1: round trip delay(usecs) = 117930
    hello there 1!
    
    Communicated 2 messages successfully on rpmsg-char-4-612
    
    TEST STATUS: PASSED
    root@AS-P-3-340009:~# ./rpmsg_char_simple -r 5 -n 2
    Created endpt device rpmsg-char-5-614, fd = 4 port = 1025
    Exchanging 2 messages with rpmsg device rpmsg-char-5-614 on rproc id 5 ...
    
    Sending message #0: hello there 0!
    Received message #0: round trip delay(usecs) = 1424740
    hello there 0!
    Sending message #1: hello there 1!
    Received message #1: round trip delay(usecs) = 153495
    hello there 1!
    
    Communicated 2 messages successfully on rpmsg-char-5-614
    
    TEST STATUS: PASSED
    

    感谢所有的帮助!

    /Bo

  • 请注意,本文内容源自机器翻译,可能存在语法或其它翻译错误,仅供参考。如需获取准确内容,请参阅链接中的英语原文或自行翻译。

    尊敬的 Bo:

    如果将  CONFIG_OMAP2PLUS_MBOX 设置为某个模块可修复您的问题、请将您的问题标记为已解决以关闭该主题。

    此致!
    Jared