Hi Robert, Sorry to hear this. Please write to service@eyecloud.tech for further assistance. Regards, Johanna

Hello Robert, First of all, welcome to the Linux world🤗, and nice question post❤️. Regarding your question, first please allow me to figure out the exact camera module product you are using. Totally we have two AR0234CS based camera modules: 1. One is CS-EYECLOUDAI-04 which was sold in Crowd Supply, and now is selling on Mouser; 2. Another is the AR0234CS camera module with a daughterboard for Raspberry Pi and Jetson Nano, which is selling in our OpenNCC online shop. Which one were you using with your Jetson Nano? The right option for you to work with Nano is Option #2. Assume you were using the right option, the AR0234CS camera module with a daughterboard for Raspberry Pi and Jetson Nano, since this product is a hardware-ready product, to work it with Jetson Nano, users need to develop the camera driver for it. Below are some suggestions on how to develop the camera driver: I see from your post above that you have successfully run imx219 based camera: $ v4l2-ctl --list-devices vi-output, imx219 7-0010(platform:54080000.vi:0): /dev/video0 To develop the driver for the AR0234CS camera module, you can refer to the one you already have for your imx219 camera. Normally there are two tasks you need to do: 1. Replace the imx219 configuration file with the one for AR0234CS(I will attach those files below). 2. Request datasheet of AR0234CS from On semi(On semi requires confidentiality for this datasheet, so users have to request it from On semi by themselves). Modify the driver with the AR0234CS datasheet. AR0234CS configuration file @60Hz AR0234CS configuration file @120Hz Above are the information and suggestions I can provide now. Please take a look and feel free to let me know if you have any other questions. Support and encouragement from me, Johanna

Thank you for the great recognition and business, we are so happy and grateful to have this! Looking forward to working with your team again in the near future, and best wishes to the progress of your project!

Thank David for the excellent post. The SKU you linked in this post can meet all your spec requirements, details are below: 1. AR0234 (monochrome is preferred, but rgb is acceptable) -->Reply: Both monochrome and RGB are available. 2. Raspberry Pi Connector -->Reply: Support. In this SKU there is a daughterboard to connect the sensor module and Raspberry Pi. 3. No ISP -->Reply: It has no ISP. This SKU outputs raw data. Replies to your second batch of questions: 1.The RPi connector's CAM_D[0:1]_{N,P} and CAM_CK_{N,P} pins are connected directly to the AR0234CS sensor module. -->Reply: Yes. 2. The I2C signals don't configure anything else besides the AR0234 image sensor -->Reply: No, they don't. 3. Configure "Power Enable" pin -->Reply: The "Power Enable" pin is connected directly to the AR0234CS RESET_BAR pin Based on our engineers' evaluation, you can use this SKU to capture MIPI data with the FPGA successfully. Below are the schematics of the daughterboard, which I think may be helpful for you. Feel free to let us know if you have any further questions. Thank you for your interest and your time. Best wishes, OpenNCC team

Take ".../Example/How_to/OpenNCC/C&C++/Capture_video" in "R21.09.01" as an example to answer this question. In the sdk.h file, the parameters defined by the structure Camerainfo are one of the parameters for the SDK initialization function sdk_init (...). The three variables in the structure that controls whether the video stream is initialized are as follows: typedef struct{ ... int isOutputYUV; int isOutputH26X; int isOutputJPEG; ... } CameraInfo; A value of 1 indicates initialization, and a value of 0 indicates no initialization, that is, the function is not turned on. In cameraCtrl.h file, the function camera_video_out(int video_type, camera_ctrl_video_out mode); Is used to realize the output mode of different video streams. Mode is assigned to 0 to stop the mode; A value of 1 indicates the single frame output mode, that is, stop the output after outputting 1 frame of data; A value of 2 indicates continuous output.