@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.
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.
@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
@alex_ai
RAW-MIPI-SC132M does not support libcamera, nor software based on libcamera. Direct invocation via the v4l2 API is required.
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
@xlwvu7mx
I don't think it's a cable length issue or a DTS problem. Have you tried testing with a different adapter board or a different mainboard? I tested it with an Orange Pi CM5, using a 50cm FFC cable plus a 20cm FPC cable, and the image was very stable.
