• State
  • Locked Locked
  • Replies 4 replies
  • Subscribers 99 subscribers
  • Views 232 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.

Original question:

TDA4VM: TDA4VM:VISS

TDA4VM: Custom ISP Implementation Application Stuck

Sithara Tresa Chacko
Expert 1120 points
Part Number: TDA4VM

Tool/software:

Hi TI 

I'm working on processor SDK 07_01_00_11 for a custom application with app_viss as  a reference.

My application has two custom Tiovx/kernelj7/HWA cores which performs the ISP functionality.

I have observed that the application gets stuck in verify graph in the function ownGraphNodeKernelInit.

I have shared a rough flow of the app in the attched file for ur reference.

Please guide what could be the reason of this application stuck in ownGraphNodeKernelInit .

/cfs-file/__key/communityserver-discussions-components-files/791/viss_5F00_query.txt

Thanks &Regards

Sithara Tresa Chacko

  • 0
    TI__Mastermind 38540 points

    Hi,

    The expert is on leave currently. Please expect a response by next week.

    Regards,
    Tanmay

  • 0 in reply to Tanmay Patil
    TI__Guru* 84746 points

    Hi Sithara,

    I see that you have a custom target CUSTOM_NODE_TARGET used for the node. Have this been integrated correctly?

    Typically in the ownGraphNodeKernelInit() the initialize and create callback of the nodes are called. 

    So you would have to check if the create callback for both your nodes are called.

    Regards,

    Nikhil

  • 0 in reply to Nikhil Dasan
    Expert 1120 points

    Hi Nikhil

    Thank you for the reply. 

    I  have observed that when I changed the task priority to 8 and 9 instead of 

    tivxPlatformCreateTargetId((vx_enum)TIVX_TARGET_ID_VPAC_CUSTOM_VISS, 23, "TIVX_CUSTOM_VISS", 9u);
    tivxPlatformCreateTargetId((vx_enum)TIVX_TARGET_ID_VPAC_CUSTOM_NODE, 0, "TIVX_CUSTOM_NODE", 8u);

    in psdk /tiovx/source/platform/psdk_j7/bios/tivx_target_config_mcu2_0.c ,the verify graph stuck issue was resolved .

    The rest of the code executed even though there were kernel registration issues. I have attached the logs for your reference.

    /cfs-file/__key/communityserver-discussions-components-files/791/query_5F00_reply.txt

    What could be the issue with the priority num?

    I have added the Code changes to integrate the hwa target in below steps:
    1.typedef enum _tivx_target)id_e and mapping of target names with Target id in TIVX_TARGET_INFO (tivx_platform_psdkj7.h)
    2.TIVX_PLATFORM_MAX TARGET increased.
    3.Created Target IDs IN tivxPlatformCreateTargets in (bios/tivx_target_config_mcu2_0.c)

    Kindly guide how to resolve the  issue.

    Thanks &Regards

    Sithara Tresa Chacko

  • 0 in reply to Sithara Tresa Chacko
    TI__Guru* 84746 points

    Hi,

    Sithara Tresa Chacko said:
    tivxPlatformCreateTargetId((vx_enum)TIVX_TARGET_ID_VPAC_CUSTOM_VISS, 23, "TIVX_CUSTOM_VISS", 9u);
    tivxPlatformCreateTargetId((vx_enum)TIVX_TARGET_ID_VPAC_CUSTOM_NODE, 0, "TIVX_CUSTOM_NODE", 8u);

    Could you let me know if these are the 2 new targets on the MCU2_0 core itself?

    If yes, then they are nothing but 2 tasks and since TIVX_CUSTOM_VISS has a higher priority, this task would always interrupt the second target when executed.

    Is that your usecase?

    Regards,

    Nikhil