• State
  • Locked Locked
  • Replies 3 replies
  • Subscribers 100 subscribers
  • Views 350 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.

TDA4VM: The network inference feature is output dimension difference issue on the EVM development board versus the PC side

Cherry Zhou
Mastermind 22235 points
Part Number: TDA4VM

Hi team,

Here's an issue from the customer may need your help:

Code location: TIDL_collectLocConfHeadInfo() in tidl_detectionOutput.C. InConfDataParams-> pitch[TIDL_line_match] in function.

When using the same model to convert the test (i.e. pc side) of the code in the TIDL model, the output values of the four heads are 2304, 576, 144, 36 respectively, however, on the TDA4VM board side, the output characteristics of the four heads are 2496, 704, 192, 36. Why is this difference?

What is the difference between the results obtained after inference at the board end (i.e., the position information of the target box, the confidence level, etc.) and the PC end?

The output from the PC side is captured as follows: 

The EVM development board output is captured as follows: 

Could you help check this case? Thanks.

Best Regards,

Cherry

  • 0
    TI__Guru 56820 points

    Hi Cherry,

         Can  you tell us which version of SDK you are using?

    Regards,

    ANshu

  • 0 in reply to Anshu Jain
    Prodigy 31 points

    Hi ANshu,

    Firstly, thank you for your reply and thanks Cherry for forwarding my question to this forum.

    The SDK version I used is: ti-processor-sdk-rtos-j721e-evm-08_05_00_11, and the TIDL version is: tidl_j721e_08_05_00_16.

    Actually the indexes as [0,1,2] in inConfDataParams->pitch[{index}] are three predefined macro like:

    #define TIDL_ROI_PITCH ((uint32_t) 0)
    #define TIDL_CHANNEL_PITCH ((uint32_t) 1)
    #define TIDL_LINE_PITCH ((uint32_t) 2)

     

    Regards,

    Nan Zhang

  • 0 in reply to zhang nan
    TI__Expert 4725 points

    Hi,

    Are you seeing the difference in output? I guess you will not see the difference in actual output. These are data pitches, and it may differ in PC and H/W flow. H/w emulates some of the restriction of data placements to avoid memory read conflicts. Or it could be other reason also. On PC there is no such restriction, or there is no emulation of h/w restriction hence you might see minimum pitch values on PC side.

    regards

    Deepak Poddar