STICKY: HOWTO: Create Custom HDMI modes

[boehm]

thank you dom.

I created a repository regarding this hoping this is what you meant
Here's the link

https://github.com/boehmiboy/RPi-Square-Resolutions.git

[tzj]

https://github.com/Hexxeh/rpi-firmware

He may have meant that you post an issue here?

[boehm]

Yes You are right. I am totally new to github. I posted an issue there. Thank you

[axius]

Hello, could anyone give me a little advice or hint on how to proceed further ?

I have a LCD display salvaged from a broken laptop (CLAA102NA0ACW) and have got a VGA LVDS controller (R.RM3251 for CLAA102NA0ACW). I'm trying to use the PiView to connect the VGA controller to the Pi and have been having little success.

The only way I get an image is when I use "hdmi_safe=1" with the following settings

Code: Select all

hdmi_cvt=1024 600 60 3 0 0 0

# uncomment to force a specific HDMI mode (this will force VGA)
hdmi_group=2
hdmi_mode=87

The problem with this is that it goes to 640x480. When I remove hdmi_safe, all I get is a whit bottom line that blinks from time to time.

Any ideas of what to try ?

Any help is greatly appreciated, thank you.
Stefan

[dom]

hdmi_safe will override your custom setting.

CVT modes are not compulsory - my guess is your monitor doesn't support CVT timing.
You can explicitly set all the timing parameters (with hdmi_timings), but you will need a datasheet for the LCD to determine what the timings are it requires.

[Mortar Art]

Hi Dom,

from the sounds of it, you're the person to ask about my issue. I've been trying to connect my Rift DK2 to the Pi B+ for a few days now, and have tried almost every possible combination in config.txt.

The DK2 is 1080x1920. It's not a rotated 1080p display. It's natively in portrait. Is there any way to get a 9x16 aspect ratio thrown in to the mix for the sake of people trying to use Oculus devices?

[dom]

from the sounds of it, you're the person to ask about my issue. I've been trying to connect my Rift DK2 to the Pi B+ for a few days now, and have tried almost every possible combination in config.txt.

The DK2 is 1080x1920. It's not a rotated 1080p display. It's natively in portrait. Is there any way to get a 9x16 aspect ratio thrown in to the mix for the sake of people trying to use Oculus devices?

Are you saying you can get an image (e.g. using CVT settings)? If so what problem are you seeing?
I assume the pixels are square?

[Mortar Art]

Hi Dom. I'm not getting an image. The Rift seems to have 3 status indicators on it's LED:

Orange; standby
Orange/blue; Incorrect mode
Blue; on

On is accompanied by the screen being active.

If I leave the Pi's settings alone, and either hotplug or boot with the Rift plugged in, I get Orange/Blue. If I set all manner of settings in config.txt and again via tvservice, I get Orange, if the settings are close to the Rift's needs.

Does the Pi support native portrait, or only rotated aspect ratios? Your earlier posts here seem to indicate that it supports 16:9, but not 9:16.

[Torben]

latest "next" firmware has some changes to custom hdmi modes.

CVT now uses a single config string to set up. (First post edited)

You can also play with the raw hdmi timings:

The hdmi_timings parameters are:

Code: Select all

hdmi_timings=<h_active_pixels> <h_sync_polarity <h_front_porch> <h_sync_pulse> <h_back_porch> <v_active_lines> <v_sync_polarity> <v_front_porch> <v_sync_pulse> <v_back_porch> <v_sync_offset_a> <v_sync_offset_b> <pixel_rep> <frame_rate> <interlaced> <pixel_freq> <aspect_ratio>

You wil obviously need a timing data sheet for the display, and quite possibly a scope to debug what is happening, but it may allow non-standard displays to be driven.

The aspect ratio is:

Code: Select all

HDMI_ASPECT_4_3 = 1
HDMI_ASPECT_14_9 = 2
HDMI_ASPECT_16_9 = 3
HDMI_ASPECT_5_4 = 4
HDMI_ASPECT_16_10 = 5
HDMI_ASPECT_15_9 = 6
HDMI_ASPECT_21_9 = 7
HDMI_ASPECT_64_27 = 8

It will appear as the last hdmi_mode (87 for DMT, 65 for CEA). Use hdmi_group to determine CEA or DMT.

This was my test, for VGA@75

Code: Select all

