Posts made by veye_xumm

@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

@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.

@xlwvu7mx
Based on our experience, under normal circumstances an FFC cable length within 50 cm does not cause any issues. We have tested a setup with a 20 cm FFC cable + an adapter board + a 50 cm FFC cable, and it worked normally. Could you please provide some photos of the actual setup so we can take a look?

@xlwvu7mx
Hello, the MIPI data rate of the GX series products is indeed higher than that of the VEYE series: GX: 1188 Mbps, VEYE: 594 Mbps. Based on the issues you are experiencing, I mainly suspect the MIPI signal quality. Please pay special attention to the following:

• What is the length of your FFC cable?

• About your adaptor board:

1. Have the differential pairs been length-matched? (This is required.)
2. Has impedance matching been implemented? (Strongly recommended.)
3. Are there any ESD protection devices with large junction capacitance on the signal lines?

• Could you take a photo of your actual connection and send it to me for review?

@sheko It looks like nothing is abnormal. You haven’t installed a lens, right?

@sheko

 cd veye_viewer
    chmod +x ./*
	chmod 755 ./config/*.sh
    ./start_veye_viewer.sh

@sheko
Hi,
It looks like you downloaded the source code, but didn’t compile it. You can download the precompiled binary from the link below and run it directly.
https://github.com/veyeimaging/veye_viewer/releases/download/v1.1.4_rpi/veye_viewer_RaspberryPi_bin.zip

@sheko

You have successfully loaded the driver and detected the camera. Please refer to the instructions for the veye_viewer client software in the previous link to directly preview the images:
https://wiki.veye.cc/index.php/Mv_series_camera_appnotes_4_rpi#veye_viewer

@sheko
https://wiki.veye.cc/index.php/Raspberry_Pi_Application_Note_Index

part1.2

@sheko
The RAW-MIPI-SC132M module requires the mvcam driver, not cssc132.

@xlwvu7mx You are welcome.

@xlwvu7mx
The driver has been uploaded to GitHub, please check.

@d_101 Sorry for the late reply. Based on the current situation, I can only suspect a hardware issue that is causing the I2C path to be unavailable. This could be a problem with your mainboard or with the camera itself. Please return the camera to us, and we will perform testing and inspection.

@ffgemanof
The veye_viewer client currently does not support the mono10 and mono12 formats. If you need to use these formats, please configure the data format using mv_mipi_i2c_new.sh, and then acquire the data using v4l2-ctl or the V4L2 API.

@xlwvu7mx
Sorry for the late reply.
The GX series is our latest product line. The driver porting work for the Rockchip (RK) platform has now been completed.
We plan to finish uploading the driver code for kernel version 6.1 as well as the images for several supported boards within this week.
Thank you for your trust and support.