S32G399a-rdb3 PFE2 ping doesn't work

[Hesham_Gharabawy]

I'm trying to bring up QNX 8 io-sock on S32G399a-rdb3 board

bsp 44.0

PFE Driver 1.9.0

PFE FW 1.8.0

Here's what I do to call io-sock process

io_sock.cfg content : 
( if I added hw.pfe.2.phy_address="4" as mentioned in the Release notes of the driver I get no phy at loc:4

phy failed to attach )

from inside QNX :

I still can't ping the ECU from the laptop or vice versa

I tried to configure pfe from uboot ( since it's working there if configured ) then make qnx act as a slave but I got undefined reference 

What am I missing?

[MilanMucka]

Hi Hesham,

PFE driver for QNX 8.0 is only in Proof of Concept level and might have some problems which are not resolved yet.

The configuration for PFE use in QNX is a little bit tricky, you need to configure HW and clocks in u-boot before starting QNX, as we don't have SerDes implementation in QNX driver.

APP FSM timeouts means, that FSM clocks are not configured correctly.

I recommend to use u-boot BSP 39.0 with DTB and ATF. Inside this u-boot, there is PFE driver which will configure all the settings before booting QNX.

Please follow PFE QNX Integration Manual from Release package
doc/qnx_drv_im/PFE_QNX_DRV_IntegrationManual.pdf

Regards
Milan

[alejandro_e]

Hello @Hesham_Gharabawy,

Thanks for reaching out to us. Reading your problem, in this community we cannot support QNX software, since it is not an NXP product, we do not have the knowledge to helpyou, I would recommend contacting QNX support directly https://blackberry.qnx.com/en/company/contact.

With that said, I am aware that QNX uses the same boot flow and it is an unix-like OS, just as Linux. Therefore sections 7.3 Ethernet Software support on S32G3 and 7.2.2 SerDes configuration for SGMII in U-Boot may help you with your problem.

If you need support testing the ping command in u-boot alone, please let me know which port of the RDB3 you are trying to use and I can guide you.

Best regards