System boot stuck at "Starting Kernel" on S32G-VNP-RDB2

[YMM]

Hi,

I am trying to bring up a  S32G-VNP-RDB2 with QNX OS 7.1. 

S32G-VNP-RDB2 boot sequence is stuck at "starting kernel" and after 5 seconds it reboots by itself.

I am using a SD card as a boot device and followed the procedure in the user manual to image it. Tried using both the RDB and RDB2 files as listed in the table below. But the system fails to start the Kernel.

File type	RDB	RDB2
Boot file	u-boot-s32g274ardb.s32	u-boot-s32g274ardb2.s32
Dtb file	fsl-s32g274a-rdb.dtb	fsl-s32g274a-rdb2.dtb
Ifs file	ifs-s32g-rdb.ui	ifs-s32g-rdb.ui ( using rdb file, since no rdb2 file available)
Result	Stuck at "Starting Kernel" and reboots after few seconds	Stuck at "Starting Kernel" and reboots after few seconds

Terminal output snippet :

[Tue Jan 11 10:15:09.377 2022] U-Boot 2020.04+geef88755a7 (Mar 03 2021 - 07:18:34 +0000)
[Tue Jan 11 10:15:09.378 2022]
[Tue Jan 11 10:15:09.378 2022] CPU: NXP S32G274A rev. 2.1.0
[Tue Jan 11 10:15:09.379 2022] Reset cause: Functional Reset
[Tue Jan 11 10:15:09.379 2022] Model: NXP S32G2XX
[Tue Jan 11 10:15:09.379 2022] Board: NXP S32G274A-RDB
[Tue Jan 11 10:15:09.379 2022] DRAM: 3.5 GiB
[Tue Jan 11 10:15:10.217 2022] CA53 core 1 running.
[Tue Jan 11 10:15:10.217 2022] CA53 core 2 running.
[Tue Jan 11 10:15:10.217 2022] CA53 core 3 running.
[Tue Jan 11 10:15:10.218 2022] All (4) cores are up.
[Tue Jan 11 10:15:10.218 2022] MMC: FSL_SDHC: 0
[Tue Jan 11 10:15:10.234 2022] Loading Environment from MMC... OK
[Tue Jan 11 10:15:10.311 2022] Using external clock for PCIe0
[Tue Jan 11 10:15:10.311 2022] Configuring PCIe0 as RootComplex(x2)
[Tue Jan 11 10:15:10.532 2022] Using external clock for PCIe1
[Tue Jan 11 10:15:10.532 2022] Frequency 125Mhz configured for PCIe1
[Tue Jan 11 10:15:10.532 2022] Configuring PCIe1 as SGMII(x2) [XPCS0 2.5G, XPCS1 OFF]
[Tue Jan 11 10:15:10.801 2022] PCIe0: Failed to get link up
[Tue Jan 11 10:15:10.801 2022] Pcie0: LINK_DBG_1: 0x00000000, LINK_DBG_2: 0x00000800 (expected 0x000000d1)
[Tue Jan 11 10:15:10.801 2022] DEBUG_R0: 0x00567000, DEBUG_R1: 0x08200000
[Tue Jan 11 10:15:10.801 2022] PCI: Failed autoconfig bar 20
[Tue Jan 11 10:15:10.801 2022] PCI: Failed autoconfig bar 24
[Tue Jan 11 10:15:10.802 2022] PCIe1: Not configuring PCIe, PHY not configured
[Tue Jan 11 10:15:10.802 2022] In: serial
[Tue Jan 11 10:15:10.802 2022] Out: serial
[Tue Jan 11 10:15:10.802 2022] Err: serial
[Tue Jan 11 10:15:10.802 2022] Net: EQOS phy: rgmii fixed-link
[Tue Jan 11 10:15:10.802 2022]
[Tue Jan 11 10:15:10.802 2022] Warning: eth_eqos (eth0) using random MAC address - 7e:94:2d:38:cf:fa
[Tue Jan 11 10:15:10.802 2022] eth0: eth_eqos PFE: emac0: sgmii emac1: none emac2: rgmii
[Tue Jan 11 10:15:10.816 2022] PFEng firmware file 'mmc@0:1:s32g_pfe_class.fw' loading failed: -2
[Tue Jan 11 10:15:10.837 2022]
[Tue Jan 11 10:15:10.837 2022] Hit any key to stop autoboot: 10 9 0
[Tue Jan 11 10:15:12.051 2022] => boot rub n boot_qnx
[Tue Jan 11 10:15:36.918 2022] Probe SJA1105
[Tue Jan 11 10:15:36.980 2022] Loading SJA1105 firmware over SPI 1:0
[Tue Jan 11 10:15:36.980 2022] No matching device ID found for devid FFFFFFFF, cs 0.
[Tue Jan 11 10:15:36.980 2022] Error SJA1105 configuration not completed
[Tue Jan 11 10:15:37.043 2022] PFEng firmware file 'mmc@0:1:s32g_pfe_class.fw' loading failed: -2
[Tue Jan 11 10:15:37.064 2022] PFE: emac0: sgmii emac1: none emac2: rgmii
[Tue Jan 11 10:15:37.128 2022] switch to partitions #0, OK
[Tue Jan 11 10:15:37.128 2022] mmc0 is current device
[Tue Jan 11 10:15:37.562 2022] 9507096 bytes read in 427 ms (21.2 MiB/s)
[Tue Jan 11 10:15:37.562 2022] ## Booting kernel from Legacy Image at 8007ffc0 ...
[Tue Jan 11 10:15:37.593 2022] Image Name:
[Tue Jan 11 10:15:37.593 2022] Image Type: AArch64 Linux Kernel Image (uncompressed)
[Tue Jan 11 10:15:37.593 2022] Data Size: 9507032 Bytes = 9.1 MiB
[Tue Jan 11 10:15:37.594 2022] Load Address: 80080000
[Tue Jan 11 10:15:37.594 2022] Entry Point: 80080000
[Tue Jan 11 10:15:37.594 2022] Verifying Checksum ... OK
[Tue Jan 11 10:15:37.675 2022] XIP Kernel Image
[Tue Jan 11 10:15:37.675 2022]
[Tue Jan 11 10:15:37.675 2022] Starting kernel ...
[Tue Jan 11 10:15:37.675 2022]
[Tue Jan 11 10:15:43.396 2022]
[Tue Jan 11 10:15:43.396 2022]
[Tue Jan 11 10:15:43.396 2022] U-Boot 2020.04+geef88755a7 (Mar 03 2021 - 07:18:34 +0000)
[Tue Jan 11 10:15:43.396 2022]
[Tue Jan 11 10:15:43.396 2022] CPU: NXP S32G274A rev. 2.1.0
[Tue Jan 11 10:15:43.396 2022] Reset cause: Power-On Reset
[Tue Jan 11 10:15:43.396 2022] Model: NXP S32G2XX
[Tue Jan 11 10:15:43.396 2022] Board: NXP S32G274A-RDB
[Tue Jan 11 10:15:43.396 2022] DRAM: 3.5 GiB

I have attached the Terminal output along with the env variables. Could someone please advise on how to fix this issue ?

I am quite new to QNX OS and NXP systems so not sure if I am missing any basic settings. I am just  following the user guide for installation. Any help is appreciated. Thank you.

[bpe]

NXP does not own QNX BSP. QNX OS is firmly controlled and developed by BlackBerry QNX.
Our recommendation in this regard is to approach the OS vendor as the first line.
NXP can get into the loop at a later stage, if after the initial debugging/research
the issue is found to be related to NXP hardware or a low-level driver, but you have
to open a ticket for that.

Best Regards,
Platon