cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
Highlighted
358 Views
Registered: ‎05-29-2019

v_hdmirx vs v_hdmirx1, v_hdmirxss vs v_hdmirxss1, vphy vs v_hdmiphy1

Hello,

We're going to switch SDK and Vivado from 2018 to 2020 very soon.

The project is running and very close to release.

I'm wondering if switching to 2020 IPs for hdmi_rx_ss and vphy will require drivers upgrades in software.

Actually drivers with suffix _1 are quite different from the current ones we're using.

Please advice asap.

 

Best Regards.

Boris Barak.

Tags (2)
0 Kudos
5 Replies
Highlighted
Moderator
Moderator
295 Views
Registered: ‎10-04-2017

Hi boris.barak@vitec.com,

 

Because the use case may be different for each project it is up to the user to figure out the impact to their design when upgrading. However, Xilinx provides collateral to make this process easier.

 

The procedure for updating and finding the scope of the work is to:

  1.  Check the changelogs in between the version you are switching from/to and see if there is any HW changes that will require modification to your HW design.
    1. Keep in mind versioning. If there are no version changes, then there may be no work needed on your side. 
  2.  Check the driver updates using the GIT repository to see if there is anything that will need to be updated. Here you can see check-in comments(history) and diff the changes to the files between tagged versions.
    1. Here is v_hdmirx1 for example: https://github.com/Xilinx/embeddedsw/tree/master/XilinxProcessorIPLib/drivers/v_hdmirx1

 

 

samk_0-1598138687748.png

 
 

2020-08-22 17_33_40-AR# 54546_ HDMI 1.4_2.0 Receiver (RX) Subsystem - Release Notes and Known Issues.png

 

Don't forget to reply, kudo, and accept as solution.

Xilinx Video Design Hub
Highlighted
235 Views
Registered: ‎05-29-2019

HI,

As could be seen for HDMI 1.4/2.0 Receiver (RX) Subsystem only revision has been changed:

2018.3-v3.1 (Rev 1)  => 2020.1-v3.1 (Rev 4).

According to Vivado IP Versioning - User action can be "No need to react" in this case.

This is including all sub-core stuff, like HDCP.

The same one is effective for Video PHY Controller:

2018.3-v2.2 (Rev 2)  => 2020.1-v2.2 (Rev 5).

So actually the migration from Vivado 2018.3 to 2020.1 is supposed to be transparent for above IPs.

Please confirm.

Best Regards.

Boris Barak.

 

0 Kudos
Highlighted
Moderator
Moderator
228 Views
Registered: ‎10-04-2017

Hi boris.barak@vitec.com,

Correct, from the physical IP standpoint, it should be transparent.
Next, please take a quick look at the drivers to make sure there were no API updates that would impact you.

Based on the HW being transparent, I would expect the API to be as well, but I would check to see if there were any bug fixes that updated the API interface.

The quickest way is to diff the top-level c code for the driver between versions. If there are no changes to the top-level functions (API) the upgrade should then require no updates from the user application.

-Sam

Don't forget to reply, kudo, and accept as solution.

Xilinx Video Design Hub
0 Kudos
Highlighted
192 Views
Registered: ‎05-29-2019

Hello Sam,

Thank you for your responses.

I'm comparing v_hdmirx/v_hdmirx1, v_hdmirxss/v_hdmirxss1 and vphy/v_hdmiphy1.

There are lot of code changes, except of functions API indexing (like XV_HdmiRx_IntrHandler vs. XV_HdmiRx1_IntrHandler).

Can you tell us if _xxxx1 drivers are more advanced versions and should be used in the long term of the project ?

Otherwise could we hold to the last versions of _xxxx drivers ? 

Best Regards.

Boris Barak.

0 Kudos
Highlighted
Moderator
Moderator
131 Views
Registered: ‎10-04-2017

Hi boris.barak@vitec.com,

 

The _XXXX1 drivers are for the HDMI 2.1 SubSystem and I do not believe they are backward compatible as the HDMI 2.1 standard is much different from HDMI 2.0.

Please continue to use _XXXX

 

On another note, each driver version is only tested and supported with its related HW IP equivalent.

EX. 2019.2 Vivado IP is intended to only be used with the 2019.2 SW release.

samk_0-1599061647842.png

 

Thanks,

Sam

 

 

 

 

Don't forget to reply, kudo, and accept as solution.

Xilinx Video Design Hub
0 Kudos