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.

DM816x McFW

Other Parts Discussed in Thread: TVP5158

Hi All,

Currently I am having hardware from udworks on dm816x, the DVR RDK version that I use is 01.06.00.11. I would like to know:

1. From this forum, some people is using RDK version 01.09.00.16, I would like to know if my hardware can also support this version? If yes, where can I get this version for evaluation.

2. Please advise where I can get more information/documentation about McFW framework and maybe some example that I can test on my udworks hardware.

Thank you very much.

Best regards,

Cheng

  • tkCheng said:

    1. From this forum, some people is using RDK version 01.09.00.16, I would like to know if my hardware can also support this version? If yes, where can I get this version for evaluation.

    Yes, we have made a release of the framework and UART based application with version 01.09.00.16. This is available on TI's myRegisteredSoftware. I assume you are getting releases from UDWorks, so you might not have access to TI's myRegisteredSoftware website. But meanwhile, you can contact your local TI FAE to get you ver 01.09.00.16. BTW, who is your local TI contact?

    tkCheng said:

    2. Please advise where I can get more information/documentation about McFW framework and maybe some example that I can test on my udworks hardware.

     Yes, all releases that TI or UDWorks do can work well on the hardware that you have got. We have updated the documentation in newer releases. Let us know if there is ay specific usecase you want to implement.

    Regards,

    Anshuman

    PS: Please mark this post as verified, if you think it has answered your question. Thanks.

  • Hi,

    We are going through Avnet for TI product.

    Is there any way I can get the 01.09.00.16 from myRegisteredSoftware website instead of going through Avnet, so that I can cut short the time and start working on it.

    In addition to that, I would like to know if the following is possible and roughly which section of the McFW has to be changes?

    1. Reduce 16 ch to 8 ch, thus reduce supported TVP5158 from 4 unit to 2 unit

    2. Support IP camera stream in. (This is possible in old omx framework, but in McFW - 01.06.00.11, I do not see any similar example/code)

    3. Support IP camera stream out. (This is available in old omx framework, but not in McFW 01.06.00.11)

    4. Live view from 4 analog input, mosaic into one and streaming out

    5. OSD overlay on video input (either from analog input or IP camera input)

    6. Perform a snapshot of live view

    Thank you very much.

    Best regards,

    Cheng

  • Cheng,

    Please find my response below.

    1. Reduce 16 ch to 8 ch, thus reduce supported TVP5158 from 4 unit to 2 unit

    [Yogesh] This change can be done with a change demo application, You can restrict num channels  to 8 by setting numChn for Vcap. You have ensure you set numChn for other modules in the system as well (VENC, VDEC and VDIS as per usecase). For VCAP it can be se as followed.

    Vcap_params_init(&vcapParams); vcapParams.numChn =8; Vcap_init(&vcapParams);

    2. Support IP camera stream in. (This is possible in old omx framework, but in McFW - 01.06.00.11, I do not see any similar example/code)

    [Yogesh] This is currently not supported but all required internal componets to support this use case are present. You can look at VDEC-VDIS demo which actually reads from encoded bitstream file system and sends it to decoder and then to display. We just need an A8 side application that can receive data from ip camera and send it to ipcBitsOut Link which intern give this to decoder. 

    3. Support IP camera stream out. (This is available in old omx framework, but not in McFW 01.06.00.11)

    [Yogesh] This is not supported

    4. Live view from 4 analog input, mosaic into one and streaming out

    [Yogesh] Do you want to stream out from A8 or display?

    5. OSD overlay on video input (either from analog input or IP camera input)

    [Yogesh] OSD is supported for analog input

    6. Perform a snapshot of live view

    [Yogesh] Not sure will get back to you

    Regards,

    Yogesh.

  • 1. Reduce 16 ch to 8 ch, thus reduce supported TVP5158 from 4 unit to 2 unit

    - Even if we reduce the physical TVP5158 chip from 4unit to 2 unit, we only require to restrict the num channels under McFW? No other software change is require to cater for this hardware changes?

    3. Support IP camera stream out. (This is available in old omx framework, but not in McFW 01.06.00.11)

    - What I really mean here is stream out the capture video(either from analog input/IP camera), I can see new version have this features implemented in CIF.

    4. Live view from 4 analog input, mosaic into one and streaming out

    - I require it to streaming out the final video from A8.

    5. Can I overlay OSD on the stream out video? Before the mosaic (in item 4)


    To better explain my use case, please refer to attached image file below: (all the show ch require D1 resolution)

    Thank you very much.

    Best regards,

    Cheng


  • Any helps on this?

    Thank you very much.

    Best regards,

    Cheng

  • Cheng,

    Essentially you need 16 Dec + 8 Enc right?  Feasibility of usecase diagram you have drawn above is also dependent on resolution of  each encode decode channel. What is the resolution for each input path above (IP camera, Analog camera and Sata read)?

    Do you need the detailed dataflow for this usecase?

    Regards,

    Yogesh.

     

     

     

  • Hi Yogesh,

    Yes, I will need 16Dec + 8 Enc. The resolution for all the pipeline would be in D1.

    Yes, a detailed dataflow for this usecase would be very much appreciated.

    Thank you very much.

    Best regards,

    Cheng