bsp16.0 uboot ping fail![s32v234evb 29288 rev b2]

[echozeng]

After set the ipaddr 192.168.5.xx,and then ping 192.168.5.1, failed!

log :

---------------------------------------------------------------------------------------------------------

U-Boot 2016.01 (Mar 06 2018 - 15:52:56 +0800)

CPU: NXP S32V234 V2.0 at 1000 MHz
Reset cause: unknown reset
Board: s32v234evb29288
I2C: ready
DRAM: 2 GiB
All (4) cores are up.
MMC: FSL_SDHC: 0

Forcing PCIe to Gen1 operation
phy link never came up
DEBUG_R0: 0x00278d00, DEBUG_R1: 0x08200000
In: serial
Out: serial
Err: serial
The security module (CSE3) is disabled.
Net: FEC
Hit any key to stop autoboot: 0
=>
=> ping 192.168.5.1
Loading SJA1105 firmware over SPI 0:0
Using FEC device

ARP Retry count exceeded; starting again
ping failed; host 192.168.5.1 is not alive

-----------------------------------------------------------------------------------------------

phy status:

PHY 0x00: OUI = 0x6037, Model = 0x08, Rev = 0x01, 100baseT, FDX
PHY 0x03: OUI = 0x0885, Model = 0x22, Rev = 0x02, 100baseT, FDX
PHY 0x04: OUI = 0x6037, Model = 0x08, Rev = 0x01, 100baseT, FDX
PHY 0x05: OUI = 0x0000, Model = 0x00, Rev = 0x00, 100baseT, FDX
PHY 0x06: OUI = 0x6037, Model = 0x08, Rev = 0x01, 100baseT, FDX
PHY 0x07: OUI = 0x0000, Model = 0x00, Rev = 0x00, 100baseT, FDX
PHY 0x0A: OUI = 0x6037, Model = 0x08, Rev = 0x01, 100baseT, FDX
PHY 0x0B: OUI = 0x0000, Model = 0x00, Rev = 0x00, 100baseT, FDX

phy:ksz9031 info:

0. (1140) -- PHY control register --
(8000:0000) 0.15 = 0 reset
(4000:0000) 0.14 = 0 loopback
(2040:0040) 0. 6,13 = b10 speed selection = 1000 Mbps
(1000:1000) 0.12 = 1 A/N enable
(0800:0000) 0.11 = 0 power-down
(0400:0000) 0.10 = 0 isolate
(0200:0000) 0. 9 = 0 restart A/N
(0100:0100) 0. 8 = 1 duplex = full
(0080:0000) 0. 7 = 0 collision test enable
(003f:0000) 0. 5- 0 = 0 (reserved)

1. (796d) -- PHY status register --
(8000:0000) 1.15 = 0 100BASE-T4 able
(4000:4000) 1.14 = 1 100BASE-X full duplex able
(2000:2000) 1.13 = 1 100BASE-X half duplex able
(1000:1000) 1.12 = 1 10 Mbps full duplex able
(0800:0800) 1.11 = 1 10 Mbps half duplex able
(0400:0000) 1.10 = 0 100BASE-T2 full duplex able
(0200:0000) 1. 9 = 0 100BASE-T2 half duplex able
(0100:0100) 1. 8 = 1 extended status
(0080:0000) 1. 7 = 0 (reserved)
(0040:0040) 1. 6 = 1 MF preamble suppression
(0020:0020) 1. 5 = 1 A/N complete
(0010:0000) 1. 4 = 0 remote fault
(0008:0008) 1. 3 = 1 A/N able
(0004:0004) 1. 2 = 1 link status
(0002:0000) 1. 1 = 0 jabber detect
(0001:0001) 1. 0 = 1 extended capabilities

On uboot of bsp14.0 has the same issue. refer to :

ping fail on s32v234evb 29288 board 

I use uboot  of bsp16.0, but I also can not ping  successfully now!

I want to to eth with ksz9031xxx, need I change jumper on sch-29288 rev b2?

I  check the user manual of bsp16.0, No jumper need to be adjust.

So what problem is it? Is my evb board  broken?

Thanks!

[dannica]

Hello again Echo,

Quick question: Is the entire route from the board to the other endpoint running at 1GBPS? Because by default, an s32v234evb running the bsp16.0 u-boot only supports Ethernet connections at 1GBPS. If you really need to connect at 100/10 MBPS, we can provide you with a patch that would allow you to do that.

[echozeng]

Hi，Dan Nica，

    Please push 100/10 MBPS patch (support uboot and linux  kernel) here,thanks!

[dannica · Accepted solution]

Hello Echo,

Those u-boot and Linux patches you need are still under development. As soon as any of them is available, we'll inform you. However, we cannot push them here. They will be available in a special section on Code Aurora Forum.

[dannica]

Hello Echo,

First of all, could you provide us with the log of the "printenv" command. We would like to take a look at the entire environment. Perhaps something is abnormal around there.

Furthermore, what are you pinging into? It is possible that the other end is not configured properly. Can you provide us more information regarding the configuration of the ping target?