Camera module 3 support ? #228

ABelliqueux · 2024-01-10T14:23:58Z

Is the Camera module 3 (imx708) supported ?
If not, is it planned ?

kbingham · 2024-01-10T14:40:26Z

showmewebcam presently uses the legacy camera stack from Raspberry Pi. The legacy camera stack can not operate the IMX708.

We have done work to update showmewebcam to the new libcamera stack, but the performances are low - as presently it uses a software encoder. There is a hardware encoder available on the Pi0-2, but the work we have done needs to be extended to make use of that.

I successfully use the IMX708 with the software encoder on an RPi0-2W - but it's not likely to work well at all on an RPi0.

So - 'planned' yes - if someone can dedicate the time to help support this, and there's even preliminary work already functional. It needs someone to work on it.

#197

ABelliqueux · 2024-01-10T14:49:13Z

Thanks for your reply.

I'm trying to use a RPI 4B, do you think I could use the software encoder on that ?
By low performance, you mean low framerate I suppose ?

If so, is there an artifact/img I can get to test it ? Otherwise, I think I have to follow https://github.com/showmewebcam/showmewebcam/tree/buildroot-update#development--building but switch to the buildroot-update branch before building, right ?

kbingham · 2024-01-10T15:29:44Z

Yes, it should work on a Pi4B with the software encoder. The hardware encoder can also be developed on there once you get started. You'll have to self build at the moment I'm afraid.

ABelliqueux · 2024-01-11T09:33:44Z

Ok, tried to build but got :

../output/raspberrypi4/build/libcamera-ab72e6641c56e876f91edee57a8969982a3ab9b7/include/libcamera/meson.build:84:25: ERROR: Index 2 out of bounds of array of size 2.

which in output/raspberrypi4/build/libcamera-ab72e6641c56e876f91edee57a8969982a3ab9b7/include/libcamera/meson.build, l.80-84 corresponds to

# version.h
version = libcamera_version.split('.')
libcamera_version_config = configuration_data()
libcamera_version_config.set('LIBCAMERA_VERSION_MAJOR', version[0])
libcamera_version_config.set('LIBCAMERA_VERSION_MINOR', version[1])
libcamera_version_config.set('LIBCAMERA_VERSION_PATCH', version[2])

so my guess is that libcamera_version is that the currently used libcamera version is only 2 chars long (x.y) instead of three (x.y.z)...

After some investigation, it looks like libcamera_version is sourced via the utils/gen-version.sh script, l.13:

version=$(git describe --abbrev=8 --match "v[0-9]*" 2>/dev/null)

which when ran manually yields :

v1.91-10-g54cad4ee

which does not conform to the pattern described in meson.build : e.g. 1.2.3+211-c94a24f4 .

So that explains why the split() method only returns a 2 items long array instead of 3.

dgsiegel · 2024-01-11T10:07:36Z

Any hint ?

What Buildroot version are you using? In #197 I didn't set any version for libcamera and it builds just fine.

ABelliqueux · 2024-01-11T10:17:35Z

@dgsiegel :
See my updated message above for more infos.

About buildroot version how do I find out ?

All I did was :

git clone --recurse-submodules https://github.com/showmewebcam/showmewebcam.git
git checkout buildroot-update
./build-showmewebcam.sh raspberrypi4

dgsiegel · 2024-01-11T10:50:11Z

About buildroot version how do I find out ?

Buildroot is a submodule in this repo, so you'd find out the current version via git. It might make sense to update to a newer version though, see my linked PR.

After some investigation, it looks like libcamera_version is sourced via the utils/gen-version.sh script, l.13:

version=$(git describe --abbrev=8 --match "v[0-9]*" 2>/dev/null)

which when ran manually yields :

v1.91-10-g54cad4ee

which does not conform to the pattern described in meson.build : e.g. 1.2.3+211-c94a24f4 .

Ah yeah, I remember running into this problem as well. v1.91-10-g54cad4ee is the showmewebcam version and is set via Buildroot. Libcamera thinks this is their version string too and breaks. I think this was fixed in more recent libcamera builds, and hence upgrading Buildroot should solve that.

