User avatar
madnerd
Posts: 10
Joined: Wed Nov 01, 2017 6:43 am
Location: Montpellier, France
Contact: Website Twitter

Re: HDMI to CSI-2 via TC358743 on kernel 4.1

Wed Jan 17, 2018 1:04 pm

In their manual for B101 Auvidea specifies several pinouts - I tried to match those to adafruit.
I recently wired an I2S Audio Out Interface (PCM5102) on a Raspberry Pi Zero

Pinout.xyz was pretty useful (as always).
https://pinout.xyz/pinout/pcm#

I only used 3 pins
[*] I2S Audio Bit Clock (BCK -> PCM CLK) = pin 12/BCM 18
[*] I2S Audio Data In (DIN -> PCM DOUT) = pin 40/BCM 21
[*] I2S Audio Word Clock (LCK -> PCM FS) = pin 35/BCM 19

Since this is audio IN (pin 38/BCM 20)
It looks like your wiring is OK.

Image
Drivers
I never used I2S Audio IN, but for my audio interface I needed to enable an overlay (hifiberry-dac).

Did you compile the I2S module as explained on the Adafruit tutorial ?
Do you see an audio interface when you type?

Code: Select all

arecord -l
If you have already compiled the I2S module, maybe the driver doesn't work for the audio I2S interface on the auvidea B101.
Auvidea Reset and Cable Pins are unclear - Which GPIO shall I connect those?
I don't think this is related to audio.
RESET : Reset the TC58743 chip
CABLE DETECT : pin is HIGH when an HDMI cable is plugged in.

hblanken
Posts: 10
Joined: Fri May 06, 2016 11:43 am

Re: HDMI to CSI-2 via TC358743 on kernel 4.1

Thu Jan 18, 2018 8:50 am

Thanks for the reply - yes I activated all as per the adafruit tutorial. All works as per instructions.

Only thing is that I do not get any audio into the wav file at the very end. It is just silent.

I connected a HDMI camera with inbuilt microphone and I can record mp4 but no wav or mp4 with sound.

Must be some little quirk we are missing here.

6by9
Raspberry Pi Engineer & Forum Moderator
Raspberry Pi Engineer & Forum Moderator
Posts: 4819
Joined: Wed Dec 04, 2013 11:27 am
Location: ZZ9 Plural Z Alpha, aka just outside Cambridge.

Re: HDMI to CSI-2 via TC358743 on kernel 4.1

Thu Jan 18, 2018 9:47 am

If you're using raspivid then it is routing the audio over the csi bus, not i2s. There was a way of extracting that, bit I don't recall it. Basically don't use raspivid for tc358743.
The kernel driver is set up for i2s output. It also exports a v4l2 control indicating whether audio is present or not.
Software Engineer at Raspberry Pi Trading. Views expressed are still personal views.
Please don't send PMs asking for support - use the forum.
I'm not interested in doing contracts for bespoke functionality - please don't ask.

steeley
Posts: 5
Joined: Fri Jun 22, 2012 3:00 pm

Re: HDMI to CSI-2 via TC358743 on kernel 4.1

Fri Jan 19, 2018 5:46 pm

I got one of these boards about a year ago, and have got round to using it for a project I have next week.

Unfortunately as stated earlier there is some confusion about the reset line which basically means if that it is incorrect it won't work.
Early B101boards seemed to have the wrong design for the reset and need some mods I think.

Despite repeated requests to the manufacturer of the board about this I have had no reply.

if any one has this setup on a PI3 please let us know what you did to get the reset working.

TIA

rocky11
Posts: 1
Joined: Fri Jan 19, 2018 6:22 pm

Re: HDMI to CSI-2 via TC358743 on kernel 4.1

Fri Jan 19, 2018 6:37 pm

Hello,

First of all - thank you all for your commitment and support! I've just read whole topic and saw enormous work you have done :)

I'm afraid that I have an issue with resolutions in EDID. I'm using B102 board with Rpi3, firmware up-to-date.
I've followed the instructions from https://www.linux-projects.org/uv4l/installation/ and my scripts (using v4l2) are able to capture video from HDMI.

Problem is: the maximum resolution I can see on source computer is 720p.
If I understand correctly, I can change Toshiba's EDID by using @6by9 EDID and enable it to capture screen in 1080p resolution, right?

I got EDID file from https://raw.githubusercontent.com/6by9/ ... 50EDID.txt and tried to set it using:

Code: Select all

v4l2-ctl --set-edid=file=1080P50EDID.txt --fix-edid-checksums
However, the VIDIOC_S_EDID: failed: Invalid argument appears. What does it mean? How can i create a valid file?

I would be grateful for any support ;)

hblanken
Posts: 10
Joined: Fri May 06, 2016 11:43 am

Re: HDMI to CSI-2 via TC358743 on kernel 4.1

Sat Jan 20, 2018 5:33 am

6by9 wrote:
Thu Jan 18, 2018 9:47 am
If you're using raspivid then it is routing the audio over the csi bus, not i2s.
Really, that would be excellent - but now I am really confused. In this thread and several others there was the statement that audio has never been extracted from the B101 rv4. And I have so far not been successful either.

