veyeimaging/raspberrypi_v4l2

raspberrypi_v4l2's Issues

No 5.10.52-v7l+ file issue

The error while sudo ./install_driver.sh veye327:
install: cannot stat './driver_bin/5.10.52-v7l+/veye327.dtbo': No such file or directory

Code will not install on the default newest Raspberry Pi image

I notice that this code will not install on the currently available Raspberry Pi image, or any image higher than kernel of 5.15.74 v7+. I am not smart enough to know how to compile for a kernel, so I looked for an older image that this software would be compatible with. Hopefully this helps others with the same issue.

Older image from 04/22 https://downloads.raspberrypi.org/raspios_full_armhf/images/raspios_full_armhf-2022-04-07/

some better instructions are located here: https://spotpear.com/index/study/detail/id/754.html

using the above, I was quickly able to get my camera to work properly, after an hour or two of fiddling with prior to figuring out I needed an older image.

Compile warnings

For reference, a few warnings during compilation.

  CC [M]  drivers/media/i2c/csimx307.o
drivers/media/i2c/csimx307.c: In function 'csimx307_stop_streaming':
drivers/media/i2c/csimx307.c:620:6: warning: unused variable 'ret' [-Wunused-variable]
  620 |  int ret;
      |      ^~~
drivers/media/i2c/csimx307.c:619:21: warning: unused variable 'client' [-Wunused-variable]
  619 |  struct i2c_client *client = v4l2_get_subdevdata(&csimx307->sd);
      |                     ^~~~~~

Error installing on RPi4

Why is exposure and other controls commented in the source code?

Hello,

I'm trying to connect the camera to INDI Library for Astrophotography and it warns about lack of features (exposure).

So I dig in the source code and found code with #if 0 and return statements.

raspberrypi_v4l2/driver_source/cam_drv_src/rpi-5.x_all/veye327.c

Line 737 in 2443c50

#if 0

raspberrypi_v4l2/driver_source/cam_drv_src/rpi-5.x_all/veye327.c

Line 285 in 2443c50

return 0;

Is it possible to uncomment them and recompile again using a Raspberry PI 4b?... I'll give it a try.

Error on RPi4

installing now worked, but I get the following error:

pi@raspberrypi:~ $ dmesg | grep veye
[ 5.708555] veye327: disagrees about version of symbol module_layout
[ 5.728882] veye327: disagrees about version of symbol module_layout
[ 5.749376] veye327: disagrees about version of symbol module_layout
[ 31.834579] veye327_vddl: disabling
[ 31.834601] veye327_vdig: disabling
[ 31.834626] veye327_vana: disabling

Error installing on Raspberry PI Zero W

Hello, perhaps the folder naming is not correct on driver_bin.

pi@raspberrypi:~/raspberrypi_v4l2/release $ sudo ./install_driver.sh veye327

usage: sudo ./install_driver.sh veye327/csimx307/cssc132

Enable i2c0 adapter...

Add dtoverlay=veye327 to /boot/config.txt

Add gpu=400M to /boot/config.txt
Add cma=128M to /boot/cmdline.txt

Installing the veye327.ko driver

install: cannot stat './driver_bin/5.4.83+/veye327.ko': No such file or directory
install: cannot stat './driver_bin/5.4.83+/veye327.dtbo': No such file or directory
reboot now?(y/n):

Error installing on RPi4

Can you help me? why does it seem to be looking for an old version of the kernel?

---

usage: sudo ./install_driver.sh veye327/csimx307/cssc132

Enable i2c0 adapter...

Add dtoverlay=veye327 to /boot/config.txt

Add gpu=400M to /boot/config.txt
Add cma=128M to /boot/cmdline.txt

Installing the veye327.ko driver

install: cannot stat './driver_bin/4.19.118-v7l+/veye327.ko': No such file or directory
install: cannot stat './driver_bin/4.19.118-v7l+/veye327.dtbo': No such file or directory
reboot now?(y/n):

What to do with drivers after compilation on Raspberry?

The "Building Locally" chapter ended unexpectedly. I have compile drivers and dts. What next?

Installation/Compilation fails on 64bit kernel

It seems the newest Raspberry Pi OS 32bit versions use the 64bit kernel but the v8+/build directory is missing, so I had to add arm_64bit=0 to /boot/config.txt and reboot so that the v7l+/build directory is used. As said here.
I think it would be helpful to add some hint for this in the README?