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.

How to debug swMsLink_drv.c FVID2_create fail?

Hi,

I am trying to make a 1080 enc+dec user case. It can work with a sclr link and I can see 1080p video. But the video is fickering in 1080i@60Hz.

Then I try to replace the sclr link with a swMsLink and I get below error:

 [m3vpss ]  13577: Assertion @ Line: 2499 in links_m3vpss/swMs/swMsLink_drv.c: pDrvObj->fvidHandle != NULL : failed !!!

I check the swMsLink_drv.c and find that it is FVID2_create fail.

The same swMsLink code worked well in the decode+display user case.  So I need to know why it fails here. But the FVID2_create is implemented in ti_tools/hdvpss/ . I did not see any print from those files. Could you please help to guide me how to debug this kind of issue? Is that possible to get debug print from ti_tools/hdvpss/ ?

Thanks,

zzs

  • Driver conflict happens usually because of resource conflict.i.e You are trying to open a scaler that is already opened in another path. Attach your usecase file where you are creating and connecting links.

    Also do you want the display to show deinterlaced content or do you want the display to show 1080i60 content without deinterlacing.

  • Hi Badri,

     

    Thanks for the answer. The problem was solved by changing the parameters to swMs link.

    My problem is that I see this error but there is no detailed error print. I may have many such kind of problems during my development. If you can have a suggestion on how to debug this kind of problem. I will appreciate it.

    I want the display to show 1080i60 contect without deinterlacing. I already got a patch from you guys in last month. It makes the interlacing enc+dec working. According to your answer, TI will release a new version to fully support interlacing enc+dec+display soon. Do you have a due date for the new release?

     

    Thanks,

    zzs

  • To debug M3 side issues it is best to have CCS+JTAG connected to target .You can then single step and identify the source of any errors.

    The next RDK release is due end of the month. The next RDK release will support deinterlacing in SwMs and is not useful to you as you want to display fields without deinterlacing.

    What is your current data flow. i.e what are the link connections ? RDK 4.0 should be able to display interlaced content in 1080i60 configuration.What is the issue you are seeing