• State Resolved
  • Locked Locked
  • Replies 14 replies
  • Subscribers 99 subscribers
  • Views 2454 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.

DM8168 DVR RDK Link API examples

Frank Bhattacharyya
Prodigy 60 points


Hi,

I'm currently working on an UDWorks DM8168 DVR RDK Rev 0.3a. I'm using the latest DVRRDK 3.00

When starting the Link API examples and selecting a demo with display task, I receive the following error:

31332: CHAINS : CPU Revision [ES1.1] !!!
31332: CHAINS : Detected [(null)] Board !!!
31332: CHAINS : Base Board Revision [DVR] !!!
31332: CHAINS : Daughter Card Revision [DVR] !!!
Display 0: Layout: CHAINS_LAYOUT_2X2_PLUS_4CH
Display 1: Layout: CHAINS_LAYOUT_2X2_PLUS_4CH
Display 0: Layout: CHAINS_LAYOUT_2X2_PLUS_4CH


31336:!!!SLAVE CORE [VPSS-M3] DOWN!!!
SystemLink_copySlaveCoreExceptionContext:146
[m3vpss ] System_dispSetPixClk: Error -6 @ line 291
[m3vpss ] 46847: Assertion @ Line: 345 in links_m3vpss/system/system_dctrl.c: FVID2_SOK == retVal : failed !!!

The mcfw API samples do work, so I don't think this is a hardware issue. All tests are done using the unmodified RDK 3.00 sources.

I had the same problem using the 2.00.00.24 RDK. Any help/suggestions on this issue?

Thanks in advance

BR

Frank

  • 0
    TI__Expert 7765 points

    Frank,

    Sorry for this. We actaully test and support only mcfw demo applications. We may plan to discontinue support for chains appliations going ahead. That is under discusions. 

     

  • 0 in reply to Yogesh Marathe
    Prodigy 60 points

    Hi Yogesh,

    thanks for the quick answer!

    Then there's another question (I hope it's OK to ask it within the same discussion):

    Are there any McFW usecases (planned) that do swms on SD (IOUTD). I didn't find (overseen?) a usecase for that in the McFW API, so I thought I need to use the "lower" API's.

    My goal is to implement two independent SD video out channels on a DM8168 based design, both capable of swms and graphics.

  • 0 in reply to Frank Bhattacharyya
    TI__Expert 7765 points

    Frank,

    There are examples of McFW usecases using SWMS on SD for plaforms other than 816x. You can look at usecase files in dvr_rdk\mcfw\src_linux\mcfw_api\usecases\ti810x or dvr_rdk\mcfw\src_linux\mcfw_api\usecases\ti814x, SWMS could not be applied on SD for 8168 for scalar performance reasons.

  • 0 in reply to Yogesh Marathe
    Prodigy 60 points

    Hi Yogesh,

    once again thank you very much for your reply, I really appreciate it.

    Our design will feature two independent SD outputs (plain CVBS) and we would only need one additional HDMI output. Do you know if there are any scaler performance issues when using only one HDMI and two SD outputs? It would also be acceptable to reduce the display frame rate, to meet speed restrictions.

    To test with the UDWorks DVR I want to create a mcfw use case with only 1 HDMI and 1 SD but software mosaic on both. Are there any "best practices" doing so? 

    Thanks in advance

    Frank

  • 0 in reply to Frank Bhattacharyya
    TI__Expert 7765 points

    Frank,

    How many channels we are talking about here? also what are the resolutions? As far as scalars are considered in DM8168 there are 5 scalars and DEI Link, SWMS Link and Scalar Link can be configured to choose particular scalar as per data flow requirement. As far as you don't exceed the scalar capacity (16D1@30fps), there wont be any scalar performance issue.

    It will be good if you can provide a basic block diagram of what exactly you are trying to do along with number of channels and resolutions mentioned, then we can comment on feasibility of usecase on DM8168.

  • 0 in reply to Yogesh Marathe
    Expert 1240 points

    UPDATE: This question was due to some personal confusion and misunderstanding the quoted post. See Yogesh's post below for clarification.


    Yogesh,

    Can you elaborate more on what you meant by "discontinuing support" for the TI Link API?  I'm just confused because I was under the impression one MUST use the TI Link API if none of the use cases provided by the McFW API are sufficient, to either develop an application via the Link API, or to develop a sufficient use case for the McFW API.

    Yogesh Marathe said:

    Frank,

    Sorry for this. We actaully test and support only mcfw demo applications. We may plan to discontinue support for chains appliations going ahead. That is under discusions. 

  • 0 in reply to Jon S.
    TI__Expert 7765 points

    Frank,

    I said we are stopping chains application support. There are two types of demo applications in DVR RDK currently. 1. Chains 2. McFW demo I am talking about chains applications (dvr_rdk\demos\link_api_demos) and not the link API. We recomend users to use McFW APIs to write their applications. If none of the already existing usecases are sufficient, users can choose to write their own use cases using Link API. I never talked about stopping support for Link API.

  • 0 in reply to Yogesh Marathe
    Expert 1240 points

    Yogesh,


    Sorry for the confusion, and thank you for responding so quickly with clarification.

    I'm just getting up to speed with the 8127 IPNC RDK, and was confused by the terms "chains" versus "links." (As far as I can tell, I don't think those chains examples are around in the IPNC RDK)

    I have updated my post above to hopefully avoid confusing other people, and will create a new thread for further questions (will be in the 814X forum).

    Regards,

    Jon

  • 0 in reply to Yogesh Marathe
    Prodigy 60 points

    Hi Yogesh,

    the previous post was written by Jon S. not me. But never mind the information is also valuable to me.

    According to my use case, I need to capture 16D1@25/30fps and encode all streams to H264.

    The SD outputs will be fed with 4 * CIF streams composed to a quad display (D1). The HD output should be able to display a 9/16 split, but the HDMI output is not our primary focus.

    So scaler requirements would be (worst case)

    8 * D1 -> CIF (to feed two quad displays) and 16 * D1 -> <480*270> (to feed HDMI 16 split)

    But the average use case is

    8 * D1 -> CIF and then 4 * CIF via swms to 1 * D1 (for both SD paths)

    Best regards

    Frank

  • 0 in reply to Frank Bhattacharyya
    TI__Expert 7765 points

    Jos,

    Thanks for quick clarification.

  • 0 in reply to Yogesh Marathe
    TI__Expert 7765 points

    Frank,

    Sorry I addressed you in the post instead of Jos. Thanks for clear details of usecase one last question on this, do you have any channels being decoded and played back on any of display? I know you have not mentioned about decode anywhere in the post but just wanted to have idea. As of now I think you have mentioned only capture encode and display are the components you want to have. I'm trying to device a data flow based on your inputs.

  • 0 in reply to Yogesh Marathe
    Prodigy 60 points

    Hi Yogesh,

    thanks for reminding me! We're also receiving IP camera streams and we need to decode 4 * SD H264 and rescale to CIF to compose into a SD quad video display. If more streams are possible this is no problem of course.

    Best regards

    Frank

  • 0 in reply to Frank Bhattacharyya
    Prodigy 60 points

    Hi Yogesh,

    I was able to create my own mcfw use case using swms on SD output.

    Thanks for your support

    Best regards

    Frank

  • 0 in reply to Frank Bhattacharyya
    TI__Expert 7765 points

    Glad to know that. Please let us know if you face any issues.