[libcamera-devel] How to detect camera after power on the raspberryPi.

[tetsuya.nomura at soho-enterprise.com]

Dear Naush-san

Thank you very much for your prompt reply.

I'll answer in line, below. 

Best Regards,
================================
  Tetsuya NOMURA
================================
 Soho Enterprise Ltd.
 4-11-26 Gent BLDG 2F, Asahi-cho, Atsugi-shi, 
 Kanagawa, Japan  243-0014
 URL: https://soho-enterprise.com
 Mail: tetsuya.nomura at soho-enterprise.com
 Phone: +81-90-1839-1135
================================


-----Original Message-----
From: Naushir Patuck <naush at raspberrypi.com> 
Sent: Monday, October 19, 2020 7:09 PM
To: tetsuya.nomura at soho-enterprise.com
Cc: David Plowman <david.plowman at raspberrypi.com>; libcamera-devel at lists.libcamera.org
Subject: Re: [libcamera-devel] How to detect camera after power on the raspberryPi.

Dear Nomura-san,

Could you provide more details on this board please?  I could not gather any information from the website you linked.

(Soho Nomura)Sorry for the lack of information.
I'm using my own camera board without Raspi official crypt chip.
And Transceiver chips are TI DS90UB953-Q1/DS90UB954-Q1, 
https://www.ti.com/product/DS90UB953-Q1
https://www.ti.com/product/DS90UB954-Q1

Connection of the devices:
IMX219 module <-> original camera board <-> UB953 serializer <-> serial cable <-> UB954 de-serializer <-> RaspberryPi 4 MIPI CSI port.

UB953/UB954 can pass the I2C communication as if IMX219 sensor were directly connected to RaspberryPi
after configuring the transceiver chips.
I am configuring(programing) them by shell script of i2cset command like attached.
But the device tree information as been already finalized before running the sh script.


Firstly, are you using an official Raspberry Pi Camera v2 board on the other end of this link?  How is the transceiver chip programmed?
(Soho) Using the original sensor board and run the sh script. 
After run the script, I run the camera application to configure IMX219 and display the image with SW ISP.

Also, what application are you using when you say that you can get RAW images out of your setup?
(Soho) We have made the raw capture application based on "dcraw".

Finally, I should note, that this type of questions might possibly be more suited for the Raspberry Pi Camera forums
(https://www.raspberrypi.org/forums/viewforum.php?f=43) and not the libcamera mailing list - assuming it is related to the hardware setup you are using.

(Soho)
I understand. I'll do so.

Many thanks,
Naush

On Mon, 19 Oct 2020 at 10:38, <tetsuya.nomura at soho-enterprise.com> wrote:
>
> Dear Sirs.
>
> May I have your favor about initialization of the RaspberryPi and the camera?
>
> I'm now evaluating the camera extension board of FPD LINK III technology to extend the camera cable for 2~3m from the RaspberryPi.
> https://soho-enterprise.com/2020/10/11/post-866/
>
> This board can pass the I2C communication to IMX219 after configuring 
> the transceiver chip, However, after configuration and run the qcam, 
> it seems the qcam program does not detect the IMX219 And I cannot start the camera even I designate the image sensor name.
>
> I can start the IMX219, get the RAW image by our own program and see the image.
> Then if qcam can send the necessary command to IMX219 when start 
> running the qcam, I think I can see the image through qcam program.
>
> It would be great if you could give us an advice to solve it.
> I appreciate your kind help in advance.
>
> Best Regards,
>
> NOMURA
>
> ================================
>   Tetsuya NOMURA
> ================================
>  Soho Enterprise Ltd.
>  4-11-26 Gent BLDG 2F, Asahi-cho, Atsugi-shi,  Kanagawa, Japan  
> 243-0014
>  URL: https://soho-enterprise.com
>  Mail: tetsuya.nomura at soho-enterprise.com
>  Phone: +81-90-1839-1135
> ================================
>
>
>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: cam0_run.sh
Type: application/octet-stream
Size: 4234 bytes
Desc: not available
URL: <https://lists.libcamera.org/pipermail/libcamera-devel/attachments/20201019/67947f70/attachment-0001.obj>