3LSS safety status (l3_getsafetystatus)

Hi all,

My driver xavier board cannot be booted to a healthy status. The board is always in a NOK state even after I do a aurixreset. Here is the error message:

shell> l3_getsafetystatus
Info: Executing cmd: l3_getsafetystatus, argc: 0, args:

Platform FuSa State: NOK STATE
Platform Startup Status: NOK STATE
Tegra A FuSa State: OK STATE
Tegra B FuSa State: INIT STATE
Tegra A nSAFE State: nSAFE DEASSERTED
Tegra B nSAFE State: NOK STATE
Platform Error Log Count: 1

It also reports errors after a aurixreset:

hell> aurixreset
DRIVE-V5.1.3-E3550-EB-Aurix-With3LSS-StepA-3.04.02
Compilation date: Feb 25 2019, 15:31:23
Copyright 1998-2017 Elektrobit Automotive GmbH

Hardware information:
SystemUpInit-Time[ms]: 0

EB-DDPX-SHELL
Enter ‘help’ to see the available commands.

Startup Finished

shell> The board has been powered on.
KL15 power UP or WakeUp from deep sleep or shell command.
Power On sequence Triggered.
Detect 2nd Harness is not connected.
If you are using DGPU, please contact your hardware representative to get 2nd harness cable
Configured BootStraps for X1 as QSPI
Configured BootStraps for X2 as QSPI
Temperature sensor initialized
Init SJA1105 sucessfully
Initial 88Q2112
Initial 88Q2112 A0 silicon slave address 01
Initial 88Q2112 A0 silicon slave address 02
Initial 88Q2112 A0 silicon slave address 03
Initial 88Q2112 A0 silicon slave address 04
Initial 88Q2112 A0 silicon slave address 05
Initial 88Q2112 A0 silicon slave address 06
Initial 88Q2112 A0 silicon slave address 07
88E6321_1 is in CPU mode
88E6321_2 is in CPU mode
Initial 88e6321_1
Enable VLAN
Initial 88e6321_1 port 1 in SGMII Mode.
Initial 88e6321_2
Reset port 3,4 Rxc delay line

User callback function invoked on platform functional safety failure.

It seems that there some callback function failed. Is there a way to debug the errors? I am new to 3LSS. Any advice would be appreciated.

Thanks,
Bin

Dear binzvxxh,

We need further logs from L2 and L1 consoles of Tegra B. The errors reported in Aurix console is indicating that Tegra B is in faulty state.

Are both Tegra A & B flashed with identical SW versions? Thanks.

Thanks for the reply. How can I get the logs from L2 and L1 consoles of Tegra B? I am new to drive Xavier.

Dear binzvxxh,

Could you please let us know if Xavier A & B flashed with identical SW versions first? Thanks.

Hey Steve,

Thanks for the reply. The two chips are flashed with different SW versions I believe. What problems would that cause?

Bin

Dear binzvxxh,

Thank you for your confirmation.
Each PDK SW have different Aurix FW like below.
ex)5.0.13.2 PDK has SW Version: DRIVE-V5.0.13-E3550-EB-Aurix-ForHyperion-3.01.05
5.1.3.x PDK has DRIVE-V5.1.3-E3550-EB-Aurix-With3LSS-StepA-3.04.02

So if the Xavier A/B are flashed with different SW versions, probably Aurix FW can’t get proper information.
So could you please flash the Xavier A/B with same SW version and re-check it? Thanks.

Hi Steve,

Thanks for the reply. Let me try that first. If they still report NOK state, I will report it here.

Dear binzvxxh,

Thanks please report if you have still same symptom.