chchart wrote: ↑
Fri Jun 21, 2019 5:17 am
I am using B101 with RPi 3B+ utilizing yavta. First of all, thank you everyone for active discussion and 6by9 for providing the support for yavta. B101 is connected to a Mac Mini, and it works great!
But, it does not work in Mac's recovery mode. When yavta capture command is run, it would "fail to create pool" and "select timeout." Does anyone have a guess to why it does not work?
I heard that screenshot does not work in the recovery mode because it's outside of the "userspace." Does yavta use mechanism similar to screen capture? I cannot seem to understand, as Pi should still be receiving a video input..
Also, I've tested with the same setup with Raspberry Pi Zero W with B102 bridge using "raspistill" and "raspivid" in Mac's recovery mode, and it works fine. That's why I am curious as to why B101 with yavta does not work.
If someone could explain what yavta does differently from raspivid that might have cause the failure, I would greatly appreciate it!
Thank you in advance.
yavta does very little different from raspivid, except that the Linux kernel is controlling it all.
Please provide the full output from yavta (in code tags). Also the output of "v4l2-ctl --query-dv-timings", and "v4l2-ctl -V" after having run yavta.
The TC358743 chip on the B101/102 takes HDMI and produces CSI2 out. The Pi receives this into a memory buffer via the bcm2835-unicam kernel driver. yavta then configures a pipeline to pass those buffers into the GPUs MMAL system to process the image and render and/or video encode it.
Software Engineer at Raspberry Pi Trading. Views expressed are still personal views.
I'm not interested in doing contracts for bespoke functionality - please don't ask.