We checked the Power-On Sequence and we cannot see any difference between a successful boot at higher temperatures and a non successful boot at very low temperatures. Will the Jetson Module release the SYS_RESET_N signal even if something before went wrong? Do you have other ideas what we could check?
We checked now if the system is not booting only when the AGXi is cold or only if our carrier board and the AGXi are cold. If the AGXi only is cold, the system still boots up normally. But now when pressing the reset button, the system does not boot until the reset is pressed again. Does this give you any indication what could go wrong?
Hi, have no clue in your tests. Do you have another AGXi module to do cross-check? Basically AGXi module is validated at low temperature, so you should focus on your custom carrier board. It is hard to tell what caused the boot failure per your description. If you can use another module or validated carrier to do cross-check, that will be helpful.
We saw this behavior already with two AGXi modules and we tested a carrier board which was not booting with the industrial version with an AGX without seeing any problems. Resetting the module does only power off and on the Carrier board by the CARRIER_POWER_ON signal, right?
We sent our schematics to NVidia for checking. Let’s hope they find something.
Have you checked all carrier power supplies to make sure no one is up before carrier_pwr_on asserted? As it needs to be guaranteed that between module and carrier, the shared IO pins status won’t be affected during power-on.
We got now one step further. When disconnecting the Goldcap attached to the VCC_RTC pin, the system always boots at low temperatures with the AGX industrial module. Do you have any explanation for this? Did you do your internal tests with a battery/goldcap connected to the DevKit?
Hi, have you probe the power on sequence? Can you share the waveform of power on sequence similar to the sequence listed in product design guide? Especially the timing between VIN_PWR_BAD and MODULE_PWR_ON? The VIN_PWR_BAD is expected to be de-asserted before others.
We checked the timing and there is no difference between a successful boot and a non-successful one. We measured the current on the VCC_RTC Pin and saw, that the industrial Xavier needs currents up to 0.4 mA (at 2.5V). This we were able to reproduce on the NVidia DevKit. The AGX Module however draws the expected current around 2uA. With the AGX Module we saw that the current changes the leading sign when it is turned on, meaning the Module charges the battery. Shouldn’t this feature be disabled by default? In the device tree it is disabled.
Do you have an explanation for this?
What do you mean with nothing connected? No module? Please explain what we have to double confirm.
There is another thread with the same topic: XAVIER Industrial RTC current consumption high
Did you internally reproduce the issue?