Hello TI,
We are using "ezsdk_dm814x-evm_5_05_01_04" version of EzSDK. We have developed our own application in reference with capture_encode demo. We have made some changes in the application to support on-the-fly resolution change. To achieve this once resolution change is detected application restarts again. Our application works fine almost every time and is able to detect the resolution change, but sometimes our application stops working.
When we enabled debug prints in our application and reproduced this issue below was the last debug print:
Module<ti.omx> @<OmxRpc_rcmClientCreate> @line<990> msg<Before RcmClient_create>
Further when we started debugging the Framework_components we found that the application stops at a point where it calls a function called MessageQ_open. For further analysis we enabled the debug messages for syslink module. Below are the debug prints for our working and non-working case.
Please find the below log we got from the syslink module.
For the failure case we got,
MessageQ_create: Max number of queues 53
MessageQ_create: Max number of queues 53
NameServer_getLocal name [OmxRpcRcmServer_2]
NameServer_getLocal: Entry not found!
After this, it gets hang and we didn't get any print further. Can you please let us know the reason for the failure?
For normal working case the debug prints are,
MessageQ_create: Max number of queues 53
MessageQ_create: Max number of queues 53
NameServer_getLocal name [OmxRpcRcmServer_2]
NameServer_getLocal: Entry not found!
Failed to get value from remote NameServer
Failed to get value from remote NameServer
MessageQ_open ioctl queueId [0x20004]
MessageQ_create: Max number of queues 53
NameServer_getLocal name [OmxRpcRcmServer_3]
NameServer_getLocal name [OmxRpcRcmServer_OMX.TI.VPSSM3.VFCC_Cb_3_0]
MessageQ_create: Max number of queues 53
MessageQ_create: Max number of queues 53
NameServer_getLocal name [OmxRpcRcmServer_OMX.TI.VPSSM3.VFCC_Ctrl_2_92]
NameServer_getLocal: Entry not found!
Please let us know if there are any more queries or questions regarding this.
PS: We are using syslink_2_20_00_14.
Thanks,
Krunal