Part Number: TDA4VM
Hi,TI
After resolving the issue of HDMI display last time, I found that the current display kernel cannot switch channels properly.
Is this a version issue?
Regards,
Damon
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.
Part Number: TDA4VM
Hi,TI
After resolving the issue of HDMI display last time, I found that the current display kernel cannot switch channels properly.
Is this a version issue?
Regards,
Damon
Hi Damon,
Sorry, which switch functionality do you mean here? can you please elaborate?
Regards,
Brijesh
Hi Brijesh,
Thanks for your pormpt reply. I use tivxNodeSendCommand to send CMD 'TIVX_DISPLAY_SELECT_CHANNEL' to display node.
The app was blocked after the first CMD was sent.
Regards,
Damon
Hi Damon,
Do you mean this control command is blocked or the usecase is blocked after it completes the control command?
I dont see any change in this control command's implementation. So it should as it is work fine.
Please confirm that you are sending image from an object array to the display node.
Regards,
Brijesh
Hi Damon,
Sorry for the delay. It is blocked after the first successful channel switch.
I checked that using the same app demo on SDK8.5, it can switch channels normally.
On SDK9.1, the HDMI port was initially unable to display. Then I added a patch to resolve this issue. Will the issue of switching channels be related to this?
Could you please do a test on your side to verify this?
Regards,
Damon.
Hi Damon,
I think Brijesh may have some more context, but I assume the patch you are referring to is the patch from this thread: https://e2e.ti.com/support/processors-group/processors/f/processors-forum/1311552/tda4vm-sdk-9-0-patch-for-edp-to-hdmi-bug/5035861#5035861.
One suspicion I have is that the patch is removing some timeouts, so maybe these are blocking. For example, like below:
- while ((i < messageSize) && (i < 1024U) && (timeout != 0U))
+ while (i < messageSize)
Might be a insightful experiment to see if you can add some debug logs to see if we are stuck in one of the while loops that were modified.
Regards,
Takuma
Hi Damon, Takuma,
Do we still see usecase running after switching the channels? is the display freeze'd?
I am suspecting that R5F is stuck somewhere and is not responding.
Regards,
Brijesh