Why does the Video Subsystem fail to configure when using a custom resolution?
When using the example in (Xilinx Answer 68227) to register a custom resolution I see that the VPSS Software Driver fails in the XVprocSs_SetSubsystemConfig function call with a return value of XST_FAILURE.
This is a known issue in the Video Processing Subsystem Software Driver that is fixed in the Video Processing Subsystem Software Driver in the Vivado SDK 2017.1 release.
The problem is that the resolution validation function called inside the XVprocSs_SetSubsystemConfig was only checking to see if the input and output resolutions were listed in the default timing tables in the Video Common library.
When a custom resolution was used, its ID would fall outside of the search range and the function would return XST_FAILURE.