TDA4VM: sending object descriptor failed with various other errors

Hafiz Muhammad Owais

Part Number: TDA4VM

Hi TI experts,

I have recently defined a custom kernel in c66 and host following the method used by TI itself. The node is called in the pre_proc_module of AVP project. At first, the custom defined node is tested on the host emulation mode of J7 and it worked perfectly fine. Now I am trying to make it work on the TDA4 and it is giving me following errors:

0.512545 s: VX_ZONE_ERROR:[ownContextSendCmd:550] sending object descriptor failed
0.512572 s: VX_ZONE_ERROR:[ownNodeKernelInit:460] Target kernel, TIVX_CMD_NODE_CREATE failed
0.512711 s: VX_ZONE_ERROR:[ownGraphNodeKernelInit:559] kernel init for node 7, kernel com.ti.img_proc.test ... failed !!!
0.512720 s: VX_ZONE_ERROR:[vxVerifyGraph:1967] Node kernel init failed
0.512725 s: VX_ZONE_ERROR:[vxVerifyGraph:2021] Graph verify failed
0.515880 s: VX_ZONE_ERROR:[tivxNodeSendCommand:248] tivxNodeSendCommand: Node Kernel Not Valid

Can you help figure out why I am having this error during board implementation and didn't meet the same problem in host mode. Thank you.

over 6 years ago

0 Jesse Villarreal over 6 years ago

TI__Expert 5655 points

Do any of the following posts lead you to the answer:

1. https://e2e.ti.com/support/processors/f/791/t/856409?-TDA4-Facing-Issue-while-creating-graph-with-custom-kernel

2. https://e2e.ti.com/support/processors/f/791/t/882592?tisearch=e2e-sitesearch&keymatch=faq%3Atrue

3. https://e2e.ti.com/support/processors/f/791/t/882591?tisearch=e2e-sitesearch&keymatch=tagkeyword%253A%2522jacinto%25207%2522%2520AND%2520tagkeyword%253Aopenvx%2520faq%253Atrue

It appears that the kernel is not known or registered on the remote core. On PC there is no remote core, so it knows about it, but the registration also needs to happen on the remote core for EVM.

Regards,

Jesse

0 Lucas Weaver over 6 years ago

TI__Genius 13875 points

Hello,

It appears that you are using the PSDKRA 6.1 release based on your logs, is this correct? In the latest PSDKRA 6.2, we have improved the logging for such errors. Could you please take a look at the following two FAQ's to see if these two things are being done correctly?

1. The below FAQ explains how to ensure that your kernel module is registered appropriately on the target core. The logs are different because of the new release, but the answer will still apply

https://e2e.ti.com/support/processors/f/791/t/882591?tisearch=e2e-sitesearch&keymatch=tagkeyword%253A%2522jacinto%25207%2522%2520AND%2520tagkeyword%253Aopenvx%2520faq%253Atrue

2. Could you also check the below FAQ? This explains that there could be errors inside the create callback of your new kernel that aren't exposed in the PC version (for example, you could be out of memory on the target).

https://e2e.ti.com/support/processors/f/791/t/882592?tisearch=e2e-sitesearch&keymatch=tagkeyword%3A%22jacinto%207%22%20AND%20tagkeyword%3Aopenvx%20faq%3Atrue

Regards,

Lucas

Processors

Processors forum

TDA4VM: sending object descriptor failed with various other errors