TDA4VM: The nested use of Scalar

ye ma

Part Number: TDA4VM

Hi,

I want to use two tivxVpacMscScaleNode, but the result is no graphics.It's show:

[MCU2_0] 40.839950 s: src/fvid2_drvMgr.c @ Line 759:
[MCU2_0] 40.839994 s: Driver create failed!!
[MCU2_0] 40.840030 s: VX_ZONE_ERROR:[tivxKernelImgMosaicMscDrvCreate:749] Fvid2_create failed

My code:

graph_parameter_index = 0;
add_graph_parameter_by_node_index(obj->graph, obj->captureObj.node, 1);
obj->captureObj.graph_parameter_index = graph_parameter_index;
graph_parameters_queue_params_list[graph_parameter_index].graph_parameter_index = graph_parameter_index;
graph_parameters_queue_params_list[graph_parameter_index].refs_list_size = MAX_NUM_BUF;
graph_parameters_queue_params_list[graph_parameter_index].refs_list = (vx_reference*)&obj->captureObj.capt_frames[0];
graph_parameter_index++;

vxSetGraphScheduleConfig(obj->graph, VX_GRAPH_SCHEDULE_MODE_QUEUE_AUTO, graph_parameter_index, graph_parameters_queue_params_list);
tivxSetGraphPipelineDepth(obj->graph, APP_PIPELINE_DEPTH);

tivxSetNodeParameterNumBufByIndex(obj->convertObj_1.node, 1, 6);

tivxSetNodeParameterNumBufByIndex(obj->scalerObj_1.node, 1, 6);
tivxSetNodeParameterNumBufByIndex(obj->scalerObj_1.node, 2, 6);

tivxSetNodeParameterNumBufByIndex(obj->scalerObj_2.node, 1, 8);
tivxSetNodeParameterNumBufByIndex(obj->scalerObj_2.node, 2, 8);

tivxSetNodeParameterNumBufByIndex(obj->imgMosaicObj_tmp.node, 1, 6);

Will scalar nodes not be nested?

PS ：

capture -> convert -> scalar 1->scalar2->mosaic->display

|--------------------------↑

over 3 years ago

0 Brijesh Jadav over 3 years ago

TI__Guru**** 475395 points

Hi ye ma,

It is possible to use scalar in this cascading way.. Could you please share the full log to see what exactly is the issue?

Also can you please see if mosaic node is removed, it works fine?

Regards,

Brijesh

0 ye ma over 3 years ago in reply to Brijesh Jadav

Prodigy 120 points

This is the full log:

====================================
Memory Parking Demo - Camera based
====================================

p: Print performance statistics

x: Exit

Enter Choice: [MCU2_0] 42.249677 s: REMOTE_SERVICE_SENSOR: Sensor(s) configuration done !!!

0 ye ma over 3 years ago in reply to Brijesh Jadav

Prodigy 120 points

Hi,

If mosaic node is removed, it works fine.

The graph is :

capture -> convert -> scalar 1->scalar2->display

What is the cause of Mosaic's error(Fvid2_create failed) please? Is my graph parameter set wrong, or should I not use it this way?

0 Brijesh Jadav over 3 years ago in reply to ye ma

TI__Guru**** 475395 points

Hi ye ma,

I suspect the scalar is running out of the instances.. Most likely, it is nothing to do with the mosaic node as such, even if you keep scalar1 -> mosaic, it would work.

Internally all scalar node uses MSC from VPAC and this driver supports limited number of instances..

You would probably have to increase the number of instance to run this graph.

Can you try increasing VHWA_M2M_MSC_MAX_HANDLES macro value in ti-processor-sdk-rtos-j721e-evm-08_00_00_12\pdk_jacinto_08_00_00_37\packages\ti\drv\vhwa\include\vhwa_m2mMsc.h and then rebuilding SDK?

Regards,

Brijesh

0 ye ma over 3 years ago in reply to Brijesh Jadav

Prodigy 120 points

Hi Brijesh Jadav，

Thank you very much. You perfect solution to my problem.

However, I would like to ask a question, you said that the VPAC driver supports a limited number of instances. So, what is the mapping between the M2M_MSC instance and the node? I see that the original value here is 8, and I have only created [ 2 Scalar + 1 Mosaic ], why is it exceeding the number of instances?

