I used RDK V4.0.0.3 on DM8168 before, now I migrate to DM8165. How to modify to suport DM8165? Thanks.
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.
I used RDK V4.0.0.3 on DM8168 before, now I migrate to DM8165. How to modify to suport DM8165? Thanks.
Hi Colin,
DM8168 and DM8165 are fully software and pin compatible devices. We have common EZSDK for all DM816x devices, thus I expect the same is valid for DVR RDK.
See also the below e2e thread:
http://e2e.ti.com/support/dsp/davinci_digital_media_processors/f/717/t/351872.aspx
Regards,
Pavel
the difference is the quantity of HDVICPs.
Just make sure the encode/decode performance doesnt exceed the DM8165's performance.
BR,
Eason
Hi Colin,
Below changes needs to be done in RDK to support DM8165.
1)dvr_rdk/mcfw/interfaces/common_def/ti_vsys_common_def.h
-- #define VSYS_MAX_NUMHDVICP (3)
++ #define VSYS_MAX_NUMHDVICP (2)
2)dvr_rdk/mcfw/src_bios6/links_m3video/codec_utils/utils_encdec.h
-- #define NUM_HDVICP_RESOURCES (3)
++ #define NUM_HDVICP_RESOURCES (2)
3)dvr_rdk/mcfw/src_bios6/links_m3video/codec_utils/utils_encdec_prf.h
-- #define UTILS_ENCDEC_MAXNUMOFHDVICP2_RESOUCES (3)
++ #define UTILS_ENCDEC_MAXNUMOFHDVICP2_RESOUCES (2)
4)dvr_rdk/mcfw/src_bios6/links_m3video/codec_utils/src/hdvicp2_soc_config.h
-- #define HDVICP_NUM_RESOURCES (3)
++ #define HDVICP_NUM_RESOURCES (2)
5)dvr_rdk/mcfw/src_bios6/links_m3video/codec_utils/src/iresman_hdvicp2_fwif.c
comment the definition of IRESMAN_HDVICP2_ISR2() api.
6)dvr_rdk/mcfw/src_bios6/links_m3video/codec_utils/src/utils_encdec.c
channel allocation should be change i.e make sure no channel should map to IVAHD3.
7) make sure no channel should map to IVAHD3 in all the use-case files available in /dvr_rdk/mcfw/src_linux/mcfw_api/usecases/.
Thanks&Regards,
Veeranna