Ov9281 CM4 init camera status = 4099


I am experiencing a problem with the raspberry compute module 4. The application ./opencvGui always reports “init camera status = 4099”

I have run ./camera_i2c.sh and get:
setting GPIO for board revision: c03140
Failed: don’t know how to set GPIO for this board!

The camera is connected to CAM1

When following the steps described in: OV9281 1MP Global Shutter Camera for Raspberry Pi - Arducam

To the command “ls /dev/video0”
I get “/dev/video0” no matter if the camera is connected or not.

To the command “v4l2-ctl --stream-mmap --stream-count=-1 -d /dev/video0 --stream-to=/dev/null”
I get something like:
<<<<<<<<<<<<<<<<<<<120.62 fps

I am also able to run the yavta application and get images from the camera.

When running ./opencvGui I had previously deleted the line
dtoverlay=ov9281 from config.txt because I found out that the drivers are different (although this is
not documented anywhere)

To the command: “dmesg | grep ov928”
I get:
[ 5.898580] ov9281 10-0060: Detected OV009281 sensor
[ 32.475627] ov9281_dvdd: disabling
[ 32.475638] ov9281_dovdd: disabling
[ 32.475650] ov9281_avdd: disabling

I have read all the related topics I found and I know I am not the only one experiencing this problem. I hope you could help me.

I am sorry I didn’t follow the procedure. I have rewrited the mail:

  1. Where did you get the camera module(s)?

  2. Model number of the product(s)?
    B0225 arducam OV9281 1MP Mono Global Shutter

  3. What hardware/platform were you working on?
    Raspberry Pi 4 compute module 4Gb ram, eMMC 32 Gb, Wifi

  4. Instructions you have followed.
    OV9281 1MP Global Shutter Camera for Raspberry Pi - Arducam
    Camera Userland Driver SDK and Examples - Arducam

  5. Problems you were having?
    When trying to execute any arducam application I get “init camera status = 4099” error

  6. The dmesg log from your hardware?
    [ 6.048288] ov9281 10-0060: Detected OV009281 sensor

  7. Troubleshooting attempts you’ve made?
    I have tested the same camera in raspberry pi 4 (8 Gb ram) and it works with no problems.
    If I follow the steps described here:
    OV9281 1MP Global Shutter Camera for Raspberry Pi - Arducam
    The camera works as expected.

The I switch to the instructions in here:

Before doing all the process, I remove the line dtoverlay=ov9281 in config.txt

  1. What help do you need?
    I need a solution to be able to run the sdk examples.


I’ve got the same issue - I was told that they have not tested on the CM4. I’ve asked for the tests to be done as I need it working but no response; silence - which is weird because Arducam have previously been very responsive… I’m on the 16MP Sony IMX298 camera but basically have the same issue as you. I’m having to look for an alternative supplier as we need this on the CM4.



Hi @Triff @neil-bennziath-com

I’m very sorry, but the person in charge of the raspberrypi pi camera has been busy recently,
I will remind them to check this issue.

I’m very sorry that it took so long to reply to you. We have updated the MIPI_Camera library file and added the version you are using now. You can download it again and try it again. As you said, when using MIPI_Camera library, you need to comment out dtoverlay=ov9281.

Thank you! You will never know how happy you made me with your response.


Thanks that is fantastic! Can you let me know if this has been done for the 32bit and 64bit libraries?



Hello, I have tested the new driver and works fine with the evaluation board. However, in the board we designed it gives you “init camera status = 4100”. However, there are no errors with the yavta application.
My question is the following:
Does the camera checks the crypto chip that comes installed with the camera board?

In our current desing, the cryto chip is not installed. However, we have design it to install it if needed.
If the crypto chip is required for the camera to work, my next question is:
Is there any way to buy them from you?

For our design, I guess that we would need to buy the stand alone camera:

… and the crypto chip if it is needed.


Yes, both 32-bit and 64-bit are supported, you can download and test.

Yes, our driver will detect the encryption chip, if not, the driver cannot be used normally.
We are very sorry, our encryption chip is not for sale. If you use our driver, you can only buy our products. If it is a self-designed board, you can only develop the driver yourself.

Thanks for your answer.