ABelliqueux · 2024-01-11T15:51:54Z

Ok, I'm getting further along the way. Here is what I did :

git clone --recurse-submodules https://github.com/showmewebcam/showmewebcam.git
cd showmewebcam
git checkout buildroot-update
cd buildroot 
git checkout 8cca1e
cd ..
./build-showmewebcam.sh raspberrypi4

I am now encountering a new issue :

bench.c: In function 'LZ4F_decompress_binding':
bench.c:324:37: warning: missing braces around initializer [-Wmissing-braces]
  324 |     LZ4F_decompressOptions_t dOpt = { 1, 0, 0, 0 };
      |                                     ^
      |                                          {       }
bench.c:326:9: error: 'LZ4F_decompressOptions_t' has no member named 'skipChecksums'
  326 |     dOpt.skipChecksums = g_skipChecksums;
      |         ^
make[3]: *** [<builtin>: bench.o] Error 1
make[2]: *** [Makefile:63: lz4] Error 2
make[1]: *** [package/pkg-generic.mk:293: /home/arthus/build/showmewebcam/output/raspberrypi4/build/host-lz4-1.9.4/.stamp_built] Error 2
make: *** [Makefile:23: _all] Error 2

Do you have a specific hash commit for buildroot that I should use ?

dgsiegel · 2024-01-11T16:13:30Z

Do you have a specific hash commit for buildroot that I should use ?

In #197 I've used Buildroot 2023.02: d467a38

I guess you could use any newer stable Buildroot release.

ABelliqueux · 2024-01-11T16:52:02Z

Yes, that's the one I'm currently trying to use (commit 8cca1e) but I now have a new error coming up :

extend.texi:2490: @itemx should not begin @table
make[3]: *** [Makefile:3385: doc/gcc.info] Error 1
make[3]: *** Waiting for unfinished jobs....
In file included from ../../gcc/spellcheck-tree.h:23,
                 from ../../gcc/c/c-decl.c:55:
In member function 'edit_distance_t best_match<GOAL_TYPE, CANDIDATE_TYPE>::get_cutoff(size_t) const [with GOAL_TYPE = tree_node*; CANDIDATE_TYPE = tree_node*]',
    inlined from 'best_match<GOAL_TYPE, CANDIDATE_TYPE>::candidate_t best_match<GOAL_TYPE, CANDIDATE_TYPE>::get_best_meaningful_candidate() const [with GOAL_TYPE = tree_node*; CANDIDATE_TYPE = tree_node*]' at ../../gcc/spellcheck.h:175:38,
    inlined from 'name_hint lookup_name_fuzzy(tree, lookup_name_fuzzy_kind, location_t)' at ../../gcc/c/c-decl.c:4405:48:
../../gcc/spellcheck.h:162:39: warning: 'bm.best_match<tree_node*, tree_node*>::m_best_candidate_len' may be used uninitialized [-Wmaybe-uninitialized]
  162 |     return ::get_edit_distance_cutoff (m_goal_len, candidate_len);
      |            ~~~~~~~~~~~~~~~~~~~~~~~~~~~^~~~~~~~~~~~~~~~~~~~~~~~~~~
../../gcc/c/c-decl.c: In function 'name_hint lookup_name_fuzzy(tree, lookup_name_fuzzy_kind, location_t)':
../../gcc/c/c-decl.c:4311:26: note: 'bm.best_match<tree_node*, tree_node*>::m_best_candidate_len' was declared here
 4311 |   best_match<tree, tree> bm (name);
      |                          ^~
/bin/sh ../../gcc/../move-if-change tmp-automata.c insn-automata.c
echo timestamp > s-automata
/bin/sh ../../gcc/../move-if-change tmp-attrtab.c    insn-attrtab.c
/bin/sh ../../gcc/../move-if-change tmp-dfatab.c     insn-dfatab.c
/bin/sh ../../gcc/../move-if-change tmp-latencytab.c insn-latencytab.c
echo timestamp > s-attrtab
make[2]: *** [Makefile:4427: all-gcc] Error 2
make[1]: *** [package/pkg-generic.mk:293: /home/arthus/build/showmewebcam/output/raspberrypi4/build/host-gcc-initial-11.3.0/.stamp_built] Error 2
make: *** [Makefile:23: _all] Error 2