0 Brijesh Jadav over 3 years ago in reply to ye ma

TI__Guru**** 475395 points

Hi ye ma,

Yeah, that's surprising. It should not fail in this case. Scalar internally uses just single driver instance and so mosaic node. So there are only 3 instances opened.

Could you please put some debug code in ti-processor-sdk-rtos-j721e-evm-08_00_00_12\pdk_jacinto_08_00_00_37\packages\ti\drv\fvid2\src\fvid2_drvMgr.c in Fvid2_create and also in Vhwa_mscAllocHdlObj API in the file ti-processor-sdk-rtos-j721e-evm-08_00_00_12\pdk_jacinto_08_00_00_37\packages\ti\drv\vhwa\src\drv\vhwa_m2mMscApi.c to see where exactly it fails?

Regards,

Brijesh

0 ye ma over 3 years ago in reply to Brijesh Jadav

Prodigy 120 points

Hi,

I add some debug code in Fvid2_create and Vhwa_mscAllocHdlObj. But only Fvid2_create debugging information is displayed. As below:

root@Linux:/opt/vision_apps# ./run_app_memory_parking.sh
APP: Init ... !!!
MEM: Init ... !!!
MEM: Initialized DMA HEAP (fd=4) !!!
MEM: Init ... Done !!!
IPC: Init ... !!!
IPC: Init ... Done !!!
REMOTE_SERVICE: Init ... !!!
REMOTE_SERVICE: Init ... Done !!!
155.937109 s: GTC Frequency = 200 MHz
APP: Init ... Done !!!
155.937152 s: VX_ZONE_INIT:Enabled
155.937159 s: VX_ZONE_ERROR:Enabled
155.937164 s: VX_ZONE_WARNING:Enabled
155.937586 s: VX_ZONE_INIT:[tivxInit:71] Initialization Done !!!
155.937780 s: VX_ZONE_INIT:[tivxHostInit:48] Initialization Done for HOST !!!
[MCU2_0] 155.948469 s: src/fvid2_drvMgr.c @ Line 737:
[MCU2_0] 155.948521 s: ********drvHandle: a2d2813c drvId: 1000 instanceId: 1 createFxn: a351b0ad********
[MCU2_0] 156.030275 s: src/fvid2_drvMgr.c @ Line 737:
[MCU2_0] 156.030328 s: ********drvHandle: a315a8a8 drvId: 3000 instanceId: 0 createFxn: a34cb0bd********
[MCU2_0] 156.051809 s: src/fvid2_drvMgr.c @ Line 737:
[MCU2_0] 156.051880 s: ********drvHandle: a319d788 drvId: 5002 instanceId: 1 createFxn: a35380bd********
[MCU2_0] 156.052478 s: src/fvid2_drvMgr.c @ Line 737:
[MCU2_0] 156.052529 s: ********drvHandle: a319fac0 drvId: 5002 instanceId: 1 createFxn: a35380bd********
[MCU2_0] 156.053047 s: src/fvid2_drvMgr.c @ Line 737:
[MCU2_0] 156.053096 s: ********drvHandle: a31a1df8 drvId: 5002 instanceId: 1 createFxn: a35380bd********
[MCU2_0] 156.053570 s: src/fvid2_drvMgr.c @ Line 737:
[MCU2_0] 156.053613 s: ********drvHandle: a31a4130 drvId: 5002 instanceId: 1 createFxn: a35380bd********
[MCU2_0] 156.054433 s: src/fvid2_drvMgr.c @ Line 737:
[MCU2_0] 156.054489 s: ********drvHandle: a31a6468 drvId: 5002 instanceId: 1 createFxn: a35380bd********
[MCU2_0] 156.055055 s: src/fvid2_drvMgr.c @ Line 737:
[MCU2_0] 156.055102 s: ********drvHandle: a31a87a0 drvId: 5002 instanceId: 1 createFxn: a35380bd********
[MCU2_0] 156.055592 s: src/fvid2_drvMgr.c @ Line 737:
[MCU2_0] 156.055635 s: ********drvHandle: a31aaad8 drvId: 5002 instanceId: 1 createFxn: a35380bd********
[MCU2_0] 156.056158 s: src/fvid2_drvMgr.c @ Line 737:
[MCU2_0] 156.056204 s: ********drvHandle: a31ace10 drvId: 5002 instanceId: 1 createFxn: a35380bd********
[MCU2_0] 156.076749 s: src/fvid2_drvMgr.c @ Line 737:
[MCU2_0] 156.076799 s: ********drvHandle: a318bdc8 drvId: 5002 instanceId: 0 createFxn: a35380bd********
[MCU2_0] 156.076927 s: src/fvid2_drvMgr.c @ Line 737:
[MCU2_0] 156.076966 s: ********drvHandle: 0 drvId: 5002 instanceId: 1 createFxn: a35380bd********
[MCU2_0] 156.077010 s: src/fvid2_drvMgr.c @ Line 761:
[MCU2_0] 156.077034 s: Driver create failed!!
[MCU2_0] 156.077067 s: VX_ZONE_ERROR:[tivxKernelImgMosaicMscDrvCreate:749] Fvid2_create failed
[MCU2_0] 156.077853 s: src/fvid2_drvMgr.c @ Line 737:
[MCU2_0] 156.077954 s: ********drvHandle: a2d2c71c drvId: 1000 instanceId: 2 createFxn: a351b0ad********
================1234567======================
[MCU2_0] 156.179768 s: REMOTE_SERVICE_SENSOR: Received command 00001002 to configure 4 sensor(s) !!!
[MCU2_0] 156.179939 s: REMOTE_SERVICE_SENSOR: IMX390: numSensors 4 portNum 1
[MCU2_0] 156.179991 s: REMOTE_SERVICE_SENSOR: IMX390: Configuring UB960 ... !!!
[MCU2_0] 158.163872 s: REMOTE_SERVICE_SENSOR: ser i2c addr 0x74
[MCU2_0] 158.195872 s: REMOTE_SERVICE_SENSOR: sensor i2c addr 0x40
[MCU2_0] 158.403874 s: REMOTE_SERVICE_SENSOR: ser i2c addr 0x76
[MCU2_0] 158.435877 s: REMOTE_SERVICE_SENSOR: sensor i2c addr 0x42
[MCU2_0] 158.643872 s: REMOTE_SERVICE_SENSOR: ser i2c addr 0x78
[MCU2_0] 158.675870 s: REMOTE_SERVICE_SENSOR: sensor i2c addr 0x44
[MCU2_0] 158.883872 s: REMOTE_SERVICE_SENSOR: ser i2c addr 0x7a
[MCU2_0] 158.915869 s: REMOTE_SERVICE_SENSOR: sensor i2c addr 0x46
[MCU2_0] 159.059876 s: select channel 0x1
[MCU2_0] 159.060110 s: select channel 0x12
[MCU2_0] 159.060311 s: select channel 0x24
[MCU2_0] 159.060504 s: select channel 0x38
[MCU2_0] 159.060701 s: check port 0x1 status
[MCU2_0] 159.076007 s: Sensor Addr 0x4d Read Value 0x3b
[MCU2_0] 159.092003 s: Sensor Addr 0x5b Read Value 0xb0
[MCU2_0] 159.108004 s: Sensor Addr 0x73 Read Value 0x3
[MCU2_0] 159.124002 s: Sensor Addr 0x74 Read Value 0xc0
[MCU2_0] 159.140008 s: Sensor Addr 0x75 Read Value 0xa
[MCU2_0] 159.156004 s: Sensor Addr 0x76 Read Value 0x0
[MCU2_0] 159.171870 s: check port 0x12 status
[MCU2_0] 159.188006 s: Sensor Addr 0x4d Read Value 0x7b
[MCU2_0] 159.204013 s: Sensor Addr 0x5b Read Value 0xb0
[MCU2_0] 159.220008 s: Sensor Addr 0x73 Read Value 0x3
[MCU2_0] 159.236006 s: Sensor Addr 0x74 Read Value 0xc0
[MCU2_0] 159.252002 s: Sensor Addr 0x75 Read Value 0xa
[MCU2_0] 159.268000 s: Sensor Addr 0x76 Read Value 0x0
[MCU2_0] 159.283872 s: check port 0x24 status
[MCU2_0] 159.300005 s: Sensor Addr 0x4d Read Value 0xbb
[MCU2_0] 159.316002 s: Sensor Addr 0x5b Read Value 0xb0
[MCU2_0] 159.332004 s: Sensor Addr 0x73 Read Value 0x3
[MCU2_0] 159.348005 s: Sensor Addr 0x74 Read Value 0xc0
[MCU2_0] 159.364003 s: Sensor Addr 0x75 Read Value 0xa
[MCU2_0] 159.379999 s: Sensor Addr 0x76 Read Value 0x0
[MCU2_0] 159.395871 s: check port 0x38 status
[MCU2_0] 159.412003 s: Sensor Addr 0x4d Read Value 0xfb
[MCU2_0] 159.428001 s: Sensor Addr 0x5b Read Value 0xb0
[MCU2_0] 159.444000 s: Sensor Addr 0x73 Read Value 0x3
[MCU2_0] 159.460001 s: Sensor Addr 0x74 Read Value 0xc0
[MCU2_0] 159.476001 s: Sensor Addr 0x75 Read Value 0xa
[MCU2_0] 159.492003 s: Sensor Addr 0x76 Read Value 0x0

