After few weeks investigation, we believed that the power cut is related to power supply problem.
It is because the power cut immediately when we turned to MODE_30W_6CORE (We are running on DC). After replacing the cable with much thicker one, it can run at MODE_30W_6CORE more than 2 hours. We thought the problem is gone.
However, the Xavier power cut again after 48 hours at MODE_15W_DESKTOP.
My question are:
What’s the differences between MODE_15W and MODE_15W_DESKTOP?
We turned on the “Jetson Clock”, is this a good practice to lock the power consumption in our case?
Our program is to capture the traffic situation and some specific type of vehicles. It connects to a PoE camera via a ethernet switch. Eventually, based on a business case, the program exports a video from the camera and upload to data center.
We are suffering power sudden cut off problem. It happened occasionally, sometimes after 12 hours, sometimes 48 hours… no clue yet. We already replaced DC battery, cables, switch and Xavier too, but still no luck.
Thanks Kevin, actually the machine is installed in a very remote area (outdoor), we can’t debug via the serial console log easily.
We installed 5 set equipment (Camera + Router + Xavier + Battery + Remote switch) in 5 different location. Only one of them is hitting this problem.
The file “reason”, within “/sys”, shows a reason for the last reboot. I think the PMIC driver creates this file and dynamically inserts it into the device tree during boot based on the previous system off condition (e.g., software reset, power loss, so on). However, that was in L4T R32.x, and it looks like the PMIC reason file is no longer created (I was so used to having that I didn’t realize R35.x does not).
I guess I should ask the question to @KevinFFF, is there anything similar to the device tree reason file on R35.x?
Hi, please read the chapter DV/Dt Circuit Considerations in Xavier Design Guide. Your issue looks like be caused by Dv/Dt. You can try the rework listed in the chapter. Besides above, you also should do more tests to make sure if it is caused by poor power supply, like using other supplies and etc.