hdmi_group=2
hdmi_mode=87
hdmi_timings=640 0 16 64 120 480 0 1 3 16 0 0 0 75 0 31500000 1

[edit: use hdmi_timings rather than hdmi_timing]

I was trying to use hdmi_timings do run an DVI-2-LVDS-Converter. Unfortunately I did not work as aspected...

So if got some questions:
- Does hdmi_timings meet the CVT-Standard from VESA? Particulary the Sync-Polarity? If I got right from the VESA standard the sync polarity for normal CRT are HSync - Negative and VSync - Positive. Is this the same for hdmi_timings?

- What does the parameter "pixel_rep" mean?

Thank you!

[andrewsi]

The "standard" sync polarities can differ from mode to mode, you have to look at the relevant standard VESA timing sheet. Not entirely clear from the post, but I'm guessing "0" is negative, 1 for "positive." As for pixel_rep: In effect, I think this is telling the display controller whether each pixel needs to be sent twice. The reason for this is that audio in HDMI is sent in-between frames of video and how much audio can be squeezed in is dependent on the pixel clock. As there are some lower resolution modes in HDMI (e.g. 640x480 interlaced like old SDTV), there wouldn't be enough available bandwidth to fit some of the higher-bandwidth compressed audio modes into the stream (e.g. AC3, DTS), so the HDMI spec defines some modes where the pixel clock runs twice as fast, but where each pixel is sent twice, resulting in the same effective video resolution but then the clock runs fast enough to jam the audio in there.

Regards,
Andy

[Thomason]

Hi there,

has anyone got a 3440x1440 display working?
I've got a new LG UltraWide 34UM95 21:9 display and try to get the native resolution 3440x1440 to work with my new PI 2 running openelec 5.x.

EDID sems to work except the desired mode is not recognized:

Code: Select all

HDMI:EDID failed to find a matching detail format for 3440x1440p hfp:48 hs:32 hbp:80 vfp:3 vs:10 vbp:21 pixel clock:265 MHz
HDMI:EDID calculated refresh rate is 50 Hz
HDMI:EDID guessing the format to be 3440x1440p @50 Hz
HDMI:EDID found unknown detail timing format: 3440x1440p hfp:48 hs:32 hbp:80 vfp:3 vs:10 vbp:21 pixel clock:265 MHz

I've tried different settings for hdmi_timings and hdmi_cvt without success. EG:

Code: Select all

hdmi_group=2
hdmi_mode=87
#hdmi_cvt=3440 1440 50 7 0 0 1
hdmi_timings=3440 1 48 32 80 1440 0 3 10 21 0 0 0 50 0 265250000 7

tvservice -m DMT doesn't display the mode and tvservice -s reports 1920x1080 (I guess selected by KODI out of the available DMT modes).

Code: Select all

tvservice -m DMT
Group DMT has 9 modes:
           mode 4: 640x480 @ 60Hz 4:3, clock:25MHz progressive 
           mode 9: 800x600 @ 60Hz 4:3, clock:40MHz progressive 
           mode 16: 1024x768 @ 60Hz 4:3, clock:65MHz progressive 
           mode 28: 1280x800 @ 60Hz 16:10, clock:83MHz progressive 
           mode 35: 1280x1024 @ 60Hz 5:4, clock:108MHz progressive 
           mode 58: 1680x1050 @ 60Hz 16:10, clock:146MHz progressive 
           mode 82: 1920x1080 @ 60Hz 16:9, clock:148MHz progressive 
           mode 83: 1600x900 @ 60Hz 16:9, clock:108MHz progressive 
           mode 85: 1280x720 @ 60Hz 16:9, clock:74MHz progressive 
pi:~ # tvservice -s
state 0x12001a [HDMI DMT (82) RGB full 16:9], 1920x1080 @ 60.00Hz, progressive

Any suggestions? Is the GPU able to handle such high resolutions at all?

Regards,
Thomas

[dom]

I've got a new LG UltraWide 34UM95 21:9 display and try to get the native resolution 3440x1440 to work with my new PI 2 running openelec 5.x.

It's not showing up because the pixel clock is too high. Add this:

Code: Select all

hdmi_pixel_freq_limit=300000000

and it will probably show up, but I suspect that it is way too high to be usable.
1920x1200@60 is the most we officially support.

You should probably read this thread for ideas.

