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:如何启用双 DSS DPI

Guru**** 2587365 points


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

https://e2e.ti.com/support/processors-group/processors/f/processors-forum/1575402/tda4vm-how-to-enable-dual-dss-dpi

器件型号:TDA4VM


工具/软件:

尊敬的专家:

我们之前已成功使用一个 DPI 输出一组摄像头数据。

现在、我们打算使用双 DPI 来输出两组摄像头数据。

我  在 app_cfg_mcu2_0.h 文件中启用了 enable_dss_dual。

但是、从 enable_dss_dual 定义中的注释可以知道默认情况下会启用 HDMI 和 eDP。

我做了以下修改以适应双 DPI。

diff --git a/platform/j721e/rtos/common/app_cfg_mcu2_0.h b/platform/j721e/rtos/common/app_cfg_mcu2_0.h
index 0b6ac38..d9b2154 100755
--- a/platform/j721e/rtos/common/app_cfg_mcu2_0.h
+++ b/platform/j721e/rtos/common/app_cfg_mcu2_0.h
@@ -83,8 +83,8 @@
      * - When ENABLE_DSS_SINGLE is defined, only one of ENABLE_DSS_HDMI or ENABLE_DSS_EDP should be defined
      * - When ENABLE_DSS_DUAL is defined, ENABLE_DSS_HDMI and ENABLE_DSS_EDP are not used, both EDP and HDMI are enabled unconditionally
      */
-    #define ENABLE_DSS_SINGLE
-    #undef  ENABLE_DSS_DUAL
+    #undef ENABLE_DSS_SINGLE
+    #define  ENABLE_DSS_DUAL
 
     /* define below to enable eDP display,
        make sure to undef ENABLE_DSS_HDMI & ENABLE_DSS_DSI as well */
diff --git a/platform/j721e/rtos/common/app_init.c b/platform/j721e/rtos/common/app_init.c
index e9589e0..219165b 100755
--- a/platform/j721e/rtos/common/app_init.c
+++ b/platform/j721e/rtos/common/app_init.c
@@ -656,15 +656,15 @@ int32_t appInit()
         /* Do not rely on "init". Always provide known good tmings */
         for(i=0; i<2; i++)
         {
-            prm.display[i].timings.width        = 1920U;
-            prm.display[i].timings.height       = 1080U;
-            prm.display[i].timings.hFrontPorch  = 88U;
-            prm.display[i].timings.hBackPorch   = 148U;
-            prm.display[i].timings.hSyncLen     = 44U;
-            prm.display[i].timings.vFrontPorch  = 4U;
-            prm.display[i].timings.vBackPorch   = 36U;
+            prm.display[i].timings.width        = 1280U;
+            prm.display[i].timings.height       = 720U;
+            prm.display[i].timings.hFrontPorch  = 640U;
+            prm.display[i].timings.hBackPorch   = 0U;
+            prm.display[i].timings.hSyncLen     = 0U;
+            prm.display[i].timings.vFrontPorch  = 5U;
+            prm.display[i].timings.vBackPorch   = 20U;
             prm.display[i].timings.vSyncLen     = 5U;
-            prm.display[i].timings.pixelClock   = 148500000ULL;
+            prm.display[i].timings.pixelClock   = 72000000ULL;
         }
 
         status = appDssDualDisplayDefaultInit(&prm);
