topic Re: pfe1 connection fail with 2.5G on RDB3 SDK BSP39 in S32G

pfe1 connection fail with 2.5G on RDB3 SDK BSP39

hittzt — Tue, 30 Jan 2024 01:58:43 GMT

Hi,

Recently, I tested pfe1 2.5G status by connecting pfe1 interface with two RDB3 boards, which runs SDK BSP39 image with pfe feature enabled like following:

DISTRO_FEATURES:append = " pfe"
NXP_FIRMWARE_LOCAL_DIR = "/path/to/firmware/binaries/folder"

But the connection failed as following:

root@s32g399ardb3:~# ifconfig pfe1
pfe1: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet 192.168.2.3 netmask 255.255.255.0 broadcast 192.168.2.255
inet6 fe80::204:9fff:febe:ef01 prefixlen 64 scopeid 0x20<link>
ether 00:04:9f:be:ef:01 txqueuelen 1000 (Ethernet)
RX packets 0 bytes 0 (0.0 B)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 111 bytes 24372 (23.8 KiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
device memory 0x46000000-46ffffff

There is no RX packets on both sides. The logs is attached.

Would you please help to confirm the issue?

Thanks,

Zhantao

Re: pfe1 connection fail with 2.5G on RDB3 SDK BSP39

chenyin_h — Wed, 31 Jan 2024 02:16:47 GMT

Hello, @hittzt

Thank you for the question.

May I know if you have tried the pre-built images on your platform? As far as I know, our FAE had used such test connection before without issues found with default images and settings, my initial suggestion is to try the pre-built images at first to check if there are any other problems existed.

The pre-built images could be downloaded from the NXP.com, you may reference the following method:

- Sign in to your NXP account (link to NXP site: Automotive, IoT & Industrial Solutions | NXP Semiconductors)
- Click on "My NXP Account" (top-right) and click on "Software Licensing and Support" under the "Licensing" section within the window it opens.
- This will redirect you to another page. In this new page, select the option "View Accounts" under the "Software accounts" section.
- This will again redirect you to another page. On this page, you should see an "Automotive SW - S32G - Linux BSP (Cortex-A53)" option, click on it.

In there, you should see all the available BSP versions for your account. Then download the per-built binaries for S32G3 for a trial.

Let me know if it helps

Best Regards

Chenyin

Re: pfe1 connection fail with 2.5G on RDB3 SDK BSP39

hittzt — Wed, 31 Jan 2024 05:06:22 GMT

Hi,

Yes, I tried to use the pre-built pfe image, but it failed as following:

NOTICE: Reset status: Power-On Reset
NOTICE: BL2: v2.5(release):bsp39.0_rc8-2.5
NOTICE: BL2: Built : 10:17:55, Dec 8 2023
NOTICE: BL2: Booting BL31

U-Boot 2022.04+g0755d13668 (Dec 07 2023 - 12:31:18 +0000)

SoC: NXP S32G399A rev. 1.1
CPU: ARM Cortex-A53 r0p4 @ max 1300 MHz
Model: NXP S32G399A-RDB3
DRAM: 3.5 GiB
Core: 306 devices, 25 uclasses, devicetree: board
MMC: FSL_SDHC: 0
Loading Environment from MMC... OK
In: serial@401c8000
Out: serial@401c8000
Err: serial@401c8000
Board revision: RDB3 Revision F
PCIe: BusDevFun VendorId DeviceId Device Class Sub-Class
__________________________________________________________________________
pcie@40400000 RootComplex
| `-- 01:00.00 0x1957 0x4300 Bridge device 0x04
Net:
Warning: ethernet@4033c000 (eth0) using random MAC address - 3a:c5:62:45:1c:1e
eth0: ethernet@4033c000
Found PFE version 0x0101 (S32G3)
, eth1: pfe0, eth2: pfe1, eth3: pfe2
Hit any key to stop autoboot: 0
switch to partitions #0, OK
mmc0 is current device
14479368 bytes read in 608 ms (22.7 MiB/s)
Booting from mmc ...
59970 bytes read in 7 ms (8.2 MiB/s)
## Error: "fdt_fixups" not defined
## Flattened Device Tree blob at 83000000
Booting using the fdt blob at 0x83000000
Using Device Tree in place at 0000000083000000, end 0000000083011a41
fixup: pfe1: update phy addr to 0x8

Starting kernel ...

[ 0.000000] Booting Linux on physical CPU 0x0000000000 [0x410fd034]
[ 0.000000] Linux version 5.15.129-rt67+gcdac0506874b (oe-user@oe-host) (aarch64-fsl-linux-gcc (GCC) 11.4.0, GNU ld (GNU Binutils) 2.38.20220708) #1 SMP PREEMPT Mon Dec 4 08:50:24 U3
[ 0.000000] Machine model: NXP S32G399A-RDB3
[ 0.000000] earlycon: linflex0 at MMIO 0x00000000401c8000 (options '115200n8')
[ 0.000000] printk: bootconsole [linflex0] enabled
[ 0.000000] Reserved memory: created DMA memory pool at 0x0000000083200000, size 3 MiB
[ 0.000000] OF: reserved mem: initialized node pfebufs@83200000, compatible id shared-dma-pool
[ 0.000000] Zone ranges:
[ 0.000000] DMA [mem 0x0000000080000000-0x00000000ffffffff]
[ 0.000000] DMA32 empty
[ 0.000000] Normal [mem 0x0000000100000000-0x00000008dfffffff]
[ 0.000000] Movable zone start for each node
[ 0.000000] Early memory node ranges
[ 0.000000] node 0: [mem 0x0000000080000000-0x00000000831fffff]
[ 0.000000] node 0: [mem 0x0000000083200000-0x00000000835dffff]
[ 0.000000] node 0: [mem 0x00000000835e0000-0x0000000083ffffff]
[ 0.000000] node 0: [mem 0x0000000084000000-0x00000000843fffff]
[ 0.000000] node 0: [mem 0x0000000084400000-0x00000000bfffffff]
[ 0.000000] node 0: [mem 0x00000000c0000000-0x00000000c07fffff]
[ 0.000000] node 0: [mem 0x00000000c0800000-0x00000000cfffffff]
[ 0.000000] node 0: [mem 0x00000000d0001000-0x00000000ff7fffff]
[ 0.000000] node 0: [mem 0x00000000ff800000-0x00000000ff9fffff]
[ 0.000000] node 0: [mem 0x00000000ffa00000-0x00000000ffffffff]
[ 0.000000] node 0: [mem 0x0000000880000000-0x00000008dfffffff]
[ 0.000000] Initmem setup node 0 [mem 0x0000000080000000-0x00000008dfffffff]
[ 0.000000] On node 0, zone DMA: 1 pages in unavailable ranges
[ 0.000000] cma: Reserved 256 MiB at 0x00000000ef800000
[ 0.000000] psci: probing for conduit method from DT.
[ 0.000000] psci: PSCIv1.1 detected in firmware.
[ 0.000000] psci: Using standard PSCI v0.2 function IDs
[ 0.000000] psci: MIGRATE_INFO_TYPE not supported.
[ 0.000000] psci: SMC Calling Convention v1.2
[ 0.000000] percpu: Embedded 18 pages/cpu s33560 r8192 d31976 u73728
[ 0.000000] pcpu-alloc: s33560 r8192 d31976 u73728 alloc=18*4096
[ 0.000000] pcpu-alloc: [0] 0 [0] 1 [0] 2 [0] 3 [0] 4 [0] 5 [0] 6 [0] 7
[ 0.000000] Detected VIPT I-cache on CPU0
[ 0.000000] CPU features: detected: GIC system register CPU interface
[ 0.000000] CPU features: detected: ARM erratum 845719
[ 0.000000] CPU features: detected: ARM errata 1165522, 1319367, 1530923, or 1530924
[ 0.000000] Built 1 zonelists, mobility grouping on. Total pages: 904959
[ 0.000000] Kernel command line: console=ttyLF0,115200 root=/dev/mmcblk0p2 rootwait rw earlycon
[ 0.000000] Dentry cache hash table entries: 524288 (order: 10, 4194304 bytes, linear)
[ 0.000000] Inode-cache hash table entries: 262144 (order: 9, 2097152 bytes, linear)
[ 0.000000] mem auto-init: stack:off, heap alloc:off, heap free:off
[ 0.000000] software IO TLB: mapped [mem 0x00000000eb800000-0x00000000ef800000] (64MB)
[ 0.000000] Memory: 3243240K/3670012K available (9024K kernel code, 636K rwdata, 3016K rodata, 1344K init, 214K bss, 164628K reserved, 262144K cma-reserved)
[ 0.000000] rcu: Preemptible hierarchical RCU implementation.
[ 0.000000] rcu: RCU event tracing is enabled.
[ 0.000000] Trampoline variant of Tasks RCU enabled.
[ 0.000000] Tracing variant of Tasks RCU enabled.
[ 0.000000] rcu: RCU calculated value of scheduler-enlistment delay is 25 jiffies.
[ 0.000000] NR_IRQS: 64, nr_irqs: 64, preallocated irqs: 0
[ 0.000000] GICv3: 544 SPIs implemented
[ 0.000000] GICv3: 0 Extended SPIs implemented
[ 0.000000] GICv3: Distributor has no Range Selector support
[ 0.000000] GICv3: MBI range [167:182]
[ 0.000000] GICv3: Using MBI frame 0x0000000050800000
[ 0.000000] Root IRQ handler: gic_handle_irq
[ 0.000000] GICv3: 16 PPIs implemented
[ 0.000000] GICv3: CPU0: found redistributor 0 region 0:0x0000000050900000
[ 0.000000] ITS: No ITS available, not enabling LPIs
[ 0.000000] arch_timer: cp15 timer(s) running at 5.00MHz (virt).
[ 0.000000] clocksource: arch_sys_counter: mask: 0xffffffffffffff max_cycles: 0x127350b88, max_idle_ns: 440795202120 ns
[ 0.000000] sched_clock: 56 bits at 5MHz, resolution 200ns, wraps every 4398046511100ns
[ 0.008554] Console: colour dummy device 80x25
[ 0.008596] Calibrating delay loop (skipped), value calculated using timer frequency.. 10.00 BogoMIPS (lpj=20000)
[ 0.022855] pid_max: default: 32768 minimum: 301
[ 0.027613] Mount-cache hash table entries: 8192 (order: 4, 65536 bytes, linear)
[ 0.034842] Mountpoint-cache hash table entries: 8192 (order: 4, 65536 bytes, linear)
[ 0.044096] rcu: Hierarchical SRCU implementation.
[ 0.049070] smp: Bringing up secondary CPUs ...
[ 0.053708] Detected VIPT I-cache on CPU1
[ 0.057302] GICv3: CPU1: found redistributor 1 region 0:0x0000000050920000
[ 0.064163] CPU1: Booted secondary processor 0x0000000001 [0x410fd034]
[ 0.071185] Detected VIPT I-cache on CPU2
[ 0.074766] GICv3: CPU2: found redistributor 2 region 0:0x0000000050940000
[ 0.081624] CPU2: Booted secondary processor 0x0000000002 [0x410fd034]
[ 0.088645] Detected VIPT I-cache on CPU3
[ 0.092224] GICv3: CPU3: found redistributor 3 region 0:0x0000000050960000
[ 0.099084] CPU3: Booted secondary processor 0x0000000003 [0x410fd034]
[ 0.106111] Detected VIPT I-cache on CPU4
[ 0.109704] GICv3: CPU4: found redistributor 100 region 0:0x0000000050980000
[ 0.116742] CPU4: Booted secondary processor 0x0000000100 [0x410fd034]
[ 0.123788] Detected VIPT I-cache on CPU5
[ 0.127370] GICv3: CPU5: found redistributor 101 region 0:0x00000000509a0000
[ 0.134400] CPU5: Booted secondary processor 0x0000000101 [0x410fd034]
[ 0.141448] Detected VIPT I-cache on CPU6
[ 0.145029] GICv3: CPU6: found redistributor 102 region 0:0x00000000509c0000
[ 0.152060] CPU6: Booted secondary processor 0x0000000102 [0x410fd034]
[ 0.159087] Detected VIPT I-cache on CPU7
[ 0.162670] GICv3: CPU7: found redistributor 103 region 0:0x00000000509e0000
[ 0.169702] CPU7: Booted secondary processor 0x0000000103 [0x410fd034]
[ 0.176273] smp: Brought up 1 node, 8 CPUs
[ 0.180292] SMP: Total of 8 processors activated.
[ 0.184971] CPU features: detected: 32-bit EL0 Support
[ 0.190103] CPU features: detected: CRC32 instructions
[ 0.202253] CPU: All CPU(s) started at EL1
[ 0.205944] alternatives: patching kernel code
[ 0.211500] devtmpfs: initialized
[ 0.221633] clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 7645041785100000 ns
[ 0.230959] futex hash table entries: 2048 (order: 5, 131072 bytes, linear)
[ 0.245077] pinctrl core: initialized pinctrl subsystem
[ 0.250681] NET: Registered PF_NETLINK/PF_ROUTE protocol family
[ 0.257569] DMA: preallocated 512 KiB GFP_KERNEL pool for atomic allocations
[ 0.264327] DMA: preallocated 512 KiB GFP_KERNEL|GFP_DMA pool for atomic allocations
[ 0.272094] DMA: preallocated 512 KiB GFP_KERNEL|GFP_DMA32 pool for atomic allocations
[ 0.280164] thermal_sys: Registered thermal governor 'step_wise'
[ 0.280798] hw-breakpoint: found 6 breakpoint and 4 watchpoint registers.
[ 0.293269] ASID allocator initialised with 65536 entries
[ 0.298575] Serial: AMBA PL011 UART driver
[ 0.303414] arm-scmi firmware:scmi: Enabled polling mode TX channel - prot_id:16
[ 0.310498] arm-scmi firmware:scmi: SCMI Notifications - Core Enabled.
[ 0.316934] arm-scmi firmware:scmi: SCMI Protocol v2.0 'NXP:S32G399A' Firmware version 0x0
[ 0.346336] HugeTLB registered 1.00 GiB page size, pre-allocated 0 pages
[ 0.352619] HugeTLB registered 32.0 MiB page size, pre-allocated 0 pages
[ 0.359299] HugeTLB registered 2.00 MiB page size, pre-allocated 0 pages
[ 0.365993] HugeTLB registered 64.0 KiB page size, pre-allocated 0 pages
[ 0.380147] vgaarb: loaded
[ 0.382583] SCSI subsystem initialized
[ 0.386274] usbcore: registered new interface driver usbfs
[ 0.391648] usbcore: registered new interface driver hub
[ 0.396948] usbcore: registered new device driver usb
[ 0.402286] pps_core: LinuxPPS API ver. 1 registered
[ 0.406899] pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo Giometti <giometti@linux.it>
[ 0.416022] PTP clock support registered
[ 0.420774] clocksource: Switched to clocksource arch_sys_counter
[ 0.431506] NET: Registered PF_INET protocol family
[ 0.436124] IP idents hash table entries: 65536 (order: 7, 524288 bytes, linear)
[ 0.444721] tcp_listen_portaddr_hash hash table entries: 2048 (order: 3, 32768 bytes, linear)
[ 0.452887] Table-perturb hash table entries: 65536 (order: 6, 262144 bytes, linear)
[ 0.460541] TCP established hash table entries: 32768 (order: 6, 262144 bytes, linear)
[ 0.468637] TCP bind hash table entries: 32768 (order: 7, 524288 bytes, linear)
[ 0.476236] TCP: Hash tables configured (established 32768 bind 32768)
[ 0.482429] UDP hash table entries: 2048 (order: 4, 65536 bytes, linear)
[ 0.489079] UDP-Lite hash table entries: 2048 (order: 4, 65536 bytes, linear)
[ 0.496339] NET: Registered PF_UNIX/PF_LOCAL protocol family
[ 0.502119] RPC: Registered named UNIX socket transport module.
[ 0.507677] RPC: Registered udp transport module.
[ 0.512360] RPC: Registered tcp transport module.
[ 0.517046] RPC: Registered tcp NFSv4.1 backchannel transport module.
[ 0.523476] PCI: CLS 0 bytes, default 64
[ 0.528182] hw perfevents: enabled with armv8_pmuv3 PMU driver, 7 counters available
[ 0.536666] workingset: timestamp_bits=62 max_order=20 bucket_order=0
[ 0.543402] fuse: init (API version 7.34)
[ 0.547115] NET: Registered PF_ALG protocol family
[ 0.551798] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 248)
[ 0.559131] io scheduler mq-deadline registered
[ 0.563643] io scheduler kyber registered
[ 0.569659] s32g-siul2-pinctrl 4009c240.siul2-pinctrl: Initialized s32cc pinctrl driver
[ 0.577535] arm-scmi firmware:scmi: Failed. SCMI protocol 128 not active.
[ 0.584141] arm-scmi firmware:scmi: Failed. SCMI protocol 129 not active.
[ 0.591490] gpio-345 (sja1110-rst-phy-t1): hogged as output/low
[ 0.596990] gpio-402 (sja1110-rst-core): hogged as output/low
[ 0.613703] printk: console [ttyLF0] enabled0x401c8000 (irq = 46, base_baud = 7812500) is a FSL_LINFLEX
[ 0.613703] printk: console [ttyLF0] enabled
[ 0.622350] printk: bootconsole [linflex0] disabled
[ 0.622350] printk: bootconsole [linflex0] disabled
[ 0.632454] 401cc000.serial: ttyLF1 at MMIO 0x401cc000 (irq = 47, base_baud = 7812500) is a FSL_LINFLEX
[ 0.642228] 402bc000.serial: ttyLF2 at MMIO 0x402bc000 (irq = 68, base_baud = 7812500) is a FSL_LINFLEX
[ 0.653242] s32cc_fccu 4030c000.fccu: FCCU status is 0 (normal)
[ 0.661200] sja1110-sw@1 enforce active low on chipselect handle
[ 0.669463] spi-nor spi6.0: mx25uw51245g (65536 Kbytes)
[ 0.675053] 7 fixed-partitions partitions found on MTD device 0.spi
[ 0.681411] Creating 7 MTD partitions on "0.spi":
[ 0.686182] 0x000000000000-0x000004000000 : "Flash-Image"
[ 0.691887] 0x000000000000-0x000000280000 : "FIP"
[ 0.696875] 0x000000280000-0x000000290000 : "U-Boot-Env"
[ 0.702468] 0x000000290000-0x000001160000 : "Kernel"
[ 0.707713] 0x000001160000-0x000001190000 : "DTB"
[ 0.712689] 0x000001190000-0x0000030a0000 : "Rootfs"
[ 0.717925] 0x0000030a0000-0x000004000000 : "PFE-Firmware"
[ 0.724783] vcan: Virtual CAN interface driver
[ 0.729289] slcan: serial line CAN interface driver
[ 0.734230] slcan: 10 dynamic interface channels.
[ 0.739000] CAN device driver interface
[ 0.743626] flexcan 401b4000.flexcan: device registered (reg_base=(____ptrval____), irq(s):
[ 0.752097] flexcan 401b4000.flexcan: 38
[ 0.756163] flexcan 401b4000.flexcan: 39
[ 0.760226] flexcan 401b4000.flexcan: 40
[ 0.764289] flexcan 401b4000.flexcan: 41
[ 0.768356] flexcan 401b4000.flexcan: )
[ 0.772797] flexcan 401be000.flexcan: device registered (reg_base=(____ptrval____), irq(s):
[ 0.781294] flexcan 401be000.flexcan: 42
[ 0.785368] flexcan 401be000.flexcan: 43
[ 0.789440] flexcan 401be000.flexcan: 44
[ 0.793511] flexcan 401be000.flexcan: 45
[ 0.797584] flexcan 401be000.flexcan: )
[ 0.801687] e100: Intel(R) PRO/100 Network Driver
[ 0.806466] e100: Copyright(c) 1999-2006 Intel Corporation
[ 0.812072] e1000: Intel(R) PRO/1000 Network Driver
[ 0.817026] e1000: Copyright (c) 1999-2006 Intel Corporation.
[ 0.822888] e1000e: Intel(R) PRO/1000 Network Driver
[ 0.827929] e1000e: Copyright(c) 1999 - 2015 Intel Corporation.
[ 0.833968] igb: Intel(R) Gigabit Ethernet Network Driver
[ 0.839451] igb: Copyright (c) 2007-2014 Intel Corporation.
[ 0.845932] hse-uio 40210000.mu0b: firmware not found
[ 0.851268] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
[ 0.857903] ehci-pci: EHCI PCI platform driver
[ 0.862553] usbcore: registered new interface driver uas
[ 0.867982] usbcore: registered new interface driver usb-storage
[ 0.875681] s32cc-rtc 40060000.rtc: registered as rtc0
[ 0.880940] s32cc-rtc 40060000.rtc: setting system clock to 1970-01-01T00:00:00 UTC (0)
[ 0.889152] i2c_dev: i2c /dev entries driver
[ 0.893789] s32cc-wdt 4010c000.watchdog: S32CC Watchdog Timer Registered. timeout=30s (nowayout=0)
[ 0.903022] s32cc-wdt 40200000.watchdog: S32CC Watchdog Timer Registered. timeout=30s (nowayout=0)
[ 0.912243] s32cc-wdt 40204000.watchdog: S32CC Watchdog Timer Registered. timeout=30s (nowayout=0)
[ 0.921462] s32cc-wdt 40208000.watchdog: S32CC Watchdog Timer Registered. timeout=30s (nowayout=0)
[ 0.930700] s32cc-wdt 40500000.watchdog: S32CC Watchdog Timer Registered. timeout=30s (nowayout=0)
[ 0.939916] s32cc-wdt 40504000.watchdog: S32CC Watchdog Timer Registered. timeout=30s (nowayout=0)
[ 0.949140] s32cc-wdt 40508000.watchdog: S32CC Watchdog Timer Registered. timeout=30s (nowayout=0)
[ 0.958358] s32cc-wdt 4050c000.watchdog: S32CC Watchdog Timer Registered. timeout=30s (nowayout=0)
[ 0.968821] sdhci: Secure Digital Host Controller Interface driver
[ 0.975100] sdhci: Copyright(c) Pierre Ossman
[ 0.979524] sdhci-pltfm: SDHCI platform and OF driver helper
[ 0.985479] SMCCC: SOC_ID: ARCH_SOC_ID not implemented, skipping ....
[ 0.985974] mmc0: CQHCI version 5.10
[ 0.992338] hse 40211000.mu1b: interface mu1b not active
[ 1.001349] usbcore: registered new interface driver usbhid
[ 1.007013] usbhid: USB HID core driver
[ 1.023320] s32-adc 401f8000.adc: using dma0chan4 for ADC DMA transfers
[ 1.024803] mmc0: SDHCI controller on 402f0000.mmc [402f0000.mmc] using ADMA
[ 1.030401] s32-adc 401f8000.adc: Device initialized successfully.
[ 1.055778] s32-adc 402e8000.adc: using dma1chan18 for ADC DMA transfers
[ 1.062910] s32-adc 402e8000.adc: Device initialized successfully.
[ 1.069829] s32-siul2-nvmem 4009c000.nvram: Initialized s32cc siul2 nvmem driver
[ 1.077456] s32-siul2-nvmem 44010000.nvram: Initialized s32cc siul2 nvmem driver
[ 1.085069] arm-scmi firmware:scmi: Failed. SCMI protocol 130 not active.
[ 1.092498] NET: Registered PF_INET6 protocol family
[ 1.093370] mmc0: new ultra high speed SDR104 SDHC card at address 0001
[ 1.098223] Segment Routing with IPv6
[ 1.104694] mmcblk0: mmc0:0001 SD32G 28.8 GiB
[ 1.107986] In-situ OAM (IOAM) with IPv6
[ 1.116461] sit: IPv6, IPv4 and MPLS over IPv4 tunneling driver
[ 1.122819] NET: Registered PF_PACKET protocol family
[ 1.128060] can: controller area network core
[ 1.132520] NET: Registered PF_CAN protocol family
[ 1.137389] can: raw protocol
[ 1.140399] can: broadcast manager protocol
[ 1.144664] can: netlink gateway - max_hops=1
[ 1.149113] 8021q: 802.1Q VLAN Support v1.8
[ 1.153539] printk: console [ttyLF0]: printing thread started
[ 1.165790] i2c i2c-0: using pinctrl states for GPIO recovery
[ 1.165855] i2c i2c-0: using generic GPIOs for recovery
[ 1.166028] pca953x 0-0022: using AI
[ 1.173036] rtc-pcf85063 0-0051: registered as rtc1
[ 1.173068] i2c i2c-0: IMX I2C adapter registered
[ 1.173111] i2c i2c-0: using dma0chan5 (tx) and dma0chan6 (rx) for DMA transfers
[ 1.173494] i2c i2c-2: using pinctrl states for GPIO recovery
[ 1.173532] i2c i2c-2: using generic GPIOs for recovery
[ 1.173597] i2c i2c-2: IMX I2C adapter registered
[ 1.173633] i2c i2c-2: using dma1chan19 (tx) and dma1chan20 (rx) for DMA transfers
[ 1.174008] i2c i2c-4: using pinctrl states for GPIO recovery
[ 1.174044] i2c i2c-4: using generic GPIOs for recovery
[ 1.175422] ina2xx 4-0040: power monitor ina231 (Rshunt = 1000 uOhm)
[ 1.175452] i2c i2c-4: IMX I2C adapter registered
[ 1.175482] i2c i2c-4: using dma1chan21 (tx) and dma1chan22 (rx) for DMA transfers
[ 1.175893] phy-s32cc-serdes 40480000.serdes: Using mode 0 for SerDes subsystem
[ 1.176225] phy-s32cc-serdes 44180000.serdes: Using mode 3 for SerDes subsystem
[ 1.203184] phy-s32cc-serdes 44180000.serdes: Unstable RX detected on XPCS1
[ 1.203203] phy-s32cc-serdes 44180000.serdes: Unstable RX detected on XPCS0
[ 1.203368] s32cc-pcie 40400000.pcie: Configured as RootComplex
[ 1.212864] blk_update_request: I/O error, dev mmcblk0, sector 0 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
[ 1.212878] Buffer I/O error on dev mmcblk0, logical block 0, async page read
[ 1.251007] blk_update_request: I/O error, dev mmcblk0, sector 0 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
[ 1.251017] Buffer I/O error on dev mmcblk0, logical block 0, async page read
[ 1.251033] mmcblk0: unable to read partition table
[ 2.204526] s32cc-pcie 40400000.pcie: Failed to stabilize PHY link
[ 2.204534] s32cc-pcie 40400000.pcie: Configuring as RootComplex
[ 2.204558] s32cc-pcie 40400000.pcie: host bridge /soc/pcie@40400000 ranges:
[ 2.204588] s32cc-pcie 40400000.pcie: IO 0x5ffffe0000..0x5ffffeffff -> 0x0000000000
[ 2.204605] s32cc-pcie 40400000.pcie: MEM 0x5800000000..0x5ffffdffff -> 0x0000000000
[ 2.204626] s32cc-pcie 40400000.pcie: Memory resource size exceeds max for 32 bits
[ 2.204654] s32cc-pcie 40400000.pcie: Resources exceed number of ATU entries (0)
[ 3.204813] s32cc-pcie 40400000.pcie: Phy link never came up
[ 3.204838] s32cc-pcie 40400000.pcie: iATU unroll: enabled
[ 3.204844] s32cc-pcie 40400000.pcie: Detected iATU regions: 6 outbound, 4 inbound
[ 4.205014] s32cc-pcie 40400000.pcie: Phy link never came up
[ 5.205122] s32cc-pcie 40400000.pcie: Phy link never came up
[ 5.205211] s32cc-pcie 40400000.pcie: PCI host bridge to bus 0000:00
[ 5.205218] pci_bus 0000:00: root bus resource [bus 00-ff]
[ 5.205227] pci_bus 0000:00: root bus resource [io 0x0000-0xffff]
[ 5.205233] pci_bus 0000:00: root bus resource [mem 0x5800000000-0x5ffffdffff] (bus address [0x00000000-0x7fffdffff])
[ 5.205279] pci 0000:00:00.0: [1957:4300] type 01 class 0x060400
[ 5.205303] pci 0000:00:00.0: reg 0x10: [mem 0x5800000000-0x58000fffff]
[ 5.205323] pci 0000:00:00.0: reg 0x38: [mem 0x5800000000-0x580000ffff pref]
[ 5.205416] pci 0000:00:00.0: supports D1
[ 5.205421] pci 0000:00:00.0: PME# supported from D0 D1 D3hot D3cold
[ 5.210572] pci 0000:00:00.0: BAR 0: assigned [mem 0x5800000000-0x58000fffff]
[ 5.210584] pci 0000:00:00.0: BAR 6: assigned [mem 0x5800100000-0x580010ffff pref]
[ 5.210592] pci 0000:00:00.0: PCI bridge to [bus 01-ff]
[ 5.210842] pcieport 0000:00:00.0: PME: Signaling with IRQ 93
[ 5.211591] s32cc-dwmac 4033c000.ethernet: IRQ eth_wake_irq not found
[ 5.211597] s32cc-dwmac 4033c000.ethernet: IRQ eth_lpi not found
[ 5.211958] s32cc-dwmac 4033c000.ethernet: User ID: 0x10, Synopsys ID: 0x52
[ 5.211968] s32cc-dwmac 4033c000.ethernet: DWMAC4/5
[ 5.211975] s32cc-dwmac 4033c000.ethernet: DMA HW capability register supported
[ 5.211980] s32cc-dwmac 4033c000.ethernet: RX Checksum Offload Engine supported
[ 5.211984] s32cc-dwmac 4033c000.ethernet: TX Checksum insertion supported
[ 5.211987] s32cc-dwmac 4033c000.ethernet: Wake-Up On Lan supported
[ 5.212025] s32cc-dwmac 4033c000.ethernet: Enabled workarounds for s32g274a platform
[ 5.212029] s32cc-dwmac 4033c000.ethernet: Enable RX Mitigation via HW Watchdog Timer
[ 5.212035] s32cc-dwmac 4033c000.ethernet: Enabled L3L4 Flow TC (entries=8)
[ 5.212040] s32cc-dwmac 4033c000.ethernet: Enabled RFS Flow TC (entries=8)
[ 5.212051] s32cc-dwmac 4033c000.ethernet: Enabling HW TC (entries=256, max_off=256)
[ 5.212058] s32cc-dwmac 4033c000.ethernet: Using 32 bits DMA width
[ 5.217095] hwmon hwmon1: temp1_input not attached to any thermal zone
[ 5.219146] imx_usb 44064000.usb: No over current polarity defined
[ 5.233422] ci_hdrc ci_hdrc.0: EHCI Host Controller
[ 5.233534] ci_hdrc ci_hdrc.0: new USB bus registered, assigned bus number 1
[ 5.252772] ci_hdrc ci_hdrc.0: USB 2.0 started, EHCI 1.00
[ 5.252900] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002, bcdDevice= 5.15
[ 5.252908] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[ 5.252914] usb usb1: Product: EHCI Host Controller
[ 5.252918] usb usb1: Manufacturer: Linux 5.15.129-rt67+gcdac0506874b ehci_hcd
[ 5.252922] usb usb1: SerialNumber: ci_hdrc.0
[ 5.253222] hub 1-0:1.0: USB hub found
[ 5.253246] hub 1-0:1.0: 1 port detected
[ 5.254735] nxp_s32cc_ddr_perf 403e0000.ddr-perf: probing device
[ 5.254912] nxp_s32cc_ddr_perf 403e0000.ddr-perf: device initialized successfully
[ 5.281288] VFS: Cannot open root device "mmcblk0p2" or unknown-block(179,2): error -6
[ 5.281295] Please append a correct "root=" boot option; here are the available partitions:
[ 5.281303] b300 30216192 mmcblk0
[ 5.281308] driver: mmcblk
[ 5.281312] Kernel panic - not syncing:
[ 5.281314] VFS: Unable to mount root fs on unknown-block(179,2)
[ 5.587082] SMP: stopping secondary CPUs
[ 5.596565] Kernel Offset: disabled
[ 5.600028] CPU features: 0x8,00002001,20000842
[ 5.604540] Memory Limit: none
[ 5.607584] ---[ end Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(179,2) ]---

I tried 3 sdcard and get the same failure as above, the previous attached log is used SDK BSP39 project image, which is built by myself.

Would you please help to check it in your local?

Thanks,

Zhantao

Re: pfe1 connection fail with 2.5G on RDB3 SDK BSP39

chenyin_h — Wed, 31 Jan 2024 09:07:46 GMT

Hello, @hittzt

Thank you for the reply.

I tried the pre-built images following your previous post on my local board, but did not reproduce your booting issue, the logs are attached for your reference.

May I know if you had checked the content of the mmcblk0p2 partition of your SD card when met the boot issue? Have you used the sync command before un-plugging the SD card after dd operation?

Best Regards

Chenyin

Re: pfe1 connection fail with 2.5G on RDB3 SDK BSP39

hittzt — Fri, 02 Feb 2024 02:51:53 GMT

Hi,

Yes, I will change to use new SD card to check the status again.

And as you said, the prebuilt image can boot up normally on RDB3, did you test the pfe1 connection status(with 2.5G and connect to another RDB3 board 2.5G pfe1 port)?

Thanks,

Zhantao

Re: pfe1 connection fail with 2.5G on RDB3 SDK BSP39

chenyin_h — Fri, 02 Feb 2024 09:52:55 GMT

Hello, @hittzt

Thanks for the reply.

I feel sorry that I did not test it because of only 1 RDB3 in hand, I am now looking for another board to have a test for the 2.5G network interface on S32G3.

Additionally, may I know if you could try testing it on other version BSP? Like BSP38, then it is helpful for us to locate the root cause.

Sorry for the delay

Best Regards

Chenyin

Re: pfe1 connection fail with 2.5G on RDB3 SDK BSP39

chenyin_h — Mon, 05 Feb 2024 09:20:51 GMT

Hello, @hittzt

Sorry for the delay.

I had tested it with two RDB3, and reproduced the issue you found, thank you for your findings.

After investigation, we found that it is a bug in BSP39, our internal teams has noticed this issue and plan to have it fixed in BSP40.

As a result, currently, we recommend using the old version BSP temporally instead.

We do apologize for your inconvenience.

Best Regards

Chenyin

Re: pfe1 connection fail with 2.5G on RDB3 SDK BSP39

hittzt — Sun, 18 Feb 2024 02:10:36 GMT

Hi,

Thanks for you update.

If any new info, please let me know.

Thanks,

Zhantao

Re: pfe1 connection fail with 2.5G on RDB3 SDK BSP39

chenyin_h — Mon, 19 Feb 2024 02:00:13 GMT

Hello, @hittzt

Thanks for the reply.

Sure, you may try this feature when BSP40 released, if any other issue found, feel free to raise a new ticket, we are happy to help.

Best Regards

Chenyin

Re: pfe1 connection fail with 2.5G on RDB3 SDK BSP39

hittzt — Mon, 19 Feb 2024 02:12:39 GMT

Hi,

OK, got it.

Thanks for you reply.

Thanks,

Zhantao