====================================
Memory Parking Demo - Camera based
====================================

p: Print performance statistics

x: Exit

Enter Choice: [MCU2_0] 159.507880 s: REMOTE_SERVICE_SENSOR: Sensor(s) configuration done !!!

Fvid2 code:

/* Call the driver's create function */
drvHandle = drv->drvOps->createFxn(
drvId,
instanceId,
createArgs,
createStatusArgs,
tempCbParams);
GT_4trace(Fvid2Trace, GT_ERR, "********drvHandle: %x drvId: %x instanceId: %x createFxn: %x********\r\n", drvHandle, drvId,
instanceId, drv->drvOps->createFxn);

main.c

if (VX_SUCCESS == status)
{
graph_parameter_index = 0;
add_graph_parameter_by_node_index(obj->graph, obj->captureObj.node, 1);
obj->captureObj.graph_parameter_index = graph_parameter_index;
graph_parameters_queue_params_list[graph_parameter_index].graph_parameter_index = graph_parameter_index;
graph_parameters_queue_params_list[graph_parameter_index].refs_list_size = 4;
graph_parameters_queue_params_list[graph_parameter_index].refs_list = (vx_reference*)&obj->captureObj.capt_frames[0];
graph_parameter_index++;

vxSetGraphScheduleConfig(obj->graph, VX_GRAPH_SCHEDULE_MODE_QUEUE_AUTO, graph_parameter_index, graph_parameters_queue_params_list);
tivxSetGraphPipelineDepth(obj->graph, APP_PIPELINE_DEPTH);

tivxSetNodeParameterNumBufByIndex(obj->convertObj_1.node, 1, 6);

tivxSetNodeParameterNumBufByIndex(obj->scalerObj_1.node, 1, 6);
tivxSetNodeParameterNumBufByIndex(obj->scalerObj_1.node, 2, 6);

tivxSetNodeParameterNumBufByIndex(obj->scalerObj_2.node, 1, 8);
tivxSetNodeParameterNumBufByIndex(obj->scalerObj_2.node, 2, 8);

tivxSetNodeParameterNumBufByIndex(obj->imgMosaicObj_tmp.node, 1, 6);
APP_PRINTF("Pipeline params setup done!\n");
}

