OV9281 and Raspberry pi 4

[Ninic0c0]

Hi,

HW : OV9281 and raspberry pi 4B 4Go

SW: fresh buster install + deps

Could you please some info about this issue :

pi@raspberrypi:/home/pi/MIPI_Camera/RPI/python $ python capture.py
Open camera...
init_camera: Unexpected result.
pi@raspberrypi:/home/pi/MIPI_Camera/RPI/python $ i2cdetect -y -r 0
0 1 2 3 4 5 6 7 8 9 a b c d e f
00: -- -- -- -- -- -- -- -- -- -- -- -- --
10: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
20: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
30: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
40: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
50: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
60: 60 -- -- -- -- -- -- -- -- -- -- -- 6c -- -- --
70: 70 -- -- -- -- -- -- --
pi@raspberrypi:/home/pi/MIPI_Camera/RPI $ ./capture2opencv
Open camera...
init camera status = -1
pi@raspberrypi:/home/pi/MIPI_Camera/RPI $ ./ov9281_external_trigger
Open camera...
init camera status = -1
pi@raspberrypi:/home/pi/MIPI_Camera/RPI $ ./preview-camera0
Open camera...
Found sensor ov9281 at address 60

Could you please provide a solution ? Thx in advance.

Note: seems ok on raspberry pi 3B

[JirkaN1]

I have the same problem, OV9281 camera on rpi 1 run OK, but rpi 4/4GB throw segmentation fault.
Probed with the same SD card image with buster on both Rpis and then with fresh install on rpi 4.
Hardware of rpi 4 seems be OK, the original rpi camera capturing without any problem.
Result of the i2cdetect is the same, 0x6c
Thank You for any help.

[JirkaN1]

Bad rpi 4 board!
Probed with another board and the same SD card, the camera working without any problem with arducam and original rpi cam.
The bad board have infinity resistance on pin 12 - CAM_CLK, on another pins are some MegaOhms.

[Ninic0c0]

Hi @JirkaN1 , have you find any solution about this trouble ? I'm mean do you think hardware modification can solve this issue ?

[Ninic0c0]

@ArduCAM Is it possible to have some help ? Tested on 3 raspberry pi 4 (buster full updated) and same issue, so maybe the sensor is bogus or it is not compatible with rpi4...

[JirkaN1]

Hi Ninic0c0,
I don't think, that the rpi can be repaired home, under microscope find I no any defect.
Board have I changed by the seller, but after two days keyboard knocking
cant't capture faster than cca 60fps, it seems, that run only one lane even if is set mode 5. Have the M12 version two lanes @ArduCAM ?

[Ninic0c0]

Hi @JirkaN1 & @ArduCAM ,

More info today after running camera_i2c tools
pi@raspberrypi:~/MIPI_Camera/RPI $ ./preview-camera0
Open camera...
Found sensor ov9281 at address 60
Setting the resolution...
Can't open the file
mmal: Failed to fix lens shading, use the default mode!
Current resolution is 1280x800
Notice:You can use the list_format sample program to see the resolution and control supported by the camera.
Start preview...
Reset the focus...
Failed to set focus, the camera may not support this control.
Setting the exposure...
Setting the exposure...
Setting the hfilp...
Enable Auto Exposure...
Enable Auto White Balance...
Mono camera does not support automatic white balance.
Setting the resolution...
Can't open the file
mmal: Failed to fix lens shading, use the default mode!
Failed to write register
Current resolution is 2560x800
Stop preview...
Close camera...

[JirkaN1]

It seems, that your camera and rpi is OK.
If are You logged to rpi on ssh, the preview isn't visible, but is projected on hdmi output. This is normal state.

[Ninic0c0]

Hi @JirkaN1,
I have already an HDMI display connected and no camera output...

Could you please share the result of :
$ ls /dev/video*

[JirkaN1]

video10 video11 video12
Try capture a image using capture_raw, the file must have 1024000Bytes.

[glddiv]

Hi @Ninic0c0
Sorry for the late reply.

More info today after running camera_i2c tools
pi@raspberrypi:~/MIPI_Camera/RPI $ ./preview-camera0

Can you show me the output of the camera_i2c script?

[glddiv]

Hi @JirkaN1
Sorry for the late reply.

cant't capture faster than cca 60fps, it seems, that run only one lane even if is set mode 5. Have the M12 version two lanes @ArduCAM ?

Can you tell me how you tested it?
Try using ./arducamstill -t 100000 -m 5 -awb 0 -ae 0 , which will display the correct frame rate

Some MMAL components can't work at such a fast speed, so you can't reach this speed when using some features.

[JirkaN1]

Hi @glddiv ,
Yes, I have tested the arducamstill yesterday, it use a raw_callback function for fps test and give me the the same result 145fps. (in sensor datasheet is 120fps as maximum)
But if I make a fast loop with use arducam_capture repeatedly, acquire raws and save them to ramdrive (or drop to NULL), I got exactly half of the number, 72fps.
This seems, that the sensor capture every second frame. Is here any way to use raw_callback to save raw images, maybe in one file (without sensor stop) aka infinity analog film reel? It can be cutted later.
If I capture 256 8bit frames, convert them to 16bit and then average them to one picture, got the true 16bit image almost without noise. But it must be done as fastest possible, because is possible the scene change in time.
Thank You!

[Ninic0c0]

Hi @glddiv ,

I'm not a work today but have made some modifications in the script : #15

Cheers,

[glddiv]

@Ninic0c0
Thanks, it looks like a new Raspberry Pi 4 ,I didn't see it in the Raspberry Pi revision codes, I will check it out.

[glddiv]

@JirkaN1
arducam_capture is designed to get the latest frame and it doesn't read the image from the cache, so if you call arducam_capture not fast enough, you will lose some frames.
If you don't want this effect, you can use raw_callback, but if you don't handle it fast enough in the callback, it will affect the overall speed.