Connect Orange Pi Plus to DVI monitor using HDMI port

matteobp

So far we cannot connect the Orange Pi Plus board to a DVI monitor using the HDMI port because it doesn't work. Is it a hardware problem, and in this case it will never work, or is it a software problem that can be solved in the future?

gaara

Same issue here, with a A20 SoC. HDMI/DVI adapter doesn't work.
This problem affects also BPi, so it's an old problem...

Dmi3X3

The adapter doesn't work because the DVI monitors not always support HDCP. It is necessary or use an adapter V1.4 HDMI to HDMI Converter Extractor Splitter SPDIF R/L+Video Audio out,HDCP Remover, US & EU Plug Adapter., at cost equal OPi2 or to disconnect HDCP in system.fex, but I didn't find mentions of HDCP there.

magicse

Dmi3X3 replied at 2015-8-21 09:45
The adapter doesn't work because the DVI monitors not always support HDCP. It is necessary or use an ...

What abou Hdmi_hal_hdcp_enable=0 option ?

larson9999

magicse replied at 2015-9-25 13:14
What abou Hdmi_hal_hdcp_enable=0 option ?

magicse,
How do you apply this? "What abou Hdmi_hal_hdcp_enable=0 option ?"

melanrz

Working only hdmi2vga

Riconec

Have the same problem with my O Pi PC
Will try another image and edit .fex

Laokoon

You can modify script.bin using sunxi-tools and add proper parameters for HDMI - DVI mode in [disp_init] section.
I've changed it basing on http://sunxi.org/Fex_Guide and was able to change resolution to any supported by OrangePi, not only 1080p and 720p.

matteobp

Can you post an example for using 1280x1024 or 1024x768?

Thanks in advance.

tokka

I see lot of peoples changing the script.bin to change resolution, but imho it has not much sense. Why don't you simply use uEnv.txt? you can change resolution using the fex parameters or a custom resolution if supported).
The script.bin parameters are passed to the kernel as first, and if there are no changes, they are used; but if you pass other parameters to the the kernel by uEnv, the last are used (so that in the uEnv file).
Manage the script.bin is good to set the defaults output, ex. disp0 -> hdmi and disp1 -> vga or composite.
Using uEnv seems give some problem only for changes in disp1, but i have not tested a lot.
Two simple exemples:

1) disp0 hdmi at 1280x720p60 (with autodectecion, if supported by the monitor) and disp1 vga at 1024x768

1. bootargs=disp.screen0_output_type=3 disp.screen0_output_mode=EDID:5 disp.screen1_output_type=4 disp.screen1_output_mode=1024x768

Copy code

2) disp0 vga@800x600 disp1 hdmi@1920x1080 without autodetection

1. bootargs=disp.screen0_output_type=4 disp.screen0_output_mode=800x600 disp.screen1_output_type=3 disp.screen1_output_mode=1920x1080p60

Copy code

In this way you can change resolution semply editing the script (from windows too, but better if don't use the default win blocknotes but another editor such notepad++) and rebooting the OP, without modding all times the script.bin

I haven't tested if it work with disp_mode too, to set single output, dualhead, xinerama, etc...in this case you have to mod the script.bin, but not for change resolution.

Below an extract of my uEnv.txt taken from fex guide for a fast resolution change.
Cheers

# disp.screen0_output_type=
# 0         none
# 1         lcd
# 2         tv
# 3         hdmi
# 4         vga

# disp.screen0_output_mode=
# 0         480i         1680*1050
# 1         576i         1440*900
# 2         480p         1360*768
# 3         576p         1280*1024
# 4         720p50         1024*768
# 5         720p60         800*600
# 6         1080i50         640*480
# 7         1080i60        
# 8         1080p24        
# 9         1080p50        
# 10         1080p60         1920*1080
# 11         pal         1280*720
# 14         ntsc