0 Brijesh Jadav over 3 years ago in reply to ye ma

TI__Guru**** 475395 points

Hi,

As we can see in the log, instance-1 is created for more than 8 times, and that's why it is failing..

One question, for how many channels are you using scalar and mosaic nodes? ie how many camera are connected?

Regards,

Brijesh

0 ye ma over 3 years ago in reply to Brijesh Jadav

Prodigy 120 points

Hi,

The camera number is 4.

0 ye ma over 3 years ago in reply to Brijesh Jadav

Prodigy 120 points

Hi,

At the same time, I ran into another problem, also Mosaic. When I used two Mosaic, the program reported an error.

capture->convert->scalar->mosaic1->encode

|--------->mosaic2->display

Log:

root@Linux:/opt/vision_apps# ./run_app_memory_parking.sh
APP: Init ... !!!
MEM: Init ... !!!
MEM: Initialized DMA HEAP (fd=4) !!!
MEM: Init ... Done !!!
IPC: Init ... !!!
IPC: Init ... Done !!!
REMOTE_SERVICE: Init ... !!!
REMOTE_SERVICE: Init ... Done !!!
45.076586 s: GTC Frequency = 200 MHz
APP: Init ... Done !!!
45.079923 s: VX_ZONE_INIT:Enabled
45.079934 s: VX_ZONE_ERROR:Enabled
45.079940 s: VX_ZONE_WARNING:Enabled
45.080519 s: VX_ZONE_INIT:[tivxInit:71] Initialization Done !!!
45.080693 s: VX_ZONE_INIT:[tivxHostInit:48] Initialization Done for HOST !!!
45.092572 s: VX_ZONE_ERROR:[vxReleaseKernel:43] Invalid kernel reference
45.142856 s: VX_ZONE_ERROR:[vxCreateNodeByStructure:96] failed to retrieve kernel enum 0
45.142910 s: VX_ZONE_ERROR:[vxGetStatus:713] Reference is NULL
================66666======================
[MCU2_0] 45.313924 s: REMOTE_SERVICE_SENSOR: Received command 00001002 to configure 4 sensor(s) !!!
[MCU2_0] 45.314064 s: REMOTE_SERVICE_SENSOR: IMX390: numSensors 4 portNum 1
[MCU2_0] 45.314108 s: REMOTE_SERVICE_SENSOR: IMX390: Configuring UB960 ... !!!
[MCU2_0] 47.297823 s: REMOTE_SERVICE_SENSOR: ser i2c addr 0x74
[MCU2_0] 47.329826 s: REMOTE_SERVICE_SENSOR: sensor i2c addr 0x40
[MCU2_0] 47.537820 s: REMOTE_SERVICE_SENSOR: ser i2c addr 0x76
[MCU2_0] 47.569818 s: REMOTE_SERVICE_SENSOR: sensor i2c addr 0x42
[MCU2_0] 47.777819 s: REMOTE_SERVICE_SENSOR: ser i2c addr 0x78
[MCU2_0] 47.809818 s: REMOTE_SERVICE_SENSOR: sensor i2c addr 0x44
[MCU2_0] 48.017818 s: REMOTE_SERVICE_SENSOR: ser i2c addr 0x7a
[MCU2_0] 48.049819 s: REMOTE_SERVICE_SENSOR: sensor i2c addr 0x46
[MCU2_0] 48.193823 s: select channel 0x1
[MCU2_0] 48.194053 s: select channel 0x12
[MCU2_0] 48.194252 s: select channel 0x24
[MCU2_0] 48.194450 s: select channel 0x38
[MCU2_0] 48.194643 s: check port 0x1 status
[MCU2_0] 48.209947 s: Sensor Addr 0x4d Read Value 0x3b
[MCU2_0] 48.225947 s: Sensor Addr 0x5b Read Value 0xb0
[MCU2_0] 48.241950 s: Sensor Addr 0x73 Read Value 0x3
[MCU2_0] 48.257950 s: Sensor Addr 0x74 Read Value 0xc0
[MCU2_0] 48.273954 s: Sensor Addr 0x75 Read Value 0xa
[MCU2_0] 48.289950 s: Sensor Addr 0x76 Read Value 0x0
[MCU2_0] 48.305818 s: check port 0x12 status
[MCU2_0] 48.321945 s: Sensor Addr 0x4d Read Value 0x7b
[MCU2_0] 48.337950 s: Sensor Addr 0x5b Read Value 0xb0
[MCU2_0] 48.353951 s: Sensor Addr 0x73 Read Value 0x3
[MCU2_0] 48.369947 s: Sensor Addr 0x74 Read Value 0xc0
[MCU2_0] 48.385951 s: Sensor Addr 0x75 Read Value 0xa
[MCU2_0] 48.401948 s: Sensor Addr 0x76 Read Value 0x0
[MCU2_0] 48.417816 s: check port 0x24 status
[MCU2_0] 48.433952 s: Sensor Addr 0x4d Read Value 0xbb
[MCU2_0] 48.449950 s: Sensor Addr 0x5b Read Value 0xb0
[MCU2_0] 48.465948 s: Sensor Addr 0x73 Read Value 0x3
[MCU2_0] 48.481959 s: Sensor Addr 0x74 Read Value 0xc0
[MCU2_0] 48.497947 s: Sensor Addr 0x75 Read Value 0xa
[MCU2_0] 48.513951 s: Sensor Addr 0x76 Read Value 0x0
[MCU2_0] 48.529824 s: check port 0x38 status
[MCU2_0] 48.545968 s: Sensor Addr 0x4d Read Value 0xfb
[MCU2_0] 48.561946 s: Sensor Addr 0x5b Read Value 0xb0
[MCU2_0] 48.577947 s: Sensor Addr 0x73 Read Value 0x3
[MCU2_0] 48.593956 s: Sensor Addr 0x74 Read Value 0xc0
[MCU2_0] 48.609947 s: Sensor Addr 0x75 Read Value 0xa
[MCU2_0] 48.625947 s: Sensor Addr 0x76 Read Value 0x0
48.641979 s: VX_ZONE_ERROR:[tivxGraphParameterEnqueueReadyRef:251] Reference enqueue not supported at graph parameter index 0
48.641994 s: VX_ZONE_ERROR:[tivxGraphParameterEnqueueReadyRef:251] Reference enqueue not supported at graph parameter index 0
48.642018 s: VX_ZONE_ERROR:[tivxGraphParameterEnqueueReadyRef:251] Reference enqueue not supported at graph parameter index 0
48.642027 s: VX_ZONE_ERROR:[tivxGraphParameterEnqueueReadyRef:251] Reference enqueue not supported at graph parameter index 0
48.642035 s: VX_ZONE_ERROR:[vxGraphParameterDequeueDoneRef:344] Reference dequeue not supported at graph parameter index 0
48.642042 s: VX_ZONE_ERROR:[tivxGraphParameterEnqueueReadyRef:251] Reference enqueue not supported at graph parameter index 0
48.642050 s: VX_ZONE_ERROR:[vxGraphParameterDequeueDoneRef:344] Reference dequeue not supported at graph parameter index 0
48.642056 s: VX_ZONE_ERROR:[tivxGraphParameterEnqueueReadyRef:251] Reference enqueue not supported at graph parameter index 0
48.642064 s: VX_ZONE_ERROR:[vxGraphParameterDequeueDoneRef:344] Reference dequeue not supported at graph parameter index 0
48.642070 s: VX_ZONE_ERROR:[tivxGraphParameterEnqueueReadyRef:251] Reference enqueue not supported at graph parameter index 0
48.642078 s: VX_ZONE_ERROR:[vxGraphParameterDequeueDoneRef:344] Reference dequeue not supported at graph parameter index 0
48.642084 s: VX_ZONE_ERROR:[tivxGraphParameterEnqueueReadyRef:251] Reference enqueue not supported at graph parameter index 0

