I’m trying to get a Matrix Orbital HDMI monitor working with my Colibri iMX8 system. The image that displays continuously moves horizontally. Part of the image is legible as it scrolls by. I’ll attach some pictures.
A similar monitor (EVICIV Raspberry Pi Touch Screen) works fine with the Colibra.
The Matrix Orbital monitor works fine with Raspberry Pi, Windows 10, and Ubuntu.
Both of these monitors are using EDID to tell the system what settings to use and the settings look reasonable.
LT8912 logs the following for the Matrix Orbital:
[ 4.085871] lt8912 20-0048: “1024x600”: 61 51000 1024 1164 1184 1323 600 612 615 635 0x48 0x5
[ 4.087695] lt8912 20-0048: LT8912 ID: 12, b2
Looking at the information here nothing seems obviously amiss. The numbers in the logs and modetest appear to be within the expected ranges for this display.
By the way the video you shared, I can’t view it. It seems my browser does not have the codec to play this video, and I’m not sure what video format you shared.
As for the issue, it’s not obvious what is wrong at the moment. As you said a similar display with the same resolution works fine. The EDID seems to be giving okay values to the device. On the Matrix Orbital display have you tried changing resolution (if possible) just to see if it has an effect?
How does the modetest/timing values of the Raspberry Pi Touch screen display compare to the Matrix Orbital display?
The video was created with an iPhone, so it is in QuickTime format.
I’ve tried other resolutions with this display, but that didn’t help.
The modetest values from the Raspberry Pi Touch Screen are very similar, the main difference is in the flags the PI screen uses phsync and the Matrix uses nhsync.
At this point, we’re going to give up on this display, since we don’t have much invested in it, only ordered a couple samples.
At this point, we’re going to give up on this display, since we don’t have much invested in it, only ordered a couple samples.
Very well then. I agree it’s probably better to move on if you’re still early on in evaluation. Displays can be quite finicky in embedded systems. Sometimes it’s more time efficient to move on to a display that does work then try and get a display that does not work, working.