The new mgain is stuck at zero, so if i use new exp mode i can set the shutter speed with new mshutter, but not the new mgain, despite changing it returns zero when i probe with the -r parameter. so using the new exp mode i only get a black image.

the old mshutter works and i was able go get up to 1 second exposure per frame in streaming mode but the capture mode and capture command don't seem to work.

Also i would like to have it work in the rpi archlinux OS that i use for astronomy. The veyecam2m driver works and i get video in the archlinux OS, but i wasn't able to compile the i2c read and write in that system.

i2c_read.c: In function ‘main’:
i2c_read.c:112:42: error: passing argument 4 of ‘i2c_rd’ from incompatible pointer type [-Wincompatible-pointer-types]
  112 |         i2c_rd(fd, device_addr,reg_addr, &value, num);
      |                                          ^~~~~~
      |                                          |
      |                                          unsigned char (*)[512]
i2c_read.c:20:68: note: expected ‘unsigned char *’ but argument is of type ‘unsigned char (*)[512]’
   20 | static int i2c_rd(int fd, uint8_t i2c_addr, uint16_t reg, uint8_t *values, uint32_t n)

~ » dmesg | grep veye 1 ↵ ```
[ 0.029025] /axi/pcie@1000120000/rp1/i2c@80000/veyecam2m@3b: Fixed dependency cycle(s) with /axi/pcie@1000120000/rp1/csi@128000
[ 0.029038] /axi/pcie@1000120000/rp1/i2c@88000/veyecam2m@3b: Fixed dependency cycle(s) with /axi/pcie@1000120000/rp1/csi@110000
[ 0.029063] /axi/pcie@1000120000/rp1/csi@110000: Fixed dependency cycle(s) with /axi/pcie@1000120000/rp1/i2c@88000/veyecam2m@3b
[ 0.029073] /axi/pcie@1000120000/rp1/csi@128000: Fixed dependency cycle(s) with /axi/pcie@1000120000/rp1/i2c@80000/veyecam2m@3b
[ 0.029230] /axi/pcie@1000120000/rp1/i2c@80000/veyecam2m@3b: Fixed dependency cycle(s) with /axi/pcie@1000120000/rp1/csi@128000
[ 0.029243] /axi/pcie@1000120000/rp1/i2c@88000/veyecam2m@3b: Fixed dependency cycle(s) with /axi/pcie@1000120000/rp1/csi@110000
[ 0.029270] /axi/pcie@1000120000/rp1/csi@110000: Fixed dependency cycle(s) with /axi/pcie@1000120000/rp1/i2c@88000/veyecam2m@3b
[ 0.029280] /axi/pcie@1000120000/rp1/csi@128000: Fixed dependency cycle(s) with /axi/pcie@1000120000/rp1/i2c@80000/veyecam2m@3b
[ 1.119276] /axi/pcie@1000120000/rp1/i2c@80000/veyecam2m@3b: Fixed dependency cycle(s) with /axi/pcie@1000120000/rp1/csi@128000
[ 1.119698] /axi/pcie@1000120000/rp1/i2c@88000/veyecam2m@3b: Fixed dependency cycle(s) with /axi/pcie@1000120000/rp1/csi@110000
[ 1.120359] /axi/pcie@1000120000/rp1/i2c@88000/veyecam2m@3b: Fixed dependency cycle(s) with /axi/pcie@1000120000/rp1/csi@110000
[ 1.120705] /axi/pcie@1000120000/rp1/csi@110000: Fixed dependency cycle(s) with /axi/pcie@1000120000/rp1/i2c@88000/veyecam2m@3b
[ 1.121105] /axi/pcie@1000120000/rp1/i2c@80000/veyecam2m@3b: Fixed dependency cycle(s) with /axi/pcie@1000120000/rp1/csi@128000
[ 1.121461] /axi/pcie@1000120000/rp1/csi@128000: Fixed dependency cycle(s) with /axi/pcie@1000120000/rp1/i2c@80000/veyecam2m@3b
[ 4.419673] /axi/pcie@1000120000/rp1/csi@128000: Fixed dependency cycle(s) with /axi/pcie@1000120000/rp1/i2c@80000/veyecam2m@3b
[ 4.419961] /axi/pcie@1000120000/rp1/i2c@80000/veyecam2m@3b: Fixed dependency cycle(s) with /axi/pcie@1000120000/rp1/csi@128000
[ 4.446956] /axi/pcie@1000120000/rp1/csi@110000: Fixed dependency cycle(s) with /axi/pcie@1000120000/rp1/i2c@88000/veyecam2m@3b
[ 4.446999] /axi/pcie@1000120000/rp1/i2c@88000/veyecam2m@3b: Fixed dependency cycle(s) with /axi/pcie@1000120000/rp1/csi@110000
[ 4.562519] rp1-cfe 1f00110000.csi: found subdevice /axi/pcie@1000120000/rp1/i2c@88000/veyecam2m@3b
[ 4.600108] rp1-cfe 1f00128000.csi: found subdevice /axi/pcie@1000120000/rp1/i2c@80000/veyecam2m@3b
[ 4.829476] veyecam2m: loading out-of-tree module taints kernel.
[ 4.837008] veyecam2m 11-003b: Unable to load ds90ub954 driver,will go on
[ 4.945847] veyecam2m 11-003b: probe failed
[ 4.965628] veyecam2m 10-003b: Unable to load ds90ub954 driver,will go on
[ 5.078216] veyecam2m 10-003b: camera id is veyecam2m
[ 5.080221] veyecam2m 10-003b: sensor is IMX327
[ 5.080580] veyecam2m 10-003b: board type is ONE board
[ 5.081367] rp1-cfe 1f00110000.csi: Using sensor veyecam2m 10-003b for capture
[ 5.108106] veyecam2m 10-003b: veyecam2m camera probed

i already tried the ./veye_mipi_i2c.sh with the -b set to 10, 11, 6, 4 and 0. all give the same results.

dmesg | grep veye

This can reveal which specific I2C bus your camera is on.

~/raspberrypi/i2c_cmd/bin (master*) » ./veye_mipi_i2c.sh -b 11 -r -f hdver
hardware version is 0xff
release date is 20ff-ff-ff

I was able to set new expmode to manual:
~/raspberrypi/i2c_cmd/bin (master*) » ./veye_mipi_i2c.sh -r -f new_expmode
r new expmode is manual, use new_mshutter and new_mgain

But when i try to set the new_mshutter i get:
~/raspberrypi/i2c_cmd/bin (master*) » ./veye_mipi_i2c.sh -b 10 -w -f new_mshutter -p1 1000

awk: cmd. line:1: (FILENAME=- FNR=1) fatal: division by zero attempted
./veye_mipi_i2c.sh: line 1290: [: -gt: unary operator expected
./veye_mipi_i2c.sh: line 1294: >>8: arithmetic syntax error: operand expected (error token is ">>8")

1. If you are using the v4l2 driver mode, camera_i2c_config is not required.
2. When running ./veye_mipi_i2c.sh, make sure to specify the I2C bus you are using with the -b parameter.

Below is an explanation regarding the I2C bus.
https://wiki.veye.cc/index.php/I2c_bus_number_and_video_node
For long exposure usage, you may need to configure the lowlight function or the new_mshutter function. Please refer to the corresponding section in the link below.
https://wiki.veye.cc/index.php/VEYE-MIPI-290/327_i2c/#new_mshutter

and get:

~ » v4l2-ctl -d /dev/v4l-subdev2 -l

Image Processing Controls

pixel_rate 0x009f0902 (int64) : min=74250000 max=74250000 step=1 default=74250000 value=74250000 flags=read-only