====================================
Memory Parking Demo - Camera based
====================================

p: Print performance statistics

x: Exit

Enter Choice: 48.642098 s: VX_ZONE_ERROR:[vxGraphParameterDequeueDoneRef:344] Reference dequeue not supported at graph parameter index 0
48.642129 s: VX_ZONE_ERROR:[tivxGraphParameterEnqueueReadyRef:251] Reference enqueue not supported at graph parameter index 0
48.642138 s: VX_ZONE_ERROR:[vxGraphParameterDequeueDoneRef:344] Reference dequeue not supported at graph parameter index 0
48.642149 s: VX_ZONE_ERROR:[tivxGraphParameterEnqueueReadyRef:251] Reference enqueue not supported at graph parameter index 0
48.642158 s: VX_ZONE_ERROR:[vxGraphParameterDequeueDoneRef:344] Reference dequeue not supported at graph parameter index 0
48.642165 s: VX_ZONE_ERROR:[tivxGraphParameterEnqueueReadyRef:251] Reference enqueue not supported at graph parameter index 0
48.642173 s: VX_ZONE_ERROR:[vxGraphParameterDequeueDoneRef:344] Reference dequeue not supported at graph parameter index 0
48.642179 s: VX_ZONE_ERROR:[tivxGraphParameterEnqueueReadyRef:251] Reference enqueue not supported at graph parameter index 0
48.642187 s: VX_ZONE_ERROR:[vxGraphParameterDequeueDoneRef:344] Reference dequeue not supported at graph parameter index 0
48.642194 s: VX_ZONE_ERROR:[tivxGraphParameterEnqueueReadyRef:251] Reference enqueue not supported at graph parameter index 0
48.642201 s: VX_ZONE_ERROR:[vxGraphParameterDequeueDoneRef:344] Reference dequeue not supported at graph parameter index 0
48.642208 s: VX_ZONE_ERROR:[tivxGraphParameterEnqueueReadyRef:251] Reference enqueue not supported at graph parameter index 0
48.642215 s: VX_ZONE_ERROR:[vxGraphParameterDequeueDoneRef:344] Reference dequeue not supported at graph parameter index 0
48.642222 s: VX_ZONE_ERROR:[tivxGraphParameterEnqueueReadyRef:251] Reference enqueue not supported at graph parameter index 0
48.642229 s: VX_ZONE_ERROR:[vxGraphParameterDequeueDoneRef:344] Reference dequeue not supported at graph parameter index 0
48.642236 s: VX_ZONE_ERROR:[tivxGraphParameterEnqueueReadyRef:251] Reference enqueue not supported at graph parameter index 0
48.642243 s: VX_ZONE_ERROR:[vxGraphParameterDequeueDoneRef:344] Reference dequeue not supported at graph parameter index 0
48.642249 s: VX_ZONE_ERROR:[tivxGraphParameterEnqueueReadyRef:251] Reference enqueue not supported at graph parameter index 0
48.642257 s: VX_ZONE_ERROR:[vxGraphParameterDequeueDoneRef:344] Reference dequeue not supported at graph parameter index 0
48.642264 s: VX_ZONE_ERROR:[tivxGraphParameterEnqueueReadyRef:251] Reference enqueue not supported at graph parameter index 0
48.642271 s: VX_ZONE_ERROR:[vxGraphParameterDequeueDoneRef:344] Reference dequeue not supported at graph parameter index 0
48.642277 s: VX_ZONE_ERROR:[tivxGraphParameterEnqueueReadyRef:251] Reference enqueue not supported at graph parameter index 0
48.642285 s: VX_ZONE_ERROR:[vxGraphParameterDequeueDoneRef:344] Reference dequeue not supported at graph parameter index 0
48.642292 s: VX_ZONE_ERROR:[tivxGraphParameterEnqueueReadyRef:251] Reference enqueue not supported at graph parameter index 0
48.642300 s: VX_ZONE_ERROR:[vxGraphParameterDequeueDoneRef:344] Reference dequeue not supported at graph parameter index 0
48.642306 s: VX_ZONE_ERROR:[tivxGraphParameterEnqueueReadyRef:251] Reference enqueue not supported at graph parameter index 0
48.642313 s: VX_ZONE_ERROR:[vxGraphParameterDequeueDoneRef:344] Reference dequeue not supported at graph parameter index 0
48.642319 s: VX_ZONE_ERROR:[tivxGraphParameterEnqueueReadyRef:251] Reference enqueue not supported at graph parameter index 0
48.642327 s: VX_ZONE_ERROR:[vxGraphParameterDequeueDoneRef:344] Reference dequeue not supported at graph parameter index 0

