My camera doesn’t have GPIO to restart the camera and power dow… I must use i2c cmd to reset this. But it doesn’t fix my problem. I am wondering the xavier-nx can change power mode at runtime??? it makes a power down supply to my camera.
Maybe you can try to unplug the camera after exit then program and restart the daemon the reconnected to try.
oh no, it still gets this problem. Do you have another idea?
Do you confirm able to communicate the sensor to initialize the sensor again after reconnected.
my driver uses soft reset to reset the sensor through protocol i2c and it works normally.
Do you try another camera port?
I can’t try it because my device was located in other regions. I can’t flash another OS to this device.
and this device using L4t 32.4.4 so problem can from jetpack version. Because with the same hardware, driver and camera when i use jetpack 5.0.2 i don’t have this problem.
I would suggest upgrade the BSP for it.
Thanks
sorry, I can’t change anything relate to BSP. Do you think the problem with the clock in Xavier?
Don’t like clock in Xavier due to boost the nvcsi/vi/emc clocks doesn’t help to it.
Thanks
when i compare 2 jetpacks with the same hardware, I see they have the different clocks. So, it is the problem? Here you can see 2 parameters.
Here is in jetpack 5.0.2:
And here is l4t 32.4.4:
I don’t think emc clock would cause this kind of problem.
thanks, I’m having trouble with the problem and don’t know how to handle it. I don’t know the problem from the camera or from core v4l2 of this version jetpack.
You can try to apply these patches
from r35.4.1 to verify the problem.
0001-vi5-continue-captures-even-after-corr-errors.patch (2.3 KB)
0001-camera-vi5-fix-stream-on-off-memory-leakage.patch (6.4 KB)
Thanks, let me try this path.
I am wondering the differrent between reseting driver by command line at runtime with typing “sudo reboot”? I think it the same. So, what driver relating to v4l2 core I must restart with driver camera at runtime (ex: VI driver or NVCSI). Help me give a temporary method to reset the driver without reboot my system.
While the APP terminal the NVCSI/VI will close and power off and after restart they are been reinitialize. Suppose it should be reset by this circle.
Thanks
I found a problem in my system. Have an IRQ process have state ‘D’. So, it can make my problem because the overload leads to my camera can’t response exactly the time from VI driver according this article Use 4 CPU for Multithreading using C in xavier NX . How i can kill this process i know i can’t send SIGKILL to kill process with state ‘D’.
