Tool/software:
Hi TI TDA4 support,
Our development team in India seems to have damaged the eDP port used by the single camera application to output the video stream to a monitor, as the TDA4 no longer detects that a monitor is present, even when the one they've been using all along is attached to the EVM.
Is there a simple way to route the ISP's output to the TDA4's other eDP port? I tried change the openVX display object's target from TIVX_TARGET_DISPLAY1 to TIVX_TARGET_DISPLAY2 as follows:
status = vxSetNodeTarget(obj->displayNode_MV, VX_TARGET_STRING, TIVX_TARGET_DISPLAY2);
but the EVM did not detect the monitor when I plugged it into the second display connector on the common processor board, with the result that I got the following error messages when trying to start the single camera application:
247.276632 s: VX_ZONE_ERROR:[ownContextSendCmd:875] Command ack message returned failure cmd_status: -1
247.276686 s: VX_ZONE_ERROR:[ownNodeKernelInit:590] Target kernel, TIVX_CMD_NODE_CREATE failed for node node_109
247.276694 s: VX_ZONE_ERROR:[ownNodeKernelInit:591] Please be sure the target callbacks have been registered for this core
247.276701 s: VX_ZONE_ERROR:[ownNodeKernelInit:592] If the target callbacks have been registered, please ensure no errors are occurring within the create callback of this kernel
247.276709 s: VX_ZONE_ERROR:[ownGraphNodeKernelInit:608] kernel init for node 6, kernel com.ti.display ... failed !!!
247.276731 s: VX_ZONE_ERROR:[vxVerifyGraph:2159] Node kernel init failed
247.276737 s: VX_ZONE_ERROR:[vxVerifyGraph:2213] Graph verify failed
I suspect some additional configuration changes are necessary in the app_init.c code that gets invoked by the source ./vision_apps_init.sh command, but it wan't obvious to me what changes would be necessary to make this work.
Thanks.
-Pete Tucker