This one is quite obscure and I think that's where I'll stop trying. Thanks for your time and answers though!

kbingham · 2024-01-12T10:56:05Z

That looks like errors building GCC ... which is buildroots responsibility. I would suspect it needs buildroot updating to a more recent version. If this is a bug exposed by buildroot. They would have already fixed it.

ABelliqueux · 2024-01-12T15:23:56Z

Finally got it working after switching to buildroot 2023.08 :

So here are the final steps to get it built :

git clone --recurse-submodules https://github.com/showmewebcam/showmewebcam.git
cd showmewebcam
git checkout buildroot-update
cd buildroot 
git checkout 2023.08
cd ..
./build-showmewebcam.sh raspberrypi4

Testing the resulting image right now :)

Thanks again to both of you.

Should I edit the issue's title to reflect the main discussion ?

kbingham · 2024-01-12T15:35:49Z

Excellent! Keep us posted. I'll help where ever I can.

ABelliqueux · 2024-01-12T15:44:44Z

It boots fine but doesn't seem to have the imx708 driver, are there some steps I missed ?

In /boot/overlays, there is no imx708.dtbo file and no module with that name either in /lib/modules/5.10.92-v7l/kernel/drivers/media/i2c/... How would I go about adding it ?

Here are some logs :

$ cam -l
[0:12:01.248106680] [272]  INFO Camera camera_manager.cpp:298 libcamera v1.91+23-a5116c27-dirty (2024-01-12T15:51:32+01:00)
Available cameras:

$ v4l2-ctl --list-devices
bcm2835-codec-decode (platform:bcm2835-codec):
        /dev/video10
        /dev/video11
        /dev/video12
        /dev/video18
        /dev/media1

bcm2835-isp (platform:bcm2835-isp):
        /dev/video13
        /dev/video14
        /dev/video15
        /dev/video16
        /dev/video20
        /dev/video21
        /dev/video22
        /dev/video23
        /dev/media0
        /dev/media2

Cannot open device /dev/video0, exiting.

$ journalctl -u uvc-webcam.service 
Jul 28 08:26:33 piwebcam systemd[1]: Started Starts Raspberry Pi UVC webcam serv
Jul 28 08:26:33 piwebcam piwebcam[219]: One video device is missing, will not st
Jul 28 08:26:33 piwebcam systemd[1]: uvc-webcam.service: Main process exited, co
Jul 28 08:26:33 piwebcam systemd[1]: uvc-webcam.service: Failed with result 'exi

kbingham · 2024-01-12T16:50:31Z

In /boot/overlays, there is no imx708.dtbo file and no module with that name either in /lib/modules/5.10.92-v7l/kernel/drivers/media/i2c/... How would I go about adding it ?

A 5.10 kernel is likely far too old. It needs to be updated to the point that Raspberry Pi added the IMX708. The current raspberry pi kernel should either by rpi-6.1-y or rpi-6.6-y.

[0:12:01.248106680] [272] INFO Camera camera_manager.cpp:298 libcamera v1.91+23-a5116c27-dirty (2024-01-12T15:51:32+01:00)

And along with that - libcamera would likely need to be updated as well, but with the versioning bug - I can't tell what version of libcamera is being used there.

ABelliqueux · 2024-01-12T18:02:01Z

Ok, so after looking at 225 and #223, I modified a few things :

rpi-firmware > 83dafbc

Replace files in buildroot/package/rpi-firmware with those :

https://github.com/buildroot/buildroot/tree/master/package/rpi-firmware

rpi-linux (kernel) > 6.1

In configs/config :

BR2_LINUX_KERNEL_CUSTOM_TARBALL_LOCATION="$(call github,raspberrypi,linux,a984fda6b2c24dbf1ca21924f99c8f9418f5765e)/linux-a984fda6b2c24dbf1ca21924f99c8f9418f5765e.tar.gz"
# Linux headers same as kernel
BR2_PACKAGE_HOST_LINUX_HEADERS_CUSTOM_6_1=y

