[beagleboard] Re: BeagleBone Black - No HDMI Output

GoogleGroups
1

Did you try anything from this page?

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

Gerald

2

OK. Send it in. Request an RMA.

http:beagleboard.org/support/RMA

Gerald

3

Glad it worked!

Gerald

4

You know. If there was patch for this, I would think it would already be included. If it is working with the original, then I suggest you go back to he original image.

I have no idea what is going on here with the DRM driver and all those TVs and monitors out there. I would welcome some help from anyone that would like to help us figure out why so many TVs and monitors work flawlessly and why some do not.

Gerald

5

Sadly the 5-20 image has not changed the results I am seeing, or not seeing on either of the two HD TVs or VGA monitor I have been trying to work with. I have tried the procedure on the linked page with both HD displays. I am willing to try the last procedure once I get a USB to serial cable, but I find the instructions unclear. I have interjected my questions in [ ] below.

After you have updated the SW and connected the cable, perform the following steps: [I see where the cable is to be connected to the pins on the BBB, but what is the other end connected to? Just a power source? A Windows machine? A Linux machine?]

  1. Power on the board with it connected to the display. Make sure the display is not in a sleep mode.
  2. Wait for the board to finish the initial boot, about 3 minutes.
  3. You should see a login. Type “root” and hit ENTER. [Where will I see this? On the display? (Isn’t that the problem we are trying to solve?)]
  4. Type “cd /sys/class/drm/card0/card0-HDMI-A-1/” and hit ENTER.
  5. Type "parse-edid edid"and hit ENTER.
  6. You should get a printout similar to the one below: …

Additional guidance please.

Thanks,

Steve

6

The 5-20 image works for some people that did not work before. For others it breaks things.

Here is the main issue. 3.8 kernel uses DRM. We have no way currently to manually set the resolution on the HDMI. It is all up to the EDID exchange of information which is suspect on a lot of displays. There is a 5/18 test release that worked fine for 1920x1080. The 5/20 release was supposed to be that release,. If you will notice on the WikI the 5/20 is not listed. Until it is, it is not an official release.

And this is coming direct from the right hand.

Gerald

7

Success! I was ready to give up and go to RMA. But as a last effort, I decided to buy a micro HDMI to HDMI cable and bypass the micro HDMI/HDMI adapter I had been using. Booted right up with the latest official release, beautiful video, no more problem.

Woohoo!

8

Awesome! Unfortunately, I have heard this before. I am trying to get something going to where everyone can buy pretested cables. Nothing solid yet but stay tuned!

Gerald

9

I have a micro-hdmi adaptor too, however the video works with the Aoril-12 angstrom build. The more recent builds up to May 20 all flicker. Would this be due to the adaptor?

10

I don’t know the HDMI standard or HDMI hardware well enough to know for sure if it’s possible. Based on my experience though, I would replace the adapter with a cable or a verified-working adapter.

As an FYI, this is the cable I achieved success with http://www.amazon.com/gp/product/B00B1DC9HM.

11

Sabi ni Gerald noong Wednesday, May 22, 2013 7:27:37 AM UTC+8:

You know. If there was patch for this, I would think it would already be included. If it is working with the original, then I suggest you go back to he original image.

I have no idea what is going on here with the DRM driver and all those TVs and monitors out there. I would welcome some help from anyone that would like to help us figure out why so many TVs and monitors work flawlessly and why some do not.

If it helps, mine worked. Here’s the label at the back of the monitor:

Pardon the funky angle, had to work around some obstacles :slight_smile:

Also, haven’t had the chance to try the audio yet.