Xavier custom board boot error

Autonomous Machines Jetson & Embedded Systems Jetson AGX Xavier
,
1

Hi,

We design custom carrier board for Nvidia Xavier
At bring up stage we immediately encounter system boot failure.
The first error is being wuote as following:

[0008.463] I> Kernel EP: 0x80080000, DTB: 0x90000000
[    0.000000] Booting Linux on physical CPU 0x0
[    0.000000] Linux version 4.9.201-tegra (user@Yehoubu15221) (gcc version 7.5.0 (Ubuntu/Linaro 7.5.0-3ubuntu1~18.04) ) #1 SMP PREEMPT Wed Mar 10 10:26:05 IST 2021
[    0.000000] Boot CPU: AArch64 Processor [4e0f0040]
[    0.000000] OF: fdt:memory scan node memory, reg size 48,
[    0.000000] OF: fdt: - 80000000 ,  2c000000
[    0.000000] OF: fdt: - ac200000 ,  44800000
[    0.000000] OF: fdt: - 100000000 ,  780000000
[    0.000000] earlycon: tegra_comb_uart0 at MMIO32 0x000000000c168000 (options '')
[    0.000000] bootconsole [tegra_comb_uart0] enabled
[    0.000000] Found tegra_fbmem: 00800000@a06a0000
[    0.000000] Found lut_mem: 00002008@a069a000
[    1.811152] ufs_tegra 2450000.ufshci: dme-link-startup: error code 1
[    1.923159] ufs_tegra 2450000.ufshci: dme-link-startup: error code 1
[    2.035154] ufs_tegra 2450000.ufshci: dme-link-startup: error code 1
[    2.147148] ufs_tegra 2450000.ufshci: dme-link-startup: error code 1
[    2.158998] ufs_tegra 2450000.ufshci: link startup failed 1
[    2.253296] CPU2: SError detected, daif=1c0, spsr=0xc000c5, mpidr=80000100, esr=be000000
[    2.253302] CPU3: SError detected, daif=1c0, spsr=0x8000c5, mpidr=80000101, esr=be000000
[    2.253308] CPU0: SError detected, daif=1c0, spsr=0x60c00045, mpidr=80000000, esr=be000000
[    2.253314] CPU1: SError detected, daif=1c0, spsr=0xc000c5, mpidr=80000001, esr=be000000
[    2.253340] CPU6: SError detected, daif=1c0, spsr=0x8000c5, mpidr=80000300, esr=be000000
גsafereg_poll_timer_cb: poll interval 130 above target 100 
ב[    2.253345] CPU7: SError detected, daif=1c0, spsr=0x8000c5, mpidr=80000301, esr=be000000
[    2.253354] CPU4: SError detected, daif=1c0, spsr=0x8000c5, mpidr=80000200, esr=be000000
[    2.253360] CPU5: SError detected, daif=1c0, spsr=0x20800045, mpidr=80000201, esr=be000000

I was looking for over the internet but I couldn’t find any information about those errors.

What does the error means and how can I analysis the root cause for the error ?
It is HW issue or Kernel configuration Issue or other thing??

TegraLog.log (125.8 KB)

3

hello yehonatans68sw4,

suggest you review Jetson AGX Xavier Platform Adaptation and Bring-Up since you’re having customize board.
if your board schematic differs from that for Jetson AGX Xavier Developer Kit board, you must change the pinmux configuration applied by the software.

4

Hi,

We have been change the pinmuux according to our board.

Can you please provide additional information about what this error means?
And how can I debugging this error?

Yehonatan

5

there’re several CPU SError failures.
may I know what’s the kernel modification you had done?

[    2.253296] CPU2: SError detected, daif=1c0, spsr=0xc000c5, mpidr=80000100, esr=be000000
[    2.253302] CPU3: SError detected, daif=1c0, spsr=0x8000c5, mpidr=80000101, esr=be000000
[    2.253308] CPU0: SError detected, daif=1c0, spsr=0x60c00045, mpidr=80000000, esr=be000000
[    2.253314] CPU1: SError detected, daif=1c0, spsr=0xc000c5, mpidr=80000001, esr=be000000
[    2.253340] CPU6: SError detected, daif=1c0, spsr=0x8000c5, mpidr=80000300, esr=be000000
6

Hi ,

We customize the Kernel and launch it successfully over Nvidia xavier EVB during the modification process.
The modification are:

*sd card removal
*Converting Usb 3 to USB 2 (The usb 3 type c IC were removed)
*Chaning pinmux.
The main difference is that the currently we are facing HW at bringup so we connected only necessry things for initial bringup which are :
*Power and GND
*Uart for debugging

While all other peripherals such as Eth phy are disconnected.
Maybe the removal of those interfaces (Phy and GPIO ) while they are configured at pinmux cause the fault or it can be Another HW issue?

Yehonatan

7

Hi

After some investigation we found that the ufshci was active even-though that at device tree it was disable.
In order to disable it we follows the instruction as described at:

How to disable "ufshci@2450000"? - #10 by JerryChang but without any success

	fragment-tegra-ufs-lane10 {
			odm-data = "enable-ufs-uphy-l10";
			override@0 {
				target = <&tegra_ufs>;
				_overlay_ {
					status = "disabled"; //need to set disabled
				};
			};
		};

Yehonatan

8

hello yehonatans68sw4,

could you please examine the device tree property via file system to check the node has disabled correctly.
for example,
# cat /proc/device-tree/plugin-manager/fragment-tegra-ufs-lane10/override\@0/_overlay_/status

9

Hi

From log file it seems disabled both overlay and ufshcy
nvidia@ubuntu:~$ cat /proc/device-tree/plugin-manager/fragment-tegra-ufs-lane10/ override@0/overlay/status
disabled

nvidia@ubuntu:/proc/device-tree/ufshci@2450000$ cat status
disablednvidia@ubuntu:/proc/device-tree/ufshci@2450000$

10

hello yehonatans68sw4,

since you’re working at initial bring-up stage,
please have pinmux customization applied, and please have another verification with your peripherals connected,
thanks

11

Ok

13

This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.

14

@JerryChang
Maybe you could extend on similar issue here