About linux bsp 35.0 on GLDBOX

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

About linux bsp 35.0 on GLDBOX

45 Views
yangjinzhuang
Contributor III

Hello,

       I reiceived the S32G-VNP-GLDBOX, boot by SD, power on and get the boot log through UART, but when I can't see pfe0/1/2 through ifconfig, and whitch phy is eth0?  what should I do if I want to ping through ETH interface?

        

root@s32g274ardb2:/etc# ifconfig
eth0: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500
inet6 fe80::c04c:a4ff:fee9:244b prefixlen 64 scopeid 0x20<link>
ether c2:4c:a4:e9:24:4b txqueuelen 1000 (Ethernet)
RX packets 18 bytes 1080 (1.0 KiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 18 bytes 2757 (2.6 KiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
device interrupt 63 base 0x2000

lo: flags=73<UP,LOOPBACK,RUNNING> mtu 65536
inet 127.0.0.1 netmask 255.0.0.0
inet6 ::1 prefixlen 128 scopeid 0x10<host>
loop txqueuelen 1000 (Local Loopback)
RX packets 82 bytes 6220 (6.0 KiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 82 bytes 6220 (6.0 KiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

 

U-Boot 2020.04+gf30287c440 (Nov 29 2022 - 16:57:39 +0000)

CPU: NXP S32G274A rev. 2.1
Model: NXP S32G274A-RDB2
DRAM: 3.5 GiB
Ignore unsupported SCMI protocol 19
MMC: FSL_SDHC: 0
Loading Environment from MMC... OK
Configuring PCIe0 as RootComplex
PCIe0: Failed to get link up
PCI: Failed autoconfig bar 20
PCI: Failed autoconfig bar 24
In: serial@401c8000
Out: serial@401c8000
Err: serial@401c8000
Board revision: RDB3 Revision E
Net: EQOS phy: rgmii @ 1

 

 

 


Welcome to Auto Linux BSP 35.0 (gatesgarth)!

 

 

0 Kudos
5 Replies

2 Views
chenyin_h
NXP Employee
NXP Employee

Thanks for the reply

  1. From the snapshot shared, we could noticed that the GMAC and PFE0-2 could be seen under Linux.
  2. hwconfig is a uboot variable, in order to show the content of it, you may use the print hwconfig

I suggest reading the chapter7 of BSP35UM in advance, it detailed described the settings/usage of the GMAC/PFE under u-boot/Linux.

Hope it helps.

 

Best Regards

Chenyin

 

0 Kudos

29 Views
chenyin_h
NXP Employee
NXP Employee

Hello, @yangjinzhuang 

Thanks for the question.

In general, eth0 is the GMAC port, would you please share the following two results?

  1. hwconfig under u-boot prompt.
  2. Ifconfig -a under Linux shell

There should be pfex which stand for the PFE related ports

 

Best Regards

Chenyin

0 Kudos

13 Views
yangjinzhuang
Contributor III

yangjinzhuang_1-1718762561951.png

 

0 Kudos

12 Views
yangjinzhuang
Contributor III

yangjinzhuang_0-1718763089797.pngyangjinzhuang_1-1718763111705.png

 

 

0 Kudos

3 Views
yangjinzhuang
Contributor III

Hello,

         If  I build linux-BSP source code myself,  there are some targets choise as follow.

        1、what is target fsl-image-networking  or fsl-image-networking-full ?  

        2、what is the difference between  fsl-image-networking  and fsl-image-networking-full?

        3、which target is for PFE include?

        4、where can I get the PFE user manual doc?

 

 

You can now run 'bitbake <target>'

 

Targets specific to NXP:

    fsl-image-mfgtool-initramfs

    fsl-image-itb

    fsl-image-blueboxdt

    fsl-image-auto

    fsl-image-bluebox

    fsl-image-networking

    fsl-image-dom0less

    fsl-image-flash

    fsl-image-blueboxsdfactory

    fsl-image-base

    fsl-image-blueboxbootflash

    fsl-image-ubuntu-base

    fsl-image-ubuntu-ros

    fsl-image-fit

    fsl-image-base-fit

    fsl-image-itbflash

    fsl-image-networking-full

    fsl-image-ubuntu

    fsl-image-sim

To return to this build environment later please run:

    .

0 Kudos