• State
  • Locked Locked
  • Replies 2 replies
  • Subscribers 99 subscribers
  • Views 124 views
  • Users 0 members are here
Support feedback
Options
Options
Related

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.

AM69A: Problem Accessing Multiple Inputs in TIDL Custom Operator Implementation

Mahmoud Hamed
Prodigy 30 points
Part Number: AM69A

Tool/software:

I'm working on implementing a custom operator that takes two inputs, where I'm using the Maxpool custom operator example as a reference which is located at:

/ti-processor-sdk-rtos-j784s4-evm-10_01_00_04/c7x-mma-tidl/ti_dl/custom/

I'm encountering an issue within the function:

TIDL_custom[MyCustomOp]_ixX_oxX_exec(void *kernelHandle, const TIDL_bufParams3D_t *srcAddr, const TIDL_bufParams3D_t *dstAddr, const void *srcPtr[], void *dstPtr)

When attempting to access input data from srcPtr, I consistently observe that srcPtr[0] contains data from the second input, while srcPtr[1] contains all zeros—effectively meaning only the second input is accessible.

It seems this issue might originate from the call to:

TIDL_DataflowProcess(void *tidlHandle, void *inPtrs[], void *outPtr[])
Although both inputs are supposed to be passed in through this function, only one appears correctly when accessed in the DSP execution function.

Could this be a bug, or is it possibly due to the current implementation only supporting TIDL_DataFlowTypeOneTensorInProcOneChannel? If so, what would be the correct way to handle multiple inputs in this case?