SV32V234-EVB2 no network

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

SV32V234-EVB2 no network

999 Views
pha1
Contributor I

Hello all,

I just received the eval board S32V234-EVB2.

I follow the instruction in Auto_Linux_BSP_20.0_User_Manual.pdf to copy the image to a sd card.

u-boot and linux came up fine but the network, eth0 doesn't work.

Even under u-boot:

=> ping 10.0.0.10

ping 10.0.0.10

Loading SJA1105 firmware over SPI 0:0

Using FEC device

ARP Retry count exceeded; starting again

ping failed; host 10.0.0.10 is not alive

=>

when linux boots up, there this error in the initialization of the SJA1105:

[    2.105259] sja1105pqrs spi0.0: Loading SJA1105P SPI driver

[    2.110579] sja1105pqrs spi0.0: Detected Device ID ae00030e ()

[    2.116356] sja1105pqrs spi0.0: Detected device id is invalid: 00000000 .  <<<<<

[    2.131918] sja1105pqrs spi0.5: Loading SJA1105P SPI driver

[    2.137230] sja1105pqrs spi0.5: Detected Device ID ae00030e ()

[    2.143018] sja1105pqrs spi0.5: Detected device id is invalid: 00000000 .   <<<<<<

[    2.160148] sja1105pqrs spi0.5: 2 switches initialized successfully!

tcpdump -i eth0 inside the eval board shows that the packets sent by the host got in, but the replies couldn't get out:

11:31:19.229980 ARP, Request who-has 10.0.0.100 tell 10.0.0.10, length 46

11:31:19.230036 ARP, Reply 10.0.0.100 is-at 00:1b:c3:12:34:22 (oui Unknown), length 28

11:31:20.228781 ARP, Request who-has 10.0.0.100 tell 10.0.0.10, length 46

11:31:20.228808 ARP, Reply 10.0.0.100 is-at 00:1b:c3:12:34:22 (oui Unknown), length 28

11:31:21.228683 ARP, Request who-has 10.0.0.100 tell 10.0.0.10, length 46

11:31:21.228704 ARP, Reply 10.0.0.100 is-at 00:1b:c3:12:34:22 (oui Unknown), length 28

the host didn't see the ARP replies.

Any suggestion to debug this is welcome.

Thank you.

Phung-Te

0 Kudos
2 Replies

816 Views
bpe
NXP Employee
NXP Employee

Hello,

Providing help with this issue may require sharing the information
which is treated as confidential info at this time and requires a
signed NDA (Non-Disclosure Agreement) between your company and NXP.

Naturally, we cannot discuss this with you in public, this requires to
be handled as a support ticket.

We will stop following this thread and contact you by email to
verify if a usable NDA is in place and to further communicate about
the technical question.

Have a great day,
Platon

-------------------------------------------------------------------------------
Note:
This thread is continued as a private discussion with the submitter,
NXP support is not following the thread anymore
-------------------------------------------------------------------------------

0 Kudos

816 Views
pha1
Contributor I

Hi all, 

I got the board to go on the network at the end but there's something I couldn't understand:

. for u-boot networking to work, I need to connect the ethernet port to the host; also I need to connect one of the automotive port to the host.

. the packets are going through the automotive port, but both ports have to be connected otherwise u-boot ping wouldn't work.

. now with the board connected as such (2 ports to the host), I can netboot the board. 

Does anyone else observe the same behavior? I would like to make sure that my board doesn't have a problem, since the document doesn't mention that I need to connect 2 ports.

Any suggestion is well appreciated. Thank you.

Phung-Te

0 Kudos