Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

test: reference image #433

Open
CarlFK opened this issue Apr 17, 2018 · 2 comments
Open

test: reference image #433

CarlFK opened this issue Apr 17, 2018 · 2 comments

Comments

@CarlFK
Copy link
Contributor

CarlFK commented Apr 17, 2018

test: supply a known image on hdmi input0/1, compare that to a known image.
image would be one of:

  1. image file supplied at build time
  2. image uploaded over usb/eth
  3. frame grabbed from input0/1
  4. internally generated pattern.

Any one of these would be good for testing the critical bit: consuming hdmi.
having all of them would also test other bits of the system.

@mithro
Copy link
Member

mithro commented Apr 17, 2018

I would start with (4). If you turn off the uptime part of the current test pattern, that image should be a known starting point and testing that you get it from the USB device would be useful.

Once you know that you can reliably capture an image via USB, it should then be pretty trivial to use something like an RPi to act as a HDMI source and generate a bunch of test patterns in the "test-patterns" repo.

@CarlFK
Copy link
Contributor Author

CarlFK commented Apr 17, 2018

added issue - option: text on/off of pattern #434

Even with uptime changing and all the other text, I would think (hope) the output and input buffers could be compared before the new pattern image steps on the output. I wonder if testing a moving target makes a better test. like if it fails, it means some timing thing fell apart.

I can reliably capture an image via USB (smug face). I am slowly getting to a legitimate test suite.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants