Posts made by veye_xumm

@若兮鱼

1. 你使用的是驱动模式，不需要调用camera_i2c_config
2. 核心问题是i2c_write这个可执行文件无法执行。可能是发布的release版本，与你的系统在可执行文件格式方面兼容性不好。你可以进入source目录下，编译一下。然后重新执行。
   首先可以通过读取devid来确认你的i2c命令通道，veye_mipi_i2c.sh脚本是否正常了。

@alex_ai I used firmware version 1.14 for comparison and did not observe any significant noise changes in gamma mode 1 compared to other modes. Could you provide your specific usage parameters and environment?

@alex_ai Thank you for your feedback; we will look into this issue.

@ouyangxin 你好，你理解的没错，但是我们现在已经取消了对sda模式的支持，所以这上面的讨论已经没有意义了。

@zoldaten looking forward to your good news.

@zoldaten
In the source code of veyecam2m.c, please comment out this function.

Additionally, since you are using the RAW-MIPI-SC132M camera, you only need the mvcam driver and its corresponding dtb.

@alex_ai OK, the GX series and the VEYE series use completely different ISP solutions, so their parameters do not correspond one-to-one. I look forward to your test results.

@zoldaten
As long as you follow the steps and place our driver and DTS files into the Orange Pi source tree, then compile the image according to the official Orange Pi instructions and flash this image onto the board, the VEYE camera driver should appear correctly.

Essentially, this operation just adds the driver to the original standard Orange Pi system. No additional steps are required after flashing the image. I suspect that you may not have fully applied the modifications in all the necessary parts of the source code.

@zoldaten

@zoldaten said in OrangePi cm5-tablet RAW-MIPI-SC132M:

i burned SD with your image provided and there veye presented. what`s the difference ?

Sorry, I misunderstood you earlier. I thought you meant that following the steps to compile wasn't working at all. So, now that you've successfully compiled it, the veyecamera has appeared, correct?

What you should do now is modify the source code of the DTS. For different MIPI interfaces, use different dtsi configurations to set it up for the specific camera or sensor model you want.

@sheko Sorry, I just got back from the Chinese New Year holiday. Regarding using the RAW-MIPI-SC132M on the Raspberry Pi 5, I suggest you primarily refer to this document. It covers driver installation, how to use the V4L2 mode, and methods for previewing using OpenCV.
https://wiki.veye.cc/index.php/Mv_series_camera_appnotes_4_rpi

@zoldaten I noticed you placed the compiled image onto the SD card. This is likely incorrect. You should refer to the official Orange Pi documentation and flash the compiled image to the eMMC storage that comes with the Orange Pi CM5 core board.

Additionally, you might wonder why we compile the camera's dtsi directly into the main dtb instead of building it separately as an overlay. This approach follows the practice recommended by the Orange Pi manufacturer.

@zoldaten
My recommended approach is to set up the system compilation environment following the official OrangePi method, then place our provided dtsi files and drivers into it to compile a new deb package.
Your suggested method might work as well, but I haven't personally tried it.

@alex_ai In the current program, HCG will be automatically enabled when the gain is higher than 26 dB — you can give it a try.

Also, please try turning off the 3D noise reduction.

@nkos

Sorry, regarding the attempt to port the camera to the Radxa Zero 3 + 6.x, we tried to set up the standard build environment but were unable to compile successfully. I posted a question on the Radxa forum, but have not yet received a follow-up response.

As for the method you mentioned to configure our registers, we recommend that you do not use the driver. Instead, please use our mv_mipi_i2c.sh script.

https://wiki.veye.cc/index.php/Mv_mipi_i2c.sh_user_guide

@alex_ai said in GX-MIPI-IMX662 can't save fps parameter:

Anyway it is not critical issue for me.
I'm trying this new GX-MIPI-IMX662 as improved version of VEYE-MIPI-IMX462 for meteors detection and can't configure with same way.
If turn off denoise_strength_3D the video image is very noisy and as in gx_mipi_i2c no feature to read sensor registers, can I ask to you confirm that:
In low light environment ISP enables HCG mode (register FDG_SEL0 0x3030 sets to 0x01) ?
Maybe you have other recommendations like for IMX462 in this post :

The issue where the FPS setting cannot be saved is likely because your module is our first version, and the firmware is not fully refined. You can try restoring the factory default settings and then test again.
https://wiki.veye.cc/index.php/Gx_mipi_i2c.sh_user_guide#factoryparam

The GX series and the VEYE series are completely different. If you would like to manually set the exposure time and gain, that is fully supported as well. Please refer to the section about expmode metime mgainin the following link.

https://wiki.veye.cc/index.php/Gx_mipi_i2c.sh_user_guide

I am currently on the Spring Festival holiday. Maybe replay late.

@xlwvu7mx said in GX-MIPI-IMX662 on RK3588 with Kernel 6.1 - MIPI CSI Errors:

Do you have any recomendations on a FPC cable design? And could you please confirm the 22-pin connector pinout featured on the GX-MIPI-IMX662 Data Sheet page (as I have seen both reset_gpio and pwdn_gpio pins in the driver source code where the page mentions only PWR_ENABLE).

Sorry, I am currently on the Spring Festival holiday. As for the camera, in fact only one pin is functional:PWR_ENABLE

https://wiki.veye.cc/index.php/GX-MIPI-IMX662_Data_Sheet

@alex_ai
RAW-MIPI-SC132M does not support libcamera, nor software based on libcamera. Direct invocation via the v4l2 API is required.

@alex_ai

You need to upgrade your camera firmware. Please refer to the link below to download the firmware, and then follow the subsequent link for the upgrade procedure.

https://www.mediafire.com/folder/4tov5s500gaif/camera_firmware_upgrade_images

https://wiki.veye.cc/index.php/GX_camera_firmware_update_manual

@alex_ai I’ve just checked this function, and it works correctly. I suspect the issue lies in the way you’re operating it.

I recommend that you always change the FPS via the v4l2-ctl command to ensure consistency across different sessions. If you use gx_mipi_i2c.sh directly, the parameters can indeed be changed by writing to the camera registers, but the driver layer is not notified of these changes. As a result, the driver retains incorrect (outdated) values.

@xlwvu7mx said in GX-MIPI-IMX662 on RK3588 with Kernel 6.1 - MIPI CSI Errors:

Also, I've noticed that GX manuals for Firefly and Orange Pi mention FFC cables that connect camera to the board directly and GX-MIPI-IMX662 Data Sheet page tells the camera now accepts I2C 1.8V level. So I think I will try direct connection as well.

OK