Qustion of the SOC_ERROR (K37) pin behavior on Jetson AGX Orin

Hello Nvidia Team,

I have a question regarding the expected behavior of the SOC_ERROR (K37) pin on the Jetson AGX Orin.
.
My expectation was that this pin would remain high by default and pull low (active low) when a critical system error occurs, such as a kernel panic. To test this, I triggered a kernel crash using:

sudo echo c > /proc/sysrq-trigger

However, the SOC_ERROR pin did not active to low after running this command. Instead, the system hung and rebooted. Additionally, I observed that the pin was pulled low starting from the bootloader stage, which seems unexpected.
.

Here is my pinmux configuration for pin K37 (soc_error_pu0):

	soc_error_pu0 {
		nvidia,pins = "soc_error_pu0";
		nvidia,function = "soc";
		nvidia,pull = <TEGRA_PIN_PULL_NONE>;
		nvidia,tristate = <TEGRA_PIN_DISABLE>;
		nvidia,enable-input = <TEGRA_PIN_DISABLE>;
		nvidia,io-high-voltage = <TEGRA_PIN_DISABLE>;
		nvidia,lpdr = <TEGRA_PIN_DISABLE>;
	};

Is SOC_ERROR expected to trigger on kernel panics (sysrq-trigger), or what else can I do to test this SOC_EEROR?

My Jetpack is 6.2. kernel 5.15.148

Does anyone know how the SOC_EEROR(K37) works?

SOC_ERROR is for FSI to use but not a general GPIO/SFIO to use here.

Hi WayneWWW,

  1. Does FSI stand for Functional Safety Island?

  2. Therefore, we cannot use pin K37 to notify another machine that an error has occurred on the AGX Orin. Is that correct?

  3. Is there any pin on the AGX Orin that can perform this function I want?

Yes, FSI is for Functional Safety Island. K37 is not able to notify error to other machine if you are using Orin AGX.

Unfortunately we don’t provide safety function on Orin AGX.

Thus, to achieve some error report functions, you may only implement something like a GPIO output to keep sending heart beat to external machines. If a panic happened so that heart beat is gone, you may trigger the action items that you want.

Okay. Thank you Wayne.