Nvargus sending "Wrong frequency range" message


I have my camera working using the test tool nvargus_camera that you can find in /usr/src/jetson-multimedia-api. However, when I check the logs of nvargus_daemon, I can see that it continually returns a warning sentence: “Wrong frequency range”. You can see the picture bellow.

What does it means? Is it linked to the skew calibration mentioned in the documentation? Also, I am under the impression that the frequency of the message augments with the movement in the image being displayed.


hello louis.guerlin,

are those camera preview frames stream normally?
this is warning messages printed by flicker detection. there might be issues of your sensor read-out time.

Hello JerryChang,

The stream seems normal. I don’t see any frame drop. Do you think that if the I2C read/write of the driver I am using is too slow this may occur?



I have an additional note, if I switch from 12001920 60fps to 12001920 30fps, I still have the message. I don’t have the message when I use a 960*600 120fps binned mode.

After further investigation, the crashes are not linked to this issue and the impulse noise disappeared when I changed the module. I removed them from my previous message.

However, the flickering warning remains, even when I deactivate AE antibanding mode, or even AE and AWB.

The sensor I am using is a global shutter sensor, I don’t know if that makes a difference.

hello louis.guerlin,

you may gather the Argus daemon debug logs for checking.
please configure below settings on the target,

$ sudo su 
# pkill nvargus-daemon
# export enableCamCoreLogs=5
# nvargus-daemon
or.. # nvargus-daemon 2>&1 | tee argus-output.log

Hi JerryChang,

Here is the output log. It shows the situation when I open the camera in 1200p, then I switched to 1080p, and finally to 960p. There is no warning only in 960p.


argus-output.log (5.0 KB)

could you please check the steps, it doesn’t looks like you’ve configure debug flag, enableCamCoreLogs.

Hi JerryChang, my bad, here are the complete logs!

argus-output.log (9.6 MB)

hello louis.guerlin,

this may be a false alarm due to camera motion. is your camera mounted on the moving device?
otherwise, please examine ReadOutTime, it’s the time taken to read out active region.
this is basically calculated by… ReadOutTime = (Image height * line length) / pixel clock in hz
you should review the sensor specification, and please also check developer guide to review Sensor Pixel Clock.

Hello JerryChang,

The camera is static but the messages do appear when dynamic objects enter its field of view. Nonetheless, my sensor is working.

that might be a false alarm as mentioned in comment #11 as long as your camera use-case works normally.

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.