For some reason, scalar and Mosaic nodes have always had problems with their use. In fact, both of these problems come from graph, which I am doing now. It is a simplified state with problems.

I hope you can answer my questions. Thank you very much.

0 Brijesh Jadav over 3 years ago in reply to ye ma

TI__Guru**** 475395 points

Then this is expected, because two scalar nodes will use up all 8 instances of the MSC driver and open for mosaic will fail..

What exactly is the usecase? Why do you require two scalar node and a mosaic in the graph? Could you please help us understand?

0 ye ma over 3 years ago in reply to Brijesh Jadav

Prodigy 120 points

Hi,

This is a very complex instance. As below:

Can you give me some guidance on why the two Mosaic failed? Thank you very much.

0 Brijesh Jadav over 3 years ago in reply to ye ma

TI__Guru**** 475395 points

Hi Ye Ma,

Scalar driver by default supports at max 8 handles.. since you are using above path for 4 channels, the two scalar node itself will consume 8 handles, and then when mosaic node tries to open scalar driver, it will fail.

Could you please try increasing number of handles in the scalar driver as i suggested before? Also can you please spread scalar on two instances? Scalar and mosaic are supported on two scalar targets.. Can you keep scalar1 on MSC1 and scalar2 on MSC2 and similarly for mosaic node? This will spread the load on MSC, otherwise you might see performance issues (depending on resolution and fps) on scalar..

Regards,

Brijesh

Processors

Processors forum

TDA4VM: The nested use of Scalar