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

HDMI IN with tc358743 #9

Open
mkameke opened this issue Mar 17, 2020 · 6 comments
Open

HDMI IN with tc358743 #9

mkameke opened this issue Mar 17, 2020 · 6 comments

Comments

@mkameke
Copy link

mkameke commented Mar 17, 2020

Hello,
we try to use the rpi with Debian Buster and the tc358743 (HDMI IN on the CSI Port).

The HDMI Device (w10 computer) rings at starting the stream because the rpi connecting the hdmi device, so it seems thats it is starting normally but then we get a segmenation fault. Please take a look at the attachments.

rpi

w10_streaming_client

messages.txt

kind regards,
Martin

@shortstheory
Copy link
Owner

shortstheory commented Mar 17, 2020

Very interesting. Could you share more details about the HDMI-IN device? In particular, please share the output of running:

v4l2-ctl --list-formats-ext --all

The most likely cause of this is that APStreamline treats it like a MJPEG camera (the default) when the device doesn't actually support the caps.

@mkameke
Copy link
Author

mkameke commented Mar 18, 2020

Hi,

it is the r100 from auvidea. It is nearly the same like the popular b101 HDMI In board.
https://auvidea.eu/product/70300/
https://auvidea.eu/b101-hdmi-to-csi-2-bridge-15-pin-fpc/

Datasheet IC: https://toshiba.semicon-storage.com/eu/semiconductor/product/interface-bridge-ics-for-mobile-peripheral-devices/hdmir-interface-bridge-ics/detail.TC358743XBG.html

v4l2 output:
v4l2.txt

at systemstart:
#hard reset integrated B102 module
echo "5" > /sys/class/gpio/export
echo "out" > /sys/class/gpio/gpio5/direction

echo "0" > /sys/class/gpio/gpio5/value
echo "1" > /sys/class/gpio/gpio5/value

kind regards,
martin

@shortstheory
Copy link
Owner

Hi, thanks for sharing the V4L2 output. The issue is that APStreamline tries treating it as an RPi camera on seeing the Stepwise frame formats, but the HDMI IN does not support all the caps that APStreamline expects which is what causes the Segmentation Fault above.

The solution to this...is not pretty. It will require adding special support for the HDMI IN device in APStreamline. While I have no issues with doing that, APStreamline in its current state doesn't make it easy to add new camera pipelines. I have thought about a way to fix it, but I'll only be able to patch it in 2-3 months from now. Will update this request once I'm done.

@GlidLov
Copy link

GlidLov commented Mar 29, 2021

+1 on this. i have some of the same HDMI cards and it would be a very nice feature for APstreamline to support this hardware. Alternative to this is the FHD hdmi-to-usb capture card (Mjpeg), anyway the one with TC chipset is smaller, and "more integrated".

@shortstheory
Copy link
Owner

Could you share some links to the parts you're referring to? I haven't worked with HDMI IN or HDMI to USB capture cards before.

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

No branches or pull requests

3 participants