But realistically the higher resolutions are only likely to be usable for X/framebuffer uses.
The hardware blocks (H.264, 3D, ISP) are just not designed for more than 1080p.

[Thomason]

It's not showing up because the pixel clock is too high. Add this:

Code: Select all

hdmi_pixel_freq_limit=300000000

and it will probably show up, but I suspect that it is way too high to be usable.
1920x1200@60 is the most we officially support.

will try this when back from work. In the ends more about the aspect ratio 21:9 as 16:9 movies look pretty distorted.
If I can't get it working, I will probably look for a resolution close to 1080p but closer to 21:9.

Thanks,
Thomas

[Thomason]

It's not showing up because the pixel clock is too high. Add this:

Code: Select all

hdmi_pixel_freq_limit=300000000

If tried the 3440x1440 with the higher hdmi_pixel_freq_limit as well as hvs_priority set to 0x32ff -> without success.
tvservice -m DMT and tvservice -s are displaying the mode as expected but the kodi screen stays black without reporting any errors in the logs.

Anyhow, if read from my displays edid data that there it also supports 2560x1080, which is also 21:9 (very close to). That one works out of the box and I don't see any performance issues...

To be complete my config.txt looks something like this:

Code: Select all

hdmi_cvt=2560 1080 60 7 0 0 1
hdmi_group=2
hdmi_mode=87
hdmi_pixel_freq_limit=400000000
hvs_priority=0x32ff

Thanks for your support
Thomas

[dom]

Anyhow, if read from my displays edid data that there it also supports 2560x1080, which is also 21:9 (very close to). That one works out of the box and I don't see any performance issues...

Good to hear. Are you using this resolution with OpenELEC without issues?

[Thomason]

Anyhow, if read from my displays edid data that there it also supports 2560x1080, which is also 21:9 (very close to). That one works out of the box and I don't see any performance issues...

Good to hear. Are you using this resolution with OpenELEC without issues?

Seems so, tvservice reports the correct resolution and KODI offers that resolution in the video settings.
If quickly tested some 1080p videos and didn't see any tethering or frame drops.
Youtube with 720p is running for over an hour now.

Seems to be perfectly fine.

BTW I'm using OpenELEC 5.0.5 and KODI 14.2beta.

Regards,
Thomas

[Hugh]

...
Anyhow, if read from my displays edid data that there it also supports 2560x1080, which is also 21:9 (very close to). That one works out of the box and I don't see any performance issues...

To be complete my config.txt looks something like this:

Code: Select all

hdmi_cvt=2560 1080 60 7 0 0 1
hdmi_group=2
hdmi_mode=87
hdmi_pixel_freq_limit=400000000
hvs_priority=0x32ff

I'm jealous

I have an LG 25UM55 with a native 2560x1080 (4^3 : 3^3 aspect ratio, clearly an advance over 4:3 and 4^2 : 3^2). I'm running raspbian with the latest updates, including firmware, on a Pi B2.

I have only been able to get it up to 2160x1080. I don't even know where the 2160 number comes from.

My config.txt is similar to yours.

The last output line of tvservice -m DMT looks good:

Code: Select all

...
(prefer) mode 87: 2560x1080 @ 60Hz 64:27 (21:9), clock:181MHz progressive

The output of edid parser isn't clear to me. But it looks like it likes the new mode, but ends up with CEA 16 (1920x1080@60). Although it appears nowhere, 2160x1080 is actually used.

Code: Select all

Enabling fuzzy format match...
Parsing edid2...
HDMI:EDID version 1.3, 1 extensions, screen size 58x24 cm
HDMI:EDID features - videodef 0x80 standby suspend active off; colour encoding:RGB444|YCbCr422; sRGB is not default colourspace; preferred format is native; does not support GTF
HDMI:EDID found monitor name descriptor tag 0xfc
HDMI:EDID monitor name is LG_ULTRAWIDE
HDMI:EDID found monitor range descriptor tag 0xfd
HDMI:EDID monitor range offsets: V min=0, V max=0, H min=0, H max=0
HDMI:EDID monitor range: vertical is 56-75 Hz, horizontal is 30-90 kHz, max pixel clock is 240 MHz
HDMI:EDID monitor range does not support GTF
HDMI:EDID failed to find a matching detail format for 2560x1080p hfp:64 hs:64 hbp:96 vfp:3 vs:10 vbp:18 pixel clock:185 MHz
HDMI:EDID calculated refresh rate is 60 Hz
HDMI:EDID guessing the format to be 2560x1080p @60 Hz
HDMI:EDID found unknown detail timing format: 2560x1080p hfp:64 hs:64 hbp:96 vfp:3 vs:10 vbp:18 pixel clock:185 MHz
HDMI:EDID found preferred CEA detail timing format: 1920x1080p @ 60 Hz (16)
HDMI:EDID established timing I/II bytes are A5 4B 80
...
HDMI:EDID preferred mode remained as CEA (16) 1920x1080p @ 60 Hz with pixel clock 148 MHz
HDMI:EDID has HDMI support and audio support

