RMA received. You will be contacted tomorrow.
RMA received. You will be contacted tomorrow.
What Display/TV are you using?
I have a display that shows HDMI is connected, but no picture. After I boot the board and get to that point, if I power cycle the display, the image them shows up.
Here is a list of those we know work.
This new one is a cheap Proscan PLED1960A. The new image defaults to 1280x720.
I am hoping other people will speak up and say what they have that works. So far, nothing has come in. If I hear, I will add them to the list.
We are still looking and the SW and we think there may be something out of whack and an investigation is ongoing.
Try the latest image.
OOPs. Just got past a few more …
Sounds like maybe the one has an issue. Go ahead and request an RMA.
Update from the RMA dept: “We have tested the HDMI interface on your unit with different TVs/monitors and all of them are working properly. We are able to see the Angstrom desktop on the TVs. The HDMI not working for you could be due to software issue.”
So the hardware is fine, but the TV is not supported by the hardware. I’m still fuzzy on how to dump the EDID debugging information to a text file. Is there a guide on how to do this somewhere? If the BBB still doesn’t output to my TV then I’ll post that information here. Hopefully discover a solution to this problem.
Search EDID on the mailing list. There is a discussion going on now. You may need a Linux PC to dump it, but we are working on something that should help. Not immediately, but in the near future.
I am also adding a trouble shooting guide to the SRM. I hope to have it out in a few days, if I can every stop answering emails. Here is part of what is going in the manual.
Many people are having issues with getting HDMI to work on their TV/Display. Unfortunately, we do not have the resources to buy all the TVs and Monitors on the market today nor go to Ebay and buy all of the TVs and monitors made over the last five years to thoroughly test each and every one. We are depending on community members to help us get these tested and information provided on how to get them to work.
One would think that if it worked on a lot of different TVs and monitors it would work on most if not all of them, assuming they meet the specification. However, there are other issues that could also result in these various TVs and monitors not working. The intent is that this page will be useful in navigating some of these issues. As others also find solutions, as long as we know about them, they will be added here as well.
The early release of the Software had some issues in the HDMI driver. Be sure and use the latest SW to take advantage of the improvements.
EDID is the way the board requests information from the display and determines all the resolutions that it can support. The driver on the board will then look at these timings and find the highest resolution that is compatible with the board and uses that resolution for the display. For more information on EDID, you can take a look at http://en.wikipedia.org/wiki/Extended_display_identification_data
If the board is not able to read the EDID, for whatever reason, it does not have this information. A few possible reasons for this are:
· Bad cable
· Cable not plugged in all the way on both ends
· Display not powered on. (It should still work powered off, but some displays do not).
One easy thing to overlook is that you need to select the display source that matches the port you are using on the TV. Some displays may auto select, so you may need to disconnect the other inputs until you are sure the display works with the board.
1.1.3 OUT OF SEQUENCE
Sometimes the display and the board can get confused. One way to prevent this is after everything is cabled up and running, you can power cycle the display, with the board still running. You can also try resetting the board and let it reboot to resync with the TV.
Some displays use what is called overscan. This can be seen in TVs and not so much on Monitors. It causes the image to be missing on the edges, such that you cannot see them displayed. Some higher end displays allow you to disable overscan.
Most TVs have a mode that allows you to adjust the image. These are options like Normal, Wide, Zoom, or Fit. Normal seems to be the best option as it does not chop of the edges. The other ones will cop of the edges.
1.1.5 Taking a Nap
In some cases the board can come up in a power down/screen save mode. No display will be present. This is due to the board believing that it is asleep. To some out of this, you will need to hit the keyboard or move the mouse.
Once working, the board will time out and go back to sleep again. This can cause the display to go into a power down mode as well. You may need to turn the display back on again. Sometimes, it may take a minute or so for the display to catch up and show the image.
Audio will only work on TV resolutions. This is due to the fact that is the way the specification was written. Some displays have built in speakers and others require external. Make sure you have a TV resolution and speakers are connected if they are not built in. The SW should default to a TV resolution giving audio support. The HDMI driver should default to the highest audio supported resolution.
Awesome! I’ll try this out as soon as I get it back in the mail. Thanks.
Gerald, thank you for putting together this helpful resource for troubleshooting display issues and also for all the hard work you are doing for this community.
It is just a start! Needs more work. What is really needed is a way to force a resolution. We are working on that.
Just post the edid to this forum as soon as you can and we will figure out what is “special” about this monitor.
Also the kernel log with drm.debug=7 set on the kernel parameters will be very helpful.
Thanks to you and your whole team for the great efforts.
In section 1.1 or elsewhere, if possible and you if think useful, could you pl. point to a link where one can find the latest/greatest list of HDMI monitors. And may be elsewhere, links pointing to lists for wifi-dongles, bluetotth-dongles, etc. Hopefulyy those links could be maintained in beaglebone.org or wherever you see fit.
You can find the list at the address of the support link on the card that
came in the box.
Just look under accessories in the table of contents.
I got the BBB back today. Thank you.
After hooking it up to wall power and TV and powering on, there is still no display. I reset the BBB, and the TV, still nothing.
I set the drm.debug=7 setting in the uEnv.txt file.
I have also logged into the terminal and issued this command:
but nothing happens on screen that I can see. I’m not sure what to do now.
I can FTP into the BBB to grab any files that will help troubleshoot. Please let me know how to proceed.
For the EDID parse to work, you need newer SW…
Upgrade to this development version http://dominion.thruhere.net/koen/angstrom/beaglebone/test-only-not-for-production-BBB-eMMC-flasher-2013.05.15.img.xz
Then try the parse method.
is this a version that might solve the jitter issue with my ASUS
VE228H? if not, then i'll just avoid wasting all the bandwidth of
Latest test SW bricked my BBB. No LEDs when booting from eMMC, even though it looks like the flash was successful (4 solid LEDs).
You cannot brick the board. It worked fine for me. I have done it dozens of times.
Most likely something went wrong in one of the steps. Did it take more than 45 minutes to complete the flashing process?