See what? The text output?
This is a standard Raspbian image?DanR wrote: ↑Tue May 21, 2019 10:20 amI have got my newer Toshiba dev board up and running and after setting the EDID file and setting the timings I can see that it sees the video stream, however when I test it with yavta and v4l2_mmal I get the following memory allocation errors (I've tried the GPU ram set to 64Mb and 128Mb with no success), do you have any ideas as I'm a bit at a loss really (possibly due to sleep deprivation?!):
geosapien wrote: ↑Tue May 21, 2019 8:09 pmhow would i check to see if i did that? I followed all of the instructions from the previous post. i have rebuilt the pi 4 times and get the same resultMy only guess is that you have enabled the vc4-kms-v3d driver, therefore MMAL can't render to the screen.
Code: Select all
lsmod | grep vc4
What to do should you require HDCP and not be able to negotiate it is badly defined. When using VideoCore with HDCP I recall they went to various efforts to put up a padlock symbol or similar should "protected content" be displayed with no HDCP negotiated.geosapien wrote: ↑Thu May 23, 2019 9:20 pmI have a pi hole sitting on my desk, so i plugged it into the b101 board. I had to reboot the pi, but after the EDID and timing query came back i was able to run the ./yavta commands and i got video on the monitor attached to the pi.
So this whole time it was the amazon box........
Encoding from the B101 is something I had been playing with, although mainly to a file rather than streaming.geosapien wrote:Thank you for all the help with this. Would have been spinning my wheels for months. Now i get to learn how to push the stream via UDP so i can use it as an encoder. Can you point me in the right direction? The Auvidea instructions dont work
I believe one of them used 2836, same as the Pi2 used to.
Not trivially with raspi_tc358743 (please note that it has moved to https://github.com/6by9/raspi_tc358743).