Difference between Controlled and Uncontrolled power down sequence of Jetson-TX2

I am developing my custom carrier board to integrate Jetson-TX2 module on it. The system will work as a camera frame grabber. I am powering up my Camera from the same carrier board through Power Over Camera Link (POCL). Camera and every IC other than Jetson-TX2 is getting powered ON only after Jetson-TX2 is powered up and CARRIER_PWR_ON is asserted.

But I cannot differentiate between the Controlled and Uncontrolled Power Down Cases mentioned in Page-12 of ‘Jetson TX2 OEM Product Design Guide’. How the controlled power down sequence will start? In Jetson TX2 Module Datasheet, it is mentioned only about Controlled Power Down Sequence that “On receiving a Shutdown request the Jetson TX2 will assert the RESET_OUT# signal, allowing the carrier board to put any
components into a known state.”
What kind of shut-down request Jetson-TX2 will receive to start controlled power-down sequence?

It is obvious that uncontrolled power down sequence starts when VDD_IN begins to ramp down. But what will be the status of VDD_IN in case of Controlled power-down sequence and when can VDD_IN start ramping down? It is not clear in the controlled power down sequencing diagrams given in both the datasheets.

Can somebody please help me clearing my confusion?

Hi mehjabin,

To activate RESET_OUT# will trigger controlled power down, that could be pressing RESET button or some SW controlled pulling RESET_OUT# pin to low.

The uncontrolled power down sequence is triggered by VDD_IN removal, removal of the VDD_IN/VDD_MUX supply causes IN_PWR_BAD# to go active which causes Jetson TX2 to initiate a controlled shut down.

Thank you for the reply Trumany.

Can you please elaborate on the last sentence “The uncontrolled power down sequence is triggered by VDD_IN removal, removal of the VDD_IN/VDD_MUX supply causes IN_PWR_BAD# to go active which causes Jetson TX2 to initiate a controlled shut down.”

How uncontrolled power removal initiates controlled shut-down in Jetson-TX2?

PMIC on the module takes 20ms to shut-down in case of controlled power down or uncontrolled power removal?

I have one more doubt. CARRIER_PWR_ON is given as open drain signal and from your reply on another post on the forum I got to know that a pull-up is present on the module. But this will make the signal active low though it’s given as active-high output from Jetson-TX2 on the datasheets.

Hi, mehjabin,

  1. About VDD_IN removal, please refer to figure 6 of OEM DG

  2. The controlled shut down takes ~20ms to complete so the internal PMIC supply needs to stay above ~2.9v for >~20ms.

  3. CARRIER_PWR_ON is active high, the pull up voltage can only be enabled when module power active, please refer to related info in table 5

At what current draw? If it’s for the entire module at the maximum load, 15W at 5V is 3A, and 3A with 2V voltage drop over 20 ms requires 30,000 uF of low-ESR capacitance.

What happens if it doesn’t?

Hi Trumany,

Actually I am confused about the terms controlled and uncontrolled shut-down.

  1. The controlled shut down takes ~20ms to complete so the internal PMIC supply needs to stay above ~2.9v for >~20ms.

Does that mean PMIC takes 20ms to shut down in controlled power down case which is triggered by RESET_OUT#?
Then what about the case of uncontrolled power down? How much time does PMIC take to shut down in this case? I need this information because I am not using RESET_OUT# to initiate controlled shut down in my custom design. So power down will happen only due to main supply removal which is the uncontrolled power down case. The moment this happens my custom carrier board power should ramp down before Jetson-TX2 module’s internal power rails go down. This requires PMIC power down timing during uncontrolled power removal event.

  1. CARRIER_PWR_ON is active high, the pull up voltage can only be enabled when module power active, please refer to related info in table 5

One of the switching regulators on my custom carrier board does not allow to place pull-up at its enable pin. I want to give CARRIER_PWR_ON as enable to it. That’s why I want to confirm whether I can totally avoid external pull-up at CARRIER_PWR_ON output?

Hi snarky, not all power rails in module are from PMIC, VDD_CPU, VDD_GPU and VDD_SOC have their own power source.

Hi mehjabin,

20% drop on VDD_IN will trigger VIN_PWR_BAD# to start a controlled power down process. So the course of this drop is decided by the capacitors on VDD_IN, you can measure on dev kit to get the time from drop start to VIN_PWR_BAD# active.

As you know there is a pull-up in module on CARRIER_PWR_ON, I don’t know why not allow a pull-up on your regulator enable pin, but since that, seems CARRIER_PWR_ON can’t be used as enable to it.