Other Parts Discussed in Thread: TVP5158
Hi,
Anyone know the difference in HW/SW architecture? 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.
Other Parts Discussed in Thread: TVP5158
Hi,
Anyone know the difference in HW/SW architecture? Thanks.
Hello,
First, I try to put the binaries from EZSDK to your DVR product and it fail to boot up as I used kernel and filesystem only. It stop in kernel and then shutdown
Second, I try to run examples like decode, decode_display...etc in EZSDK, and it fail as I run decode_display... etc. I can run very few examples like decode...
Any idea about running failed examples from EZSDK? Thanks
Hi,
DM8168 DVR hardware is different from DM8168 EVM. So the default EVM configuration of kernel would not work on DVR hardware. You should use the kernel source code provided in the DVR RDK.
The significant difference because of which many EZSDK applications would not work as in on DVR hardware is that the TVP5158 addresses for EVM are different from DVR hardware. This would result in I2C accesses not completing if you use EVM based binary application on DVR.
I would recommend using the DVR applications or modify EZSDK based on the DVR hardware details. Please look particularly at the
1. TVP5158 addresses
2. NAND specific code (like uboot)
3. DDR configuration
4. GPIO configurations
5. PMIC
Regards,
Anshuman