diff --git a/utils/dss/include/app_dss_defaults.h b/utils/dss/include/app_dss_defaults.h
index a0f0220..25c7a72 100755
--- a/utils/dss/include/app_dss_defaults.h
+++ b/utils/dss/include/app_dss_defaults.h
@@ -93,6 +93,8 @@ extern "C" {
 /** \brief Enables DSI output on AOU LCD Display */
 #define APP_DSS_DEFAULT_DISPLAY_TYPE_DSI         (2u)
 
+#define APP_DSS_DEFAULT_DISPLAY_TYPE_DPI1_HDMI   (3u)
+
 /* ========================================================================== */
 /*                         Structure Declarations                             */
 /* ========================================================================== */
diff --git a/utils/dss/src/app_dss_dual_display_defaults.c b/utils/dss/src/app_dss_dual_display_defaults.c
index 2d890d0..1c35f24 100755
--- a/utils/dss/src/app_dss_dual_display_defaults.c
+++ b/utils/dss/src/app_dss_dual_display_defaults.c
@@ -80,7 +80,7 @@ void appDssDualDisplayDefaultSetDefaultPrm(app_dss_dual_display_default_prm_t *d
 
         if(i==0)
         {
-            prm->display_type = APP_DSS_DEFAULT_DISPLAY_TYPE_EDP;
+            prm->display_type = APP_DSS_DEFAULT_DISPLAY_TYPE_DPI1_HDMI;
         }
         else
         {
@@ -136,15 +136,15 @@ int32_t appDssDualDisplayDefaultInit(app_dss_dual_display_default_prm_t *dual_di
 
         memcpy(&obj->initPrm, prm, sizeof(*prm));
 
-        if(prm->display_type==APP_DSS_DEFAULT_DISPLAY_TYPE_EDP)
+        if(prm->display_type==APP_DSS_DEFAULT_DISPLAY_TYPE_DPI1_HDMI)
         {
-            appLogPrintf("DSS DUAL DISPLAY: Display %d type is eDP !!!\n", i);
+            appLogPrintf("DSS DUAL DISPLAY: Display %d type is HDMI1 !!!\n", i);
             obj->nodeOverlayId = APP_DCTRL_NODE_OVERLAY1;
             obj->nodeVpId      = APP_DCTRL_NODE_VP1;
-            obj->nodeDpiId     = APP_DCTRL_NODE_EDP_DPI0;
+            obj->nodeDpiId     = APP_DCTRL_NODE_DPI_DPI1;
             obj->overlayId     = APP_DSS_OVERLAY_ID_1;
             obj->vpId          = APP_DSS_VP_ID_1;
-            obj->videoIfWidth  = APP_DCTRL_VIFW_36BIT;
+            obj->videoIfWidth  = APP_DCTRL_VIFW_10BIT;
         }
         else
         {
@@ -154,7 +154,7 @@ int32_t appDssDualDisplayDefaultInit(app_dss_dual_display_default_prm_t *dual_di
             obj->nodeDpiId     = APP_DCTRL_NODE_DPI_DPI0;
             obj->overlayId     = APP_DSS_OVERLAY_ID_2;
             obj->vpId          = APP_DSS_VP_ID_2;
-            obj->videoIfWidth  = APP_DCTRL_VIFW_24BIT;
+            obj->videoIfWidth  = APP_DCTRL_VIFW_10BIT;
         }
 
         appDssConfigurePm(prm);
diff --git a/utils/dss/src/app_dss_soc.c b/utils/dss/src/app_dss_soc.c
index 4d4b383..536a2c8 100755
--- a/utils/dss/src/app_dss_soc.c
+++ b/utils/dss/src/app_dss_soc.c
@@ -232,6 +232,14 @@ void appDssConfigurePm(app_dss_default_prm_t *prm)
         SET_CLOCK_STATE(TISCI_DEV_DSS0, TISCI_DEV_DSS0_DSS_INST0_DPI_1_IN_2X_CLK, 0, TISCI_MSG_VALUE_CLOCK_SW_STATE_REQ);
         SET_DEVICE_STATE_ON(TISCI_DEV_DSS0);
     }
+    else if(prm->display_type==APP_DSS_DEFAULT_DISPLAY_TYPE_DPI1_HDMI)
+    {
+        SET_DEVICE_STATE_OFF(TISCI_DEV_DSS0);
+        SET_CLOCK_PARENT(TISCI_DEV_DSS0, TISCI_DEV_DSS0_DSS_INST0_DPI_1_IN_2X_CLK, TISCI_DEV_DSS0_DSS_INST0_DPI_1_IN_2X_CLK_PARENT_DPI1_EXT_CLKSEL_OUT0);
+        SET_CLOCK_FREQ (TISCI_DEV_DSS0, TISCI_DEV_DSS0_DSS_INST0_DPI_1_IN_2X_CLK, prm->timings.pixelClock);
+        SET_CLOCK_STATE(TISCI_DEV_DSS0, TISCI_DEV_DSS0_DSS_INST0_DPI_1_IN_2X_CLK, 0, TISCI_MSG_VALUE_CLOCK_SW_STATE_REQ);
+        SET_DEVICE_STATE_ON(TISCI_DEV_DSS0);
+    }
     else if (prm->display_type==APP_DSS_DEFAULT_DISPLAY_TYPE_DSI)
     {
         #if defined (SOC_J721E) 

 但是、在运行应用程序时、 发现 vxVerifyGraph 接口卡住、并且没有错误日志。

在运行应用程序之前、我首先运行“source ./vision_apps_init.sh“、发现以下错误。

您能帮我检查一下我的修改是否有任何问题或遗漏吗?

谢谢!

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

    您好:

    已分配给专家、请等待答复。

    谢谢

    此致

    Tarun

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

    尊敬的 Cheng:

    下面列出了支持的 VP 和 dpi 输出组合:

    static const Fvid2_GraphEdgeInfo gDctrlGraphEdgeInfoDefaults[DSS_DCTRL_MAX_EDGES] =
    {
        {DSS_DCTRL_NODE_VID1,     DSS_DCTRL_NODE_OVERLAY1},
        {DSS_DCTRL_NODE_VIDL1,    DSS_DCTRL_NODE_OVERLAY1},
        {DSS_DCTRL_NODE_VID2,     DSS_DCTRL_NODE_OVERLAY1},
        {DSS_DCTRL_NODE_VIDL2,    DSS_DCTRL_NODE_OVERLAY1},
        {DSS_DCTRL_NODE_VID1,     DSS_DCTRL_NODE_OVERLAY2},
        {DSS_DCTRL_NODE_VIDL1,    DSS_DCTRL_NODE_OVERLAY2},
        {DSS_DCTRL_NODE_VID2,     DSS_DCTRL_NODE_OVERLAY2},
        {DSS_DCTRL_NODE_VIDL2,    DSS_DCTRL_NODE_OVERLAY2},
        {DSS_DCTRL_NODE_VID1,     DSS_DCTRL_NODE_OVERLAY3},
        {DSS_DCTRL_NODE_VIDL1,    DSS_DCTRL_NODE_OVERLAY3},
        {DSS_DCTRL_NODE_VID2,     DSS_DCTRL_NODE_OVERLAY3},
        {DSS_DCTRL_NODE_VIDL2,    DSS_DCTRL_NODE_OVERLAY3},
        {DSS_DCTRL_NODE_VID1,     DSS_DCTRL_NODE_OVERLAY4},
        {DSS_DCTRL_NODE_VIDL1,    DSS_DCTRL_NODE_OVERLAY4},
        {DSS_DCTRL_NODE_VID2,     DSS_DCTRL_NODE_OVERLAY4},
        {DSS_DCTRL_NODE_VIDL2,    DSS_DCTRL_NODE_OVERLAY4},
        {DSS_DCTRL_NODE_OVERLAY1, DSS_DCTRL_NODE_VP1},
        {DSS_DCTRL_NODE_OVERLAY2, DSS_DCTRL_NODE_VP2},
        {DSS_DCTRL_NODE_OVERLAY3, DSS_DCTRL_NODE_VP3},
        {DSS_DCTRL_NODE_OVERLAY4, DSS_DCTRL_NODE_VP4},
        {DSS_DCTRL_NODE_VP1,      DSS_DCTRL_NODE_EDP_DPI0},
        {DSS_DCTRL_NODE_VP1,      DSS_DCTRL_NODE_DISCSYNC0},
        {DSS_DCTRL_NODE_VP1,      DSS_DCTRL_NODE_DISCSYNC1},
        {DSS_DCTRL_NODE_VP2,      DSS_DCTRL_NODE_DPI_DPI0},
        {DSS_DCTRL_NODE_VP2,      DSS_DCTRL_NODE_DPI_DPI1},
        {DSS_DCTRL_NODE_VP2,      DSS_DCTRL_NODE_EDP_DPI1},
        {DSS_DCTRL_NODE_VP3,      DSS_DCTRL_NODE_DSI_DPI2},
        {DSS_DCTRL_NODE_VP3,      DSS_DCTRL_NODE_EDP_DPI2},
        {DSS_DCTRL_NODE_VP3,      DSS_DCTRL_NODE_DISCSYNC0},
        {DSS_DCTRL_NODE_VP4,      DSS_DCTRL_NODE_DPI_DPI0},
        {DSS_DCTRL_NODE_VP4,      DSS_DCTRL_NODE_DPI_DPI1},
        {DSS_DCTRL_NODE_VP4,      DSS_DCTRL_NODE_EDP_DPI3},
        {DSS_DCTRL_NODE_VIDL2,    DSS_DCTRL_NODE_WB},
        {DSS_DCTRL_NODE_OVERLAY1, DSS_DCTRL_NODE_WB},
        {DSS_DCTRL_NODE_OVERLAY2, DSS_DCTRL_NODE_WB},
        {DSS_DCTRL_NODE_OVERLAY3, DSS_DCTRL_NODE_WB},
        {DSS_DCTRL_NODE_OVERLAY4, DSS_DCTRL_NODE_WB}
    };

    因此、VP_1 不能与 DPI1 一起使用。 将 VP_4 与 DPI1 一起使用、将 VP_2 与 DPI0 一起使用。

    此致、
    Gokul

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

    尊敬的 Gokul:

    DisplayM2M 节点还使用 VP_4。

    这是否意味着不能使用 DisplayM2M 节点? 或者 DisplayM2M 节点是否可以使用其他 VP?

    谢谢!

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

    尊敬的 Cheng:

    如果您需要两个 DPI 输出并且两者都 用于输出 BT601 格式、则是、不能使用 DISPLAY M2M。  

    此致、

    Brijesh

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

    尊敬的 Brijesh 和 Gokul:

    [引述 userid=“637485" url="“ url="~“~/support/processors-group/processors/f/processors-forum/1575402/tda4vm-how-to-enable-dual-dss-dpi/6068532 ]]将 VP_4 与 DPI1 结合使用、将 VP_2 与  DPI0结合使用

    根据上述建议、我作了以下补充修改。

    diff --git a/platform/j721e/rtos/common/app_init.c b/platform/j721e/rtos/common/app_init.c
    index 219165b..85e61c5 100755
    --- a/platform/j721e/rtos/common/app_init.c
    +++ b/platform/j721e/rtos/common/app_init.c
    @@ -652,7 +652,7 @@ int32_t appInit()
             /* default parameters are enough to enable both EDP and HDMI */
             appDssDualDisplayDefaultSetDefaultPrm(&prm);
    
    -        prm.enableM2m                           = true;
    +        prm.enableM2m                           = false;
             /* Do not rely on "init". Always provide known good tmings */
             for(i=0; i<2; i++)
             {
    diff --git a/utils/dss/src/app_dss_dual_display_defaults.c b/utils/dss/src/app_dss_dual_display_defaults.c
    index 1c35f24..1c4221b 100755
    --- a/utils/dss/src/app_dss_dual_display_defaults.c
    +++ b/utils/dss/src/app_dss_dual_display_defaults.c
    @@ -119,7 +119,7 @@ int32_t appDssDualDisplayDefaultInit(app_dss_dual_display_default_prm_t *dual_di
         dssParams.isPipeAvailable[APP_DSS_VID_PIPE_ID_VID1] = true;
         dssParams.isPipeAvailable[APP_DSS_VID_PIPE_ID_VID2] = true;
         dssParams.isPipeAvailable[APP_DSS_VID_PIPE_ID_VIDL1] = true;
    -    dssParams.isPipeAvailable[APP_DSS_VID_PIPE_ID_VIDL2] = false;
    +    dssParams.isPipeAvailable[APP_DSS_VID_PIPE_ID_VIDL2] = true;
    
         for(i=0; i<APP_DSS_VID_PIPE_ID_MAX; i++)
         {
    @@ -139,11 +139,11 @@ int32_t appDssDualDisplayDefaultInit(app_dss_dual_display_default_prm_t *dual_di
             if(prm->display_type==APP_DSS_DEFAULT_DISPLAY_TYPE_DPI1_HDMI)
             {
                 appLogPrintf("DSS DUAL DISPLAY: Display %d type is HDMI1 !!!\n", i);
    -            obj->nodeOverlayId = APP_DCTRL_NODE_OVERLAY1;
    -            obj->nodeVpId      = APP_DCTRL_NODE_VP1;
    +            obj->nodeOverlayId = APP_DCTRL_NODE_OVERLAY4;
    +            obj->nodeVpId      = APP_DCTRL_NODE_VP4;
                 obj->nodeDpiId     = APP_DCTRL_NODE_DPI_DPI1;
    -            obj->overlayId     = APP_DSS_OVERLAY_ID_1;
    -            obj->vpId          = APP_DSS_VP_ID_1;
    +            obj->overlayId     = APP_DSS_OVERLAY_ID_4;
    +            obj->vpId          = APP_DSS_VP_ID_4;
                 obj->videoIfWidth  = APP_DCTRL_VIFW_10BIT;
             }
             else
    

    在我创建的图形中、当显示节点的“pipeId"参数“参数设置为 defalut 值 2 (VP2) 时、即可成功传输图像数据。

    当我将显示节点的“pipeid"参数“参数更改为 3 (VP4) 时、vxVerifyGraph 界面出现以下错误。

    root@Linux:/opt/vision_apps/test_hw# ./capture_hw.out
    APP: Init ... !!!
    MEM: Init ... !!!
    MEM: Initialized DMA HEAP (fd=5) !!!
    MEM: Init ... Done !!!
    IPC: Init ... !!!
    IPC: Init ... Done !!!
    REMOTE_SERVICE: Init ... !!!
    REMOTE_SERVICE: Init ... Done !!!
       129.643864 s: GTC Frequency = 200 MHz
    APP: Init ... Done !!!
    appCommonInit  success  !
       129.644072 s:  VX_ZONE_INIT:Enabled
       129.644085 s:  VX_ZONE_ERROR:Enabled
       129.644090 s:  VX_ZONE_WARNING:Enabled
       129.646070 s:  VX_ZONE_INIT:[tivxInitLocal:130] Initialization Done !!!
       129.646172 s:  VX_ZONE_INIT:[tivxHostInitLocal:101] Initialization Done for HOST !!!
    [CAPTURE_MODULE]: errorframe_Y: data_ptr=0xffff95bdc000, size = 657920, dim_y = 514, stride_y = 1280
    captureObj init done!
    displayObj init done!
    graph Set Reference Name  Success !!
    captureObj node graph done  !
    displayObj node graph done !
    vxSetGraphScheduleConfig done !
    tivxSetGraphPipelineDepth done !
       129.654545 s:  VX_ZONE_ERROR:[ownContextSendCmd:822] Command ack message returned failure cmd_status: -1
       129.654566 s:  VX_ZONE_ERROR:[ownContextSendCmd:862] tivxEventWait() failed.
       129.654573 s:  VX_ZONE_ERROR:[ownNodeKernelInit:584] Target kernel, TIVX_CMD_NODE_CREATE failed for node DisplayNode
       129.654579 s:  VX_ZONE_ERROR:[ownNodeKernelInit:585] Please be sure the target callbacks have been registered for this core
       129.654585 s:  VX_ZONE_ERROR:[ownNodeKernelInit:586] If the target callbacks have been registered, please ensure no errors are occurring within the create callback of this kernel
       129.654592 s:  VX_ZONE_ERROR:[ownGraphNodeKernelInit:583] kernel init for node 1, kernel com.ti.display ... failed !!!
       129.654606 s:  VX_ZONE_ERROR:[vxVerifyGraph:2059] Node kernel init failed
       129.654612 s:  VX_ZONE_ERROR:[vxVerifyGraph:2113] Graph verify failed
    capture_hw: Verifying graph failed!
    app_create_graph exiting
    deinit app...
    app_deinit_capture done
    app_deinit_display done
    tivxHwaUnLoadKernels done
    tivxVideoIOUnLoadKernels done
    tivxImagingUnLoadKernels done
    tivxImgProcUnLoadKernels done
    tivxFileIOUnLoadKernels done
       129.657088 s:  VX_ZONE_WARNING:[vxReleaseContext:1099] A kernel with name com.ti.display has not been removed, possibly due to a kernel module not being unloaded.
       129.657099 s:  VX_ZONE_WARNING:[vxReleaseContext:1100] Removing as a part of garbage collection
       129.657107 s:  VX_ZONE_WARNING:[ownDecrementReference:486] #### EXTERNAL REF COUNT IS ALREADY ZERO!!! 0xffffa14a8120 type:00000804 #####
       129.657114 s:  VX_ZONE_WARNING:[vxReleaseContext:1099] A kernel with name com.ti.capture has not been removed, possibly due to a kernel module not being unloaded.
       129.657120 s:  VX_ZONE_WARNING:[vxReleaseContext:1100] Removing as a part of garbage collection
       129.657126 s:  VX_ZONE_WARNING:[ownDecrementReference:486] #### EXTERNAL REF COUNT IS ALREADY ZERO!!! 0xffffa14a9810 type:00000804 #####
       129.657133 s:  VX_ZONE_WARNING:[vxReleaseContext:1088] Found a reference 0xffffa1520988 of type 0000080f at external count 1, internal count 2, releasing it
       129.657139 s:  VX_ZONE_WARNING:[vxReleaseContext:1090] Releasing reference (name=image_107) now as a part of garbage collection
       129.657146 s:  VX_ZONE_WARNING:[vxReleaseContext:1088] Found a reference 0xffffa0b720d0 of type 00000802 at external count 1, internal count 0, releasing it
       129.657152 s:  VX_ZONE_WARNING:[vxReleaseContext:1090] Releasing reference (name=capture_hw) now as a part of garbage collection
       129.657232 s:  VX_ZONE_WARNING:[ownDecrementReference:486] #### EXTERNAL REF COUNT IS ALREADY ZERO!!! 0xffffa1520988 type:0000080f #####
    vxReleaseContext  done
       129.657468 s:  VX_ZONE_INIT:[tivxHostDeInitLocal:115] De-Initialization Done for HOST !!!
       129.661890 s:  VX_ZONE_INIT:[tivxDeInitLocal:193] De-Initialization Done !!!
    APP: Deinit ... !!!
    REMOTE_SERVICE: Deinit ... !!!
    [MCU2_0]    129.654239 s: src/drv/disp/dss_dispApi.c @ Line 273:
    [MCU2_0]    129.654286 s: Driver instance already created!!
    [MCU2_0]    129.654321 s: src/fvid2_drvMgr.c @ Line 759:
    [MCU2_0]    129.654344 s: Driver create failed!!
    [MCU2_0]    129.654378 s:  VX_ZONE_ERROR:[tivxDisplayCreate:555] DISPLAY: ERROR: Display Create Failed!
    [MCU2_0]    129.654774 s: ==========================================================
    [MCU2_0]    129.654862 s:  Capture Status: Instance|1
    [MCU2_0]    129.654896 s: ==========================================================
    [MCU2_0]    129.654936 s:  overflowCount: 0
    [MCU2_0]    129.654981 s:  spuriousUdmaIntrCount: 0
    REMOTE_SERVICE: Deinit ... Done !!!
    IPC: Deinit ... !!!
    [MCU2_0]    129.655009 s:  frontFIFOOvflCount: 0
    [MCU2_0]    129.655033 s:  crcCount: 0
    [MCU2_0]    129.655052 s:  eccCount: 0
    [MCU2_0]    129.655073 s:  correctedEccCount: 0
    [MCU2_0]    129.655097 s:  dataIdErrorCount: 0
    [MCU2_0]    129.655120 s:  invalidAccessCount: 0
    [MCU2_0]    129.655143 s:  invalidSpCount: 0
    [MCU2_0]    129.655168 s:  strmFIFOOvflCount[0]: 0
    [MCU2_0]    129.655194 s:  strmFIFOOvflCount[1]: 0
    [MCU2_0]    129.655218 s:  Channel Num | Frame Queue Count | Frame De-queue Count | Frame Drop Count | Error Frame Count |
    [MCU2_0]    129.655269 s:            0 |                 0 |                    0 |                0 |                 0 |
    IPC: DeInit ... Done !!!
    MEM: Deinit ... !!!
    DDR_SHARED_MEM: Alloc's: 7 alloc's of 3289860 bytes
    DDR_SHARED_MEM: Free's : 7 free's  of 3289860 bytes
    DDR_SHARED_MEM: Open's : 0 allocs  of 0 bytes
    MEM: Deinit ... Done !!!
    APP: Deinit ... Done !!!
    

    您能帮助我分析一下问题是什么吗?

    谢谢!

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

    尊敬的 Cheng:

    如果已使用相同的 pipe_id 创建了驱动程序、则会出现此错误您可以检查是否已使用相同的 pipeId 创建显示节点、
    您是否可以在重新启动设备后检查此情况?

    此致、
    Gokul