libcamera (v0.0.5 > 0.1.0)

Replace files in buildroot/package/libcamera with those :

https://github.com/buildroot/buildroot/tree/master/package/libcamera

bootcode packaging

Add BR2_PACKAGE_RPI_FIRMWARE_BOOTCODE_BIN=y to configs/raspberrypi4.

Rebuild

Not sure if the doc (https://github.com/showmewebcam/showmewebcam/wiki/Development-guide#sample-scenario-uprevving-uvc-gadget) is up to date but running BOARDNAME=raspberrypi4 make -C "output/$BOARDNAME" rpi-firmware-rebuild from showmewebcam or showmewebcam/buildrootdidn't work for me, so I had to do :

rm -rf output/raspberrypi4

before building everything again. But as the kernel has to be compiled again anyway...

It's building right now 🤞 ...

ABelliqueux · 2024-01-13T11:51:43Z

Well it built fine, but the rpi won't start with that image. All I'm getting is a blinking cursor after the rainbow screen. Not sure how I can find the culprit from here...

The filesystems look ok when accessed via my workstation...

The img file is here fwiw : https://upload.disroot.org/r/HB_nSM95#nKXBwg4/J1jkQ+mvdbOYZeYfhM1c6JVnlFCCZHO9DhM=

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Camera module 3 support ? #228

Camera module 3 support ? #228

ABelliqueux commented Jan 10, 2024

kbingham commented Jan 10, 2024 •

edited

ABelliqueux commented Jan 10, 2024 •

edited

kbingham commented Jan 10, 2024

ABelliqueux commented Jan 11, 2024 •

edited

dgsiegel commented Jan 11, 2024

ABelliqueux commented Jan 11, 2024 •

edited

dgsiegel commented Jan 11, 2024

ABelliqueux commented Jan 11, 2024 •

edited

dgsiegel commented Jan 11, 2024

ABelliqueux commented Jan 11, 2024

kbingham commented Jan 12, 2024

ABelliqueux commented Jan 12, 2024

kbingham commented Jan 12, 2024

ABelliqueux commented Jan 12, 2024 •

edited

kbingham commented Jan 12, 2024

ABelliqueux commented Jan 12, 2024 •

edited

ABelliqueux commented Jan 13, 2024 •

edited

Camera module 3 support ? #228

Camera module 3 support ? #228

Comments

ABelliqueux commented Jan 10, 2024

kbingham commented Jan 10, 2024 • edited

ABelliqueux commented Jan 10, 2024 • edited

kbingham commented Jan 10, 2024

ABelliqueux commented Jan 11, 2024 • edited

dgsiegel commented Jan 11, 2024

ABelliqueux commented Jan 11, 2024 • edited

dgsiegel commented Jan 11, 2024

ABelliqueux commented Jan 11, 2024 • edited

dgsiegel commented Jan 11, 2024

ABelliqueux commented Jan 11, 2024

kbingham commented Jan 12, 2024

ABelliqueux commented Jan 12, 2024

kbingham commented Jan 12, 2024

ABelliqueux commented Jan 12, 2024 • edited

kbingham commented Jan 12, 2024

ABelliqueux commented Jan 12, 2024 • edited

rpi-firmware > 83dafbc

rpi-linux (kernel) > 6.1

libcamera (v0.0.5 > 0.1.0)

bootcode packaging

Rebuild

ABelliqueux commented Jan 13, 2024 • edited

kbingham commented Jan 10, 2024 •

edited

ABelliqueux commented Jan 10, 2024 •

edited

ABelliqueux commented Jan 11, 2024 •

edited

ABelliqueux commented Jan 11, 2024 •

edited

ABelliqueux commented Jan 11, 2024 •

edited

ABelliqueux commented Jan 12, 2024 •

edited

ABelliqueux commented Jan 12, 2024 •

edited

ABelliqueux commented Jan 13, 2024 •

edited