HDMI Succeses

We have a few people having some issues with HDMI on their respective TVs.

It would be most helpful to us if everyone that is not having issues could let us know the model and manufacturer of the TV/Display/Monitor that they are using. If you see you model posted by someone else, no need to post it again.

Also, if you had to do something “tricky” to make it work, we would like to have that information as well.

Thank you!!

Gerald

gerald@beagleboard.org
g-coley1@ti.com
http://beagleboard.org/
http://circuitco.com/support/

Works fine at 1280x1024 with an HDMI to DVI adapter on both HP S2031 and ViewSonic vs14833 (but the USB HID touchscreen isn’t recognized). I have three more at home (all with native hdmi port) I could try when I go for lunch (and one more here at the office if the graphic designer goes to lunch before me).

Thanks,
Hugh Johnson

So as not to create more churn, anyone responding, THANK YOU!!!

Gerald

Okay tried the three at home,

Asus VE278H - worked great at 720p

HP TSS - 23x11 (it’s HP but “unbranded”) worked at 1280x1024.

FAILED: LG 37LH30 - did not seem to work, the display didn’t even recognize that anything was plugged in at all.

Thanks,
Hugh Johnson

yet mine, which is a VE228H, had that annoying jitter. did you have
to add any boot-time video info? or did it just auto-detect and do
the right thing?

rday

I didn't do anything special, just plugged and played as they say. I didn't play too much so I just hooked it back up to double check and it looks perfect, nothing jittery at all.

I assume you tried it in both hdmi ports (does yours have two?), and maybe switched cables? What image are you using? I am on: BBB-eMMC-flasher-2013.05.03.img.xz (I'm pretty sure).

Thanks,
Hugh Johnson

I didn't do anything special, just plugged and played as they say. I
didn't play too much so I just hooked it back up to double check and
it looks perfect, nothing jittery at all.

I assume you tried it in both hdmi ports (does yours have two?),

  no, mine has only the one.

and maybe switched cables?

  i've got just the one micro-HDMI cable.

What image are you using? I am on:
BBB-eMMC-flasher-2013.05.03.img.xz (I'm pretty sure).

  i'm using koen's latest test flasher image, but the jitter has been
there since the beginning, across at least three different images. i'm
going to try to get my hands on another monitor for testing.

rday

hdmi display on the beagle bone black a4 is working autodetected at 1360x768 on an RCA MODEL# 32LB30RQD combination dvd/tv/32" display. It seems to not want to log in… but that appears to be another issue, possibly an incomplete previous boot or bad shutdown previously and if I’m unable to resolve that issue, I’ll start another thread.

Eric

Resolved the login issue… just hit reset and it came up fine. really nice to have a display. and proper power off, rather than just powerfail and reset.

Eric

I found my problem to be that the cheap HDMI to DVI cable I had didn’t tie the shields on both sides together. The only way I would get video is if I somehow grounded it another way. A simple way to do this is to connect a usb cable between the computer and BBB.

Hello!
Please understand, I’m not good at English.
I use BBB. I have a problem about HDMI.

LG FLATRON M2294D - It works the angstrom image(5/8)
But they don’t work the angstrom images(6/6, 6/17)

I tested 4 different monitors. worked other Monitors with any angstrom images.
Only LG FLATRON M2294D didn’t work.

What should I do?

Thanks.

2013년 5월 14일 화요일 오전 12시 55분 1초 UTC+9, Gerald 님의 말:

http://circuitco.com/support/index.php?title=BeagleBoneBlack_HDMI

And use the latest image. Those images are old.

Gerald

Hello!
I think I had some mistake what I wrote about the date.
I already tested the latest image(20/June/2013) with the other images(08/May/2013, 06/June/2013, 17/June/2013)

08/May/2013 - It was fine for all monitors.
06/June/2013, 17/June/2013, 20/June/2013 - Only 1 monitor didn’t work(LG FLATRON M2294D)

I’ll set the default resolution tomorrow , and then I’ll reply again whether success or not.

Thanks!

2013년 6월 26일 수요일 오전 12시 55분 4초 UTC+9, Gerald 님의 말:

Hello!
I set the resolution like list of supported resolutions.

1920x1080@24, 1280x720@60 - I can see the beaglebone image(left top) when the BBB boot. And then no signal

1324x768@60, 1280x768@60, 1280x1024@60, 1152x864@75, 1024x768@76, 1024x758@60, 800x600@60, 800x600@75, 640x480@75 - no signal

Here is the edid

parse-edid: parse-edid version 2.0.0
parse-edid: EDID checksum passed.

EDID version 1 revision 3

Section “Monitor”

Block type: 2:0 3:fd

Block type: 2:0 3:fc

Identifier “M2294D-PM”
VendorName “GSM”
ModelName “M2294D-PM”

Block type: 2:0 3:fd

HorizSync 30-83
VertRefresh 56-75

Max dot clock (video bandwidth) 170 MHz

Block type: 2:0 3:fc

DPMS capabilities: Active off:yes Suspend:yes Standby:yes

Mode “1920x1080” # vfreq 60.000Hz, hfreq 67.500kHz
DotClock 148.500000
HTimings 1920 2008 2052 2200
VTimings 1080 1084 1089 1125
Flags “+HSync” “+VSync”
EndMode
Mode “1360x768” # vfreq 60.015Hz, hfreq 47.712kHz
DotClock 85.500000
HTimings 1360 1424 1536 1792
VTimings 768 771 777 795
Flags “+HSync” “+VSync”
EndMode

Block type: 2:0 3:fd

Block type: 2:0 3:fc

EndSection

What should I do now?

Thanks

2013년 6월 26일 수요일 오전 12시 55분 4초 UTC+9, Gerald 님의 말:

So, the board is working fine then. Setting the resolution only affects the first Logo boot up resolution. Once EDID is read, the Kernel uses that to set the resolution.

Gerald

Hello!

What should I do now?

Thanks.

2013년 6월 26일 수요일 오후 9시 50분 55초 UTC+9, Gerald 님의 말:

At this point, it appears that you LCD is not compatible with what the Kernel is sending out. It is hard to say what the issue is.

Gerald

One thing you could try is to do an CTRL-ALT-F1 on the keyboard and see if that shows the command line display.

Gerald

Hello!

It shows the command line when I type the CTRL-ALT-F1.

I can’t use gui with this monitor now when I use angstrom image?

Thanks for reply.

2013년 6월 26일 수요일 오후 10시 44분 39초 UTC+9, Gerald 님의 말:

Oh it does? Is there a way to see the resolution from the display?
Maybe a menu option or something?
Or maybe switch inputs and see if the resolution is displayed?
What happens if you do CTRL-ALT-F2?

Gerald