What I mean now is to install libcamera0 of arducam, and then install the apps of Raspberry Pi
@Edward, how do I install just libcamera0 from you? I reverted libcamera to the original I believe
$ dpkg -l | grep libcamera ii libcamera-apps 0~git20230301+54a781d-1 armhf libcamera-apps ii libcamera-dev:armhf 0~git20230302+923f5d70-1 armhf complex camera support library (development files) ii libcamera0:armhf 0~git20230302+923f5d70-1 armhf complex camera support library
And now I can do:
$ libcamera-still --list-cameras Available cameras ----------------- 0 : imx519 [4656x3496] (/base/soc/i2c0mux/i2c@1/imx519@1a) Modes: 'SRGGB10_CSI2P' : 1280x720 [120.02 fps - (1048, 1042)/2560x1440 crop] 1920x1080 [60.00 fps - (408, 674)/3840x2160 crop] 2328x1748 [30.00 fps - (0, 0)/4656x3496 crop] 3840x2160 [21.01 fps - (408, 672)/3840x2160 crop] 4656x3496 [10.00 fps - (0, 0)/4656x3496 crop]
libcamera-hello still fails. Is it because of original libcamera0?
$ libcamera-hello Preview window unavailable [0:12:57.160444099]  INFO Camera camera_manager.cpp:299 libcamera v0.0.4+22-923f5d70 [0:12:57.342232538]  INFO RPI raspberrypi.cpp:1476 Registered camera /base/soc/i2c0mux/i2c@1/imx519@1a to Unicam device /dev/media3 and ISP device /dev/media0 [0:12:57.347175496]  INFO Camera camera.cpp:1028 configuring streams: (0) 2328x1748-YUV420 [0:12:57.349988472]  INFO RPI raspberrypi.cpp:851 Sensor: /base/soc/i2c0mux/i2c@1/imx519@1a - Selected sensor format: 2328x1748-SRGGB10_1X10 - Selected unicam format: 2328x1748-pRAA [0:12:57.387134153]  WARN IPARPI raspberrypi.cpp:801 Could not set AF_MODE - no AF algorithm Segmentation fault
./install_pivariety_pkgs.sh -p libcamera0
reinstalls libcamera-dev automatically to the arducam one as well breaking everything again. So now I have:
$ dpkg -l | grep libcamera ii libcamera-apps 0~git20230301+54a781d-1 armhf libcamera-apps ii libcamera-dev:armhf 0~git20230321+74d023d8-1 armhf complex camera support library (development files) ii libcamera0:armhf 0~git20230321+74d023d8-1 armhf complex camera support library ii python3-libcamera 0~git20230302+923f5d70-1 armhf complex camera support library (Python 3 bindings)
Is it still not working?
Well, next week I’ll sort things out in unison
Now I believe I have
libcamera-apps original and
libcamera0 from arducam.
Illegal operation is back.
That is the raspberry pi official has the same problem. This is because the arm version is too low.
I’ll look at this question next week
There is another way to open the camera
There will be an interface, you can try to get the camera working first, next week I will try to compile a working version.
qcam right now, I have only
Lite OS installed, no UI.
This is because the arm version is too low.
Isn’t there a quick magic trick for this? boot/config.txt settings? Btw. it doesn’t happen with a different camera type.
@Edward I very appreciate your prompt replies!
Just tried qcam, same issue as running libcamera-hello
@LoKau Have you tried the original libcamera and do you get the same result as I do? Thinking the underlying cause is the same for both of us.
@jhud, Ill try it this week-end, ill let you know in the next days.
I uninstalled arducam libcamera-apps, then I installed the raspberry one → illegal instruction
Finally I installed again libcamera0 from the pivariety_pkgs → same issue.
@Edward , keep us informed this week plz
I was dealing with some urgent issues the last two days.
Please don’t worry, I have arranged this test for today.
Thanks but unfortunately no change.
$ dpkg -l | grep libcamera ii libcamera-apps 0~git20230309+4def288-1 armhf libcamera-apps ii libcamera-dev:armhf 0~git20230321+74d023d8-1 armhf complex camera support library (development files) ii libcamera0:armhf 0~git20230321+74d023d8-1 armhf complex camera support library ii python3-libcamera 0~git20230302+923f5d70-1 armhf complex camera support library (Python 3 bindings) $ sudo apt install ./libcamera-apps_0_git20230309+4def288-1_armhf.deb Reading package lists... Done Building dependency tree... Done Reading state information... Done Note, selecting 'libcamera-apps' instead of './libcamera-apps_0_git20230309+4def288-1_armhf.deb' The following packages will be upgraded: libcamera-apps 1 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. Need to get 0 B/300 kB of archives. After this operation, 0 B of additional disk space will be used. Get:1 /home/pi/libcamera-apps_0_git20230309+4def288-1_armhf.deb libcamera-apps armhf 0~git20230309+4def288-1 [300 kB] Reading changelogs... Done (Reading database ... 59271 files and directories currently installed.) Preparing to unpack .../libcamera-apps_0_git20230309+4def288-1_armhf.deb ... Unpacking libcamera-apps (0~git20230309+4def288-1) over (0~git20230309+4def288-1) ... Setting up libcamera-apps (0~git20230309+4def288-1) ... Processing triggers for libc-bin (2.31-13+rpt2+rpi1+deb11u5) ... $ libcamera-hello Preview window unavailable [0:25:50.330955891]  INFO Camera camera_manager.cpp:299 libcamera v0.0.0+4225-74d023d8 Illegal instruction
Note I installed
libcamera-apps_0_git20230309+4def288-1_armhf.deb instead of
libcamera-apps_0~git20230309+4def288-1_armhf.deb that you linked but it’s the same thing.
~ was replaced by
- when downloading through Windows.
It’s not easy for me to debug without hardware support.
So i am applying for a new Raspberry Pi Zero
If it goes well maybe I’ll get the hardware next week.
Thanks @Edward. I’m thinking if there’s something I can do to debug myself. I understand there’s no guarantee you get access to RPI Zero, right?
It hasn’t been mentioned but I assume from the context here that Arducam, as a company, doesn’t know if the camera is supposed to work with RPI Zero (1.3 in my case) or not, correct? The shop I bought it from claims it’s compatible with ALL RPIs which may be wrong information. I find it hard to believe I’m the only one trying to do so for the first time. And so I’m also trying to rule out a possibility that I just have a faulty camera.
@Edward, same question for my 1B+ model.
I agree that it is quite old but I don’t think I’m the only one using this device.
First of all I would like to express my apologies.
This is indeed a known issue and we have addressed similar issues before. We thought that the official solved this problem permanently, so we didn’t treat these devices specially. Now it seems that the problem has appeared again, so I need to solve it again, and release a special version.
Now I’ve purchased the hardware, but it hasn’t arrived yet.
If you are willing to give me some patience, I will also be responsible to the end.
Thank you for the update. I’ll wait more and will ask the seller if they’re ok me possibly returning the camera later. But hoping you’ll make it to work.
Re the problem. I have no technical insight into it but as a different camera works fine, this must be specific somehow to your cam, correct?