[jeuf]

Thomason,

Thanks a lot I used your config.txt file with my LG29UM65 and a Rpi2 using Openelec 5.95.1 and it works just perfectly at 2560x1080 !!

Hugh,

I have a model very similar to yours and it works just fine. I suggest to give a try with OE 5.95.1

Regards,
Jeuf

[sraeisi]

I have an odd one

I have my Pi set up on a monitor with max resolution on 1600x1200 60Hz using a HDMI to DVI adapter and I set up the config as below:

config_hdmi_boost=4
hdmi_drive=1
hdmi_group=2
hdmi_mode=51

For all hdmi_mode values > 4 on hdmi_group=2 I get blinking red lines where it should be black screen.

i.e for hdmi_mode=51 I get the whole black areas filled with blinking red horizontal lines.

Any idea how to fix it?

[mrillinthebrain]

Hi!

I have also a LG Electronics 29UM65-W, 29"
i was able to get a 2560x1080 resolution but i have huge black bars left and rigth and the screen is not centered.
I am able to move the mouse "behind" the right black bar.

with overscan settings i was only able move the picture to the left or rigth.
but if i use a negative value for overscan_left the screen stays black but tells me its getting a signal.
#overscan_left=-50
#overscan_right=-50

here are my settings: (some of them does not seem to have an effect)
force_hdmi__hotplug=1
hdmi_drive=2
avoid_pwm_pll=1
disable_overscan=1
hdmi_ignore_edid=0xa5000080
hdmi_group=2
hdmi_mode=87
hdmi_cvt 2560 1080 60 7 0 0 0
hdmi_timings=2560 1 64 64 96 1080 1 3 10 18 0 0 1 60 0 185580000 7
config_hdmi_boost=4
max_framebuffer_width=2560
max_framebuffer_height=1080
framebuffer_width=2560
framebuffer_height=1080
gpu_mem=128
arm_freq=900
gpu_freq=275
sdram_freq=500
hdmi_pixel_freq_limit=400000000
avoid_pwm_pll=1
hvs_priority=0x32f4


edid data:
https://drive.google.com/file/d/0B5yO2j ... sp=sharing

i got the hdmi_timings out of the edid data and edidparser from pi. also took a view to https://forums.adafruit.com/viewtopic.p ... 0&start=60 and http://www.edidreader.com/

but by now no Idea how to reduce the black bars...
anyone?

[mrillinthebrain]

i will never know why but max_framebuffer_height was the problem.

i have now 2560x1080 60hz 21x9 on my LG 29UM65 on raspbian(!)

here is my confix.txt

Code: Select all

hdmi_ignore_cec_init=1
hdmi_drive=2
disable_overscan=1

hdmi_ignore_edid=0xa5000080
hdmi_group=2
hdmi_mode=87
hdmi_timings=2560 1 64 64 96 1080 1 3 10 31 0 0 1 60 0 185580000 8

config_hdmi_boost=4

max_framebuffer_width=2560
max_framebuffer_height=1280
framebuffer_width=2560
framebuffer_height=1080

gpu_mem=128
arm_freq=900
gpu_freq=275
sdram_freq=500
hdmi_pixel_freq_limit=400000000
avoid_pwm_pll=1

[dan002]

Yes! Thank you for the config, now I also have the display working on my LG ultra wide.

[dastels]

Has there been any advances on this topic? I need a Pi 2 to output to square display of 1600x1600.

Dave

[trio198]

Hi,

Does anyone has any experience with 32:9 (1920*540) monitor running on pi 2?
I'm trying to build a digital signage system and this monitor seems to be what I need.

[trio198]

Hi,

Another question:

How do you find values for the hdmi_timings parameters?

Thanks.