Problem with GXC-MIPI-IMX662

alex_ai

Hi @veye_xumm,
As I wrote - camera is static, no vibration. Turning off of 3D Noise Reduction didn't help. I also tried with test image - it also has this issue on the last line at the bottom of frame (see attached renamed to txt video file)
test_2x264.mp4.txt

veye_xumm

@alex_ai

I believe the issue does not lie with the camera output, but rather with the compression process after you receive the data. Please verify this using the client software available at the link below. The veye_viewer client is designed to preview raw grey format data directly, without applying any compression.

https://github.com/veyeimaging/veye_viewer

alex_ai

@veye_xumm said:

veye_viewer

Hi @veye_xumm, all videos captured from veye_viewer (you can see it on first video)

veye_xumm

@alex_ai Sorry, I misunderstood your setup. I've verified this on other boards, including Jetson, and it works fine. I now believe the issue is caused by image scaling in the veye_viewer client software on the latest Raspberry Pi OS. We'll fix this as soon as possible — please bear with us.

veye_xumm

@alex_ai
Good news — I've found a solution to the issue. The camera's MIPI signal needs to be switched to continuous clock (non-discontinuous) mode. You can do this by running the following command: https://wiki.veye.cc/index.php/Gx_mipi_i2c.sh_user_guide#nondiscontinuousmode — or alternatively by setting register 0x44c in veye_viewer.
After making the change, please use the paramsave command to save the settings to the camera.

alex_ai

Hi @veye_xumm
I tried to set value to 1

rms@raspberrypi10:~/source/raspberrypi_v4l2/gx_i2c_tools $ ./gx_mipi_i2c.sh -r nondiscontinuousmode -b 6
Read Nondiscontinuous_mode is 1

But when click "Start Show" - no video in veye_viewer (same as in python) just nothing happened (it works when back value to 0)

Maybe need also change some another parameter?

veye_xumm

@alex_ai

@alex_ai said:

./gx_mipi_i2c.sh -r nondiscontinuousmode -b 6

use -w, not -r.
-w means write.

veye_xumm

@alex_ai
No need to set it up manually anymore! We've updated the driver, so just grab the latest code, compile it, and install it.
https://github.com/veyeimaging/raspberrypi_v4l2

alex_ai

@veye_xumm said:

use -w, not -r.

Yes, I know, I just wanted to confirm that nondiscontinuousmode is set to 1 :

Read Nondiscontinuous_mode is 1

I installed new driver and no differences - no video for value 1

My PiOs : 6.18.39+rpt-rpi-2712
dmesg log:

[    2.624024] gxcam 10-003b: veye gx series camera driver version: 01.00.04
[    2.624247] gxcam 10-003b: no reset gpio provided
[    2.685103] gxcam 10-003b: camera is: GXC-MIPI-IMX662
[    2.688265] gxcam 10-003b: VideoModeCap: 0x2
[    2.706466] gxcam 10-003b: gxcam_enum_controls success

example of veye_viewer and no video

veye_xumm

@alex_ai
Register 0x44c should indeed be configured to 1.
This is quite strange, as the image preview works perfectly on our end with the exact same configuration.

Are you viewing the image via remote desktop?
Under the same conditions, does setting register 0x44c to 0 produce an image (with jitter), while setting it to 1 results in no image at all?

alex_ai

@veye_xumm said:

Are you viewing the image via remote desktop?

yes, also just tried with hdmi - same

@veye_xumm said:

Under the same conditions, does setting register 0x44c to 0 produce an image (with jitter), while setting it to 1 results in no image at all?

yes, it works if set 0 with jitter and no image with value 1, I recorded video to demo

test_3x264.mp4.txt

alex_ai

Just tried to run it on Rpi4 (bookworm 6.12)
It is same: no image for setting 1 but for 0 - no jitter!

Probably this issue only for Rpi5 (trixie 6.18).

Not sure how it works for you with value 1, I tested on 2 devices and it same no image for value 1

veye_xumm

@alex_ai
Since the MIPI CSI issue does not occur on our Raspberry Pi 5 setup but occurs on your system, we suspect it may be related to firmware versions or hardware initialization rather than the Linux version itself. However, this still needs to be verified.

On Raspberry Pi 5, we recommend comparing the following firmware versions and system information between the working and failing systems:

RP1 firmware version

dmesg | grep 'RP1 Firmware version'

VideoCore firmware version

vcgencmd version

EEPROM bootloader version

vcgencmd bootloader_version

Kernel version

uname -a

Please send us the outputs of these commands so we can compare the two systems.

The output from my Raspberry Pi 5 is as follows:

pi@raspberrypi:~ $ dmesg | grep 'RP1 Firmware version'
[   10.187794] rp1-firmware rp1_firmware: RP1 Firmware version 23fca1cd776798b50bd3e640ecb242215778e7f8

pi@raspberrypi:~ $ vcgencmd version
2025/11/05 17:37:18
Copyright (c) 2012 Broadcom
version 57db150d (release) (embedded)

pi@raspberrypi:~ $ vcgencmd bootloader_version
2025/11/05 17:37:18
version 57db150d63864d47e6c9071f6b086a5401eb4e92 (release)
timestamp 1762364238
update-time 1762994706
capabilities 0x0000007f

pi@raspberrypi:~ $ uname -a
Linux raspberrypi 6.18.50+rpt-rpi-2712 #1 SMP PREEMPT Debian 1:6.18.50-1+rpt1 (2026-09-11) aarch64 GNU/Linux

pi@raspberrypi:~ $ dmesg | grep 'Attached to firmware from'
[    0.021083] raspberrypi-firmware soc@107c000000:firmware: Attached to firmware from 2025-11-05T17:37:18, variant start_cd