s32g2 QNX PFE driver

miles_yang — Fri, 03 Apr 2026 09:24:10 GMT

Hi Teams,

software information:
PFE QNX driver version: 1.8.0
PFE FW version: 1.11.0
QNX SDP version: 7.1.0
Uboot ATF BSP39.0
When I made these changes:

struct udevice *dev = NULL;

const struct eth_ops* opsptr;

char cmd[128];

/* Enable GMAC eqos eth */

ret = uclass_get_device_by_name(UCLASS_ETH, "ethernet@4033c000", &dev);

opsptr = DM_DRIVER_GET(eth_eqos)->ops;

ret = opsptr->start(dev);

/* Enable PFE driver */

uclass_get_device_by_name(UCLASS_MISC, "pfeng-base", &dev);

DM_DRIVER_GET(pfeng)->probe(dev);

uclass_get_device_by_name(UCLASS_ETH, "pfe2", &dev);

opsptr = DM_DRIVER_GET(pfeng_netif)->ops;

opsptr->start(dev);

uclass_get_device_by_name(UCLASS_ETH,"pfe1",&dev);

opsptr = DM_DRIVER_GET(pfeng_netif)->ops;

opsptr->start(dev);

uclass_get_device_by_name(UCLASS_ETH,"pfe0",&dev);

opsptr = DM_DRIVER_GET(pfeng_netif)->ops;

opsptr->start(dev);

snprintf(cmd, sizeof(cmd), "scmi_clk gate protocol@14 pfe_ts 1");

run_command(cmd, 0);

snprintf(cmd, sizeof(cmd), "scmi_clk gate protocol@14 ftm 1");

run_command(cmd, 0);
And use these commands to start the QNX system
setenv boot_qnx_atf 'mmc dev 0; fatload mmc 0:1 0x83e00000 s32g274a-rdb2.dtb; run atf_fdt_0to3; run
release_cpus; fatload mmc 0:1 0x80080000 ifs-s32g274a-rdb.ui; bootm 0x80080000 - 0x83E00000'
setenv atf_fdt_0to3 'fdt addr 0x83e00000; fdt resize; fdt set /cpus/cpu@1 cpu-release-addr <0x0
0xa0000010>; fdt set /cpus/cpu@100 cpu-release-addr <0x0 0xa0000010>; fdt set /cpus/cpu@101
cpu-release-addr <0x0 0xa0000010>;'
setenv release_cpus 'run cpu_trap; mp 1 release 0xa0000000; mp 2 release 0xa0000000; mp 3 release
0xa0000000;'
setenv cpu_trap 'dcache off; mw.l 0xa0000000 0xd503205f; mw.l 0xa0000004 0x58000060; mw.l 0xa0000008
0xb4ffffc0; mw.l 0xa000000C 0xd61f0000; mw.q 0xa0000010 0x00000000; dcache on;'
setenv bootcmd 'run boot_qnx_atf'
setenv hwconfig "serdes0:mode=pcie,clock=ext;pcie0:mode=rc;serdes1:mode=xpcs0&xpcs1,
clock=ext,fmhz=125;xpcs1_0:speed=2G5;xpcs1_1:speed=1G"
setenv skip_scmi_reset_agent '1'
saveenv
System will startup failed，

Starting kernel ...

clk pfe1_tx_sgmii already disabled
clk pfe1_rx_sgmii already disabled

Found PFE version 0x50300 (S32G2)

Found PFE version 0x50300 (S32G2)
pfe2 Waiting for PHY auto negotiation to complete......... TIMEOUT !
## Setting pfe_ts clock ...
## Setting ftm0_sys clock ...
## Setting ftm0_ext clock ...
## Setting ftm1_sys clock ...
## Setting ftm1_ext clock ...
Board: NXP S32G274A RDB2 Revision E
Error bringing up core 1 with error 0

The startup log has been uploaded to the attachment.

Best Regards
Miles

Re: s32g2 QNX PFE driver

Joey_z — Fri, 03 Apr 2026 10:14:19 GMT

Hi,miles_yang

Thank you for contacting us.

Could you share more information with me?

1.are you using the customer board or our development board RDB2/RDB3?

2.Do you only use the PFE application on the A core?

Joey

Re: s32g2 QNX PFE driver

miles_yang — Tue, 07 Apr 2026 01:21:31 GMT

Hi Joey,
I am using the customer board, and the CPU is S32G274A.
Yes, currently only core A is running. The QNX system is started via Uboot. If the above modifications are not added, the QNX system can start normally. However, after adding the modifications in PFE-DRV_S32G_QNX_1.8.0_IntegrationManual.pdf, the startup fails.
please help check.Thanks.

Best Regards,
Miles

Re: s32g2 QNX PFE driver

Joey_z — Thu, 09 Apr 2026 02:33:01 GMT

Hi,miles_yang

Thank you for your reply.

Do you want to config the PFE in U-boat stage? About the more information, you can try to refer to the 7.3 Ethernet Software support on S32G2 of S32G2_LinuxBSP_39.0_User_Manual.pdf.

Joey

S32Gのトピックs32g2 QNX PFE driver

s32g2 QNX PFE driver

Re: s32g2 QNX PFE driver

Re: s32g2 QNX PFE driver

Re: s32g2 QNX PFE driver