Must I set up the tc358743 kernel driver first?
I am travelling right now, but shall I only do this and it works? With the original board or only with the kernel driver?
raspivid -t 0 -o - | avconv -i pipe:0 -c:v libx264 -preset ultrafast -tune zerolatency -acodec aac -ab 128k -strict experimental -f file.flv
6by9 wrote:
Thu Jan 18, 2018 9:47 am
There was a way of extracting that, bit I don't recall it. Basically don't use raspivid for tc358743.
The kernel driver is set up for i2s output. It also exports a v4l2 control indicating whether audio is present or not.
You are saying, if I would rather like to have audio enabled via i2s, I should not use raspivid? If I use ffmpeg with v4l2 I am not yet successful for audio nor via i2s and csi directly..
6by9 wrote:
Thu Jan 18, 2018 9:47 am
The kernel driver is set up for i2s output. It also exports a v4l2 control indicating whether audio is present or not.
Audio present via i2s? Do we have any further about this?

Thanks so much

ruder
Posts: 8
Joined: Sat Nov 18, 2017 3:48 pm
Location: Rajkot,Gujarat,India.
Contact: Facebook Twitter

Re: HDMI to CSI-2 via TC358743 on kernel 4.1

Fri Feb 02, 2018 3:51 pm

Hello,

is it working for RPi-Cam-Web-Interface with TC358743?
if anyone has tried.
Ty :)

koop_g
Posts: 4
Joined: Sun Jan 14, 2018 2:20 pm

Re: HDMI to CSI-2 via TC358743 on kernel 4.1

Thu Feb 08, 2018 10:28 pm

@6by9
after some drilling and trying to understand the language you guys speak( I am sill not)
I have managed to to install the tc driver by you !
lol I needed peace from every page

any way I wen with the HDMI in hack
and then the yavata repo in the end
so I think I am on the spot now

running your tc_... app Working and I can finely see my 5D Mark 3 on raspberry pi, no HDCP involved
(after I bought 8 hdmi switchers to test ;:) )
any way.....
Raspberry pi 3
raspbian stretch
canon 5d mark 3
B101 Borad with the Tc drivers by you
giving me a video output ( I do have some system crashes, not sure why )
on my camera I have an option of output
24p, 1080i50, 1080i60

now for my needs
I DONT need to record the video output. NEVER.
Quilty: not important ( I would go av if i all of this breaks )
all I need is to make my openCV test.py on the raspberry pi to be feed with the stream from the camera.
everything is localy on the raspberrypi and stay there

I have managed to do that with uv4l on jessi build
but can't make that happens on stretch

can it be done?

I am willing to Beta Tester for anything in bound with my hardware
my English is not well
but I am QA engineer in a big corp so I can try my best here ( with your weird language, i mean the techi language )

my Goal would be getting back to were I am comfortable watching my pycharm do my magic
and make a use of this tech on the next lvl which is
apps, python wrap etc....

please let me know how can I get openCV link by cap.VideoCapture(0) to get the feed from my cam ....

by the way in the end I get the same as @rock11
" VIDIOC_S_EDID: failed: Invalid argument appears"

{code}
pi@raspberrypi:~ $ ./test.sh

CEA-861 Header
IT Formats Underscanned: no
Audio: no
YCbCr 4:4:4: no
YCbCr 4:2:2: no

HDMI Vendor-Specific Data Block
Physical Address: 3.0.0.0
YCbCr 4:4:4 Deep Color: no
30-bit: no
36-bit: no
48-bit: no

CEA-861 Video Capability Descriptor
RGB Quantization Range: yes
YCC Quantization Range: no
PT: Supports both over- and underscan
IT: Supports both over- and underscan
CE: Supports both over- and underscan
VIDIOC_S_EDID: failed: Invalid argument
ffmpeg version 3.2.10-1~deb9u1+rpt1 Copyright (c) 2000-2018 the FFmpeg developers
built with gcc 6.3.0 (Raspbian 6.3.0-18+rpi1) 20170516
configuration: --prefix=/usr --extra-version='1~deb9u1+rpt1' --toolchain=hardened --libdir=/usr/lib/arm-linux-gnueabihf --incdir=/usr/include/arm-linux-gnueabihf --enable-gpl --disable-stripping --enable-avresample --enable-avisynth --enable-gnutls --enable-ladspa --enable-libass --enable-libbluray --enable-libbs2b --enable-libcaca --enable-libcdio --enable-libebur128 --enable-libflite --enable-libfontconfig --enable-libfreetype --enable-libfribidi --enable-libgme --enable-libgsm --enable-libmp3lame --enable-libopenjpeg --enable-libopenmpt --enable-libopus --enable-libpulse --enable-librubberband --enable-libshine --enable-libsnappy --enable-libsoxr --enable-libspeex --enable-libssh --enable-libtheora --enable-libtwolame --enable-libvorbis --enable-libvpx --enable-libwavpack --enable-libwebp --enable-libx265 --enable-libxvid --enable-libzmq --enable-libzvbi --enable-omx-rpi --enable-mmal --enable-openal --enable-opengl --enable-sdl2 --enable-libdc1394 --enable-libiec61883 --enable-chromaprint --enable-frei0r --enable-libopencv --enable-libx264 --enable-shared
libavutil 55. 34.101 / 55. 34.101
libavcodec 57. 64.101 / 57. 64.101
libavformat 57. 56.101 / 57. 56.101
libavdevice 57. 1.100 / 57. 1.100
libavfilter 6. 65.100 / 6. 65.100
libavresample 3. 1. 0 / 3. 1. 0
libswscale 4. 2.100 / 4. 2.100
libswresample 2. 3.100 / 2. 3.100
libpostproc 54. 1.100 / 54. 1.100
pipe:: Invalid data found when processing input

{code}

Return to “Graphics, sound and multimedia”

Who is online

Users browsing this forum: PianoPCJ/A.F and 15 guests