I have a LS1021A board (rev A0) on which I'm trying to have a simple ethernet connection. I've tried several SDK (uboot+kernel+dtb), each time I flash uboot on a SD card, boot it, load the kernel/rootfs/dtb by tftp (with any ethernet port) and start it.
Once Linux has started, I can't reach anymore the network, I can set ip address for each interface but impossible to establish a connection with my computer. I have the message
libphy: mdio@2d24000:00 - Link is Down
libphy: mdio@2d24000:00 - Link is Up - 1000/Full
When I plug/unplug the ethernet cable but it's strange that if I have a ping command while unplugging it I don't get the message "Network is unreachable". When I use Wireshark on my computer, most of the time there are no packets at all going through, but sometimes I can see the ping coming, my computer acknowledge it but on the board it is not received...
I've tried several configurations but none of them works. My switch configuration is the default one :
SW2 ON  OFF  OFF  OFF  ON  ON  ON  ON 
SW3 OFF ON ON OFF OFF ON OFF ON
I don't know if there is anything linked to the RCW. Here is my uboot env :
U-Boot 2015.01+ls1+g3281947 (Jul 30 2015 - 20:01:52)
CPU: Freescale LayerScape LS1021E, Version: 2.0, (0x87081120)
Bus:300 MHz, DDR:800 MHz (1600 MT/s data rate),
Reset Configuration Word (RCW):
00000000: 0608000a 00000000 00000000 00000000
00000010: 70000000 00007900 e0025a00 21046000
00000020: 00000000 00000000 00000000 20000000
00000030: 00080000 881b7340 00000000 00000000
DRAM: 1 GiB
Using SERDES1 Protocol: 112 (0x70)
Firmware 'Microcode version 0.0.1 for LS1021a r1.0' for 1021 V1.0
QE: uploading microcode 'Microcode for LS1021a r1.0' version 0.0.1
Flash: 128 MiB
MMC: FSL_SDHC: 0
EEPROM: NXID v1
PCIe1: Root Complex no link, regs @ 0x3400000
PCIe2: Root Complex no link, regs @ 0x3500000
SEC0: RNG instantiated
SATA link 0 timeout.
AHCI 0001.0300 1 slots 1 ports ? Gbps 0x1 impl SATA mode
flags: 64bit ncq pm clo only pmp fbss pio slum part ccc
scanning bus for devices...
Found 0 device(s).
SCSI: Net: eTSEC2 is in sgmii mode.
eTSEC1, eTSEC2 [PRIME], eTSEC3
Hit any key to stop autoboot: 0
bootargs=root=/dev/ram0 rw console=ttyS0,115200
bootcmd=tftpboot 82000000 192.168.0.102:ls1021; bootm 82000000
bootmd_old=cp.b 60300000 82000000 700000;cp.b 60a00000 88000000 2000000; cp.b 60200000 8f000000 10000;bootm 82000000 88000000 8f000000;
It's highly strange and I don't know at all what could cause this behaviour...
I have the IoT Gateway and the eth0 does not work too.
I checked RCW config, SW2.5 = OFF.
Does the bug come from the same area as the one for the Tower board?
The eth0 is multiplexed with SATA signals, which is controlled by the mux_sata_sgmii (MUX's SEL) from the sw_mux_sel0 (SW2.5). I read this from the CPLD source program. Anyone else is playing with the CPLD?
Note: eth1 is working.
I too face same issue. Eth0 is not pinging, whereas Eth1 and Eth2 seems working.
I am using SDK 2.0. Is the problem is fixed? Could you please point me the right fix.