P-SeriesのトピックRe: Ping is not working from u-boot

Ping is not working from u-boot

rajasekhar — Thu, 18 Jul 2013 05:30:11 GMT

Hello to all,

I'm working on P2041RDB board and I'm trying PXE boot. for that i configured the u-boot variables ipaddr, ethaddr, netmask, gatewayip, ethact .

and i ran the ping command but i'm getting error like as follows..........

=> ping 192.168.2.144

FM1@DTSEC1: No link.

FM1@DTSEC2: No link.

FM1@DTSEC3: No link.

FM1@DTSEC4: No link.

FM1@DTSEC5: No link.

ping failed; host 192.168.2.144 is not alive

..........What are the reasons to get that error message.... and this is the total console out put is as follows ...............

U-Boot 2011.12-00064-gbfb0c9a (Jun 15 2012 - 18:21:35)

CPU0: P2041E, Version: 1.1, (0x82180111)

Core: E500MC, Version: 2.2, (0x80230022)

Clock Configuration:

CPU0:1500 MHz, CPU1:1500 MHz, CPU2:1500 MHz, CPU3:1500 MHz,

CCB:750 MHz,

DDR:666.667 MHz (1333.333 MT/s data rate) (Asynchronous), LBC:93.750 MHz

FMAN1: 583.333 MHz

PME: 375 MHz

L1: D-cache 32 kB enabled

I-cache 32 kB enabled

Board: P2041RDB, CPLD version: 4.0 vBank: 0

36-bit Addressing

Reset Configuration Word (RCW):

00000000: 12600000 00000000 241c0000 00000000

00000010: 648ea0c1 c3c02000 de800000 40000000

00000020: 00000000 00000000 00000000 d0030f07

00000030: 00000000 00000000 00000000 00000000

SERDES Reference Clocks: Bank1=100Mhz Bank2=125Mhz

I2C: ready

SPI: ready

DRAM: Initializing....using SPD

Detected UDIMM UG51U6400N8SU-ACF

2 GiB left unmapped

4 GiB (DDR3, 64-bit, CL=9, ECC off)

DDR Chip-Select Interleaving Mode: CS0+CS1

Testing 0x00000000 - 0x7fffffff

Testing 0x80000000 - 0xffffffff

Remap DDR 2 GiB left unmapped

POST memory PASSED

Flash: 128 MiB

L2: 128 KB enabled

Corenet Platform Cache: 1024 KB enabled

SERDES: bank 3 disabled

SRIO1: disabled

SRIO2: disabled

MMC: FSL_SDHC: 0

EEPROM: Invalid ID (ff ff ff ff)

PCIe1: disabled

PCIe2: Root Complex, no link, regs @ 0xfe201000

PCIe2: Bus 00 - 00

PCIe3: disabled

In: serial

Out: serial

Err: serial

Net: Initializing Fman

Fman1: Uploading microcode version 106.1.4

FM1@DTSEC1, FM1@DTSEC2, FM1@DTSEC3, FM1@DTSEC4, FM1@DTSEC5

Hit any key to stop autoboot: 0

=> pri ipaddr

ipaddr=192.168.2.168

=> pri etha

ethact ethaddr

=> pri ethaddr

ethaddr=00-04-9F-02-4C-4C

=> printenv netmask

netmask=255.255.255.0

=> printenv gatewayip

gatewayip=192.168.2.123

=> printenv ethact

ethact=FM1@DTSEC1

=> ping 192.168.2.144

FM1@DTSEC1: No link.

FM1@DTSEC2: No link.

FM1@DTSEC3: No link.

FM1@DTSEC4: No link.

FM1@DTSEC5: No link.

ping failed; host 192.168.2.144 is not alive

Original Attachment has been moved to: ping_issue.log.zip

Re: Ping is not working from u-boot

lunminliang — Thu, 18 Jul 2013 07:58:09 GMT

Some simple initial tips:

1. Make sure the cable is correctly connected to the right ethernet port on the board (there are several ports)

2. Make sure the host 192.168.2.144 is normally available, you may use a third host to ping to the 192.168.2.144.

3. Check the switch settings whether they are all in default postion as the board quick start document.

Re: Ping is not working from u-boot

rajasekhar — Mon, 22 Jul 2013 05:53:56 GMT

Hilunminliang,

Thanks for you kind reply....

I've ensured the switch settings. all are in default... and the cable is also connected to the right ports(one to one)..

Even If i didn't connect any Ethernet cable. It should take some time to ping and display failed message. But it is not happening like that.

it's directly showing "No link." message with in a fraction of seconds. what would be the reason.....

Thanks,

Rajasekhar

Re: Ping is not working from u-boot

lunminliang — Wed, 24 Jul 2013 07:57:57 GMT

Please provide additional U-Boot logs:

1) of the "pri" command

2) of the "mdio list" command

3) to which exactly socket the Ethernet cabe is connected?

Please also ensure all the on board jumpers are in default position (Refer to the board quick start guide)

Re: Ping is not working from u-boot

rajasekhar — Thu, 25 Jul 2013 04:32:37 GMT

U-Boot 2011.12-00064-gbfb0c9a (Jun 15 2012 - 18:21:35)

CPU0: P2041E, Version: 1.1, (0x82180111)

Core: E500MC, Version: 2.2, (0x80230022)

Clock Configuration:

CPU0:1500 MHz, CPU1:1500 MHz, CPU2:1500 MHz, CPU3:1500 MHz,

CCB:750 MHz,

DDR:666.667 MHz (1333.333 MT/s data rate) (Asynchronous), LBC:93.750 MHz

FMAN1: 583.333 MHz

PME: 375 MHz

L1: D-cache 32 kB enabled

I-cache 32 kB enabled

Board: P2041RDB, CPLD version: 4.0 vBank: 0

36-bit Addressing

Reset Configuration Word (RCW):

00000000: 12600000 00000000 241c0000 00000000

00000010: 648ea0c1 c3c02000 de800000 40000000

00000020: 00000000 00000000 00000000 d0030f07

00000030: 00000000 00000000 00000000 00000000

SERDES Reference Clocks: Bank1=100Mhz Bank2=125Mhz

I2C: ready

SPI: ready

DRAM: Initializing....using SPD

Detected UDIMM UG51U6400N8SU-ACF

2 GiB left unmapped

4 GiB (DDR3, 64-bit, CL=9, ECC off)

DDR Chip-Select Interleaving Mode: CS0+CS1

Testing 0x00000000 - 0x7fffffff

Testing 0x80000000 - 0xffffffff

Remap DDR 2 GiB left unmapped

POST memory PASSED

Flash: 128 MiB

L2: 128 KB enabled

Corenet Platform Cache: 1024 KB enabled

SERDES: bank 3 disabled

SRIO1: disabled

SRIO2: disabled

MMC: FSL_SDHC: 0

EEPROM: Invalid ID (ff ff ff ff)

PCIe1: disabled

PCIe2: Root Complex, no link, regs @ 0xfe201000

PCIe2: Bus 00 - 00

PCIe3: disabled

In: serial

Out: serial

Err: serial

Net: Initializing Fman

Fman1: Uploading microcode version 106.1.4

FM1@DTSEC1, FM1@DTSEC2, FM1@DTSEC3, FM1@DTSEC4, FM1@DTSEC5

Hit any key to stop autoboot: 3

=> pri

baudrate=115200

bdev=sda3

bootcmd=run sataboot

bootdelay=3

bootfile=uImage-p2041rdb.bin

consoledev=ttyS0

defaultboot=setenv bootargs root=/dev/ram rw console=$consoledev,$baudrate $othbootargs;bootm e8020000 e9300000 e8800000

eth1addr=00-04-9F-02-4C-4D

eth2addr=00-04-9F-02-4C-4E

eth3addr=00-04-9F-02-4C-4F

eth4addr=00-04-9F-02-4C-50

eth5addr=00-04-9F-02-4C-51

eth6addr=00:E0:0C:00:ea:06

eth7addr=00:E0:0C:00:ea:07

eth8addr=00:E0:0C:00:ea:08

eth9addr=00:E0:0C:00:ea:09

ethact=FM1@DTSEC1

ethaddr=00-04-9F-02-4C-4C

ethprime=e1000#0

fdtaddr=c00000

fdtfile=uImage-p2041rdb.dtb

filesize=80000

fman_ucode=0xef000000

gatewayip=192.168.2.123

hvboot=setenv bootargs config-addr=0xfe8900000;bootm 0xfe8700000 - 0xfe8800000

hwconfig=fsl_ddr:ctlr_intlv=cacheline,bank_intlv=cs0_cs1;fsl_fm1_xaui_phy:xfi

ipaddr=192.168.2.158

loadaddr=1000000

netdev=eth0

netmask=255.255.255.0

nfsboot=setenv bootargs root=/dev/nfs rw nfsroot=$serverip:$rootpath ip=$ipaddr:$serverip:$gatewayip:$netmask:$hostname:$netdev:off console=$consoledev,$baudrate $othbootargs;tftp $loadaddr $bootfile;tftp $fdtaddr $fdtfile;bootm $loadaddr - $fdtaddr

ramboot=setenv bootargs root=/dev/ram rw console=$consoledev,$baudrate $othbootargs;tftp $ramdiskaddr $ramdiskfile;tftp $loadaddr $bootfile;tftp $fdtaddr $fdtfile;bootm $loadaddr $ramdiskaddr $fdtaddr

ramdiskaddr=2000000

ramdiskfile=devel-image-p2041rdb.ext2.gz.u-boot

rootpath=/opt/nfsroot

sataboot=setenv bootargs root=/dev/sda3 rw rootdelay=5 console=$consoledev,$baudrate $othbootargs;bootm e8020000 - e8800000

serverip=192.168.2.144

stderr=serial

stdin=serial

stdout=serial

tftpflash=tftpboot $loadaddr $uboot && protect off $ubootaddr +$filesize && erase $ubootaddr +$filesize && cp.b $loadaddr $ubootaddr $filesize && protect on $ubootaddr +$filesize && cmp.b $loadaddr $ubootaddr $filesize

uboot=u-boot.bin

ubootaddr=0xeff80000

usbboot=setenv bootargs root=/dev/sdb1 rw rootdelay=10 console=ttyS0,115200; bootm 0xe8020000 - e8800000

Environment size: 2043/8188 bytes

=> mdio list

FSL_MDIO0:

0 - Generic PHY <--> FM1@DTSEC5

1 - Generic PHY <--> FM1@DTSEC4

2 - Generic PHY <--> FM1@DTSEC1

3 - Generic PHY <--> FM1@DTSEC2

4 - Generic PHY <--> FM1@DTSEC3

FM_TGEC_MDIO:

=> ping 192.168.2.144

FM1@DTSEC1: No link.

FM1@DTSEC2: No link.

FM1@DTSEC3: No link.

FM1@DTSEC4: No link.

FM1@DTSEC5: No link.

ping failed; host 192.168.2.144 is not alive

Re: Re: Ping is not working from u-boot

lunminliang — Mon, 29 Jul 2013 05:28:20 GMT

The RDB team compared the log file with the quick start guide(see attached).

Uboot revision should be same, but Fman code revision and rcw are different.

Please try attached rcw and ucode.

If still not work, maybe hardware issue somewhere.

Is the board brand new?

Re: Ping is not working from u-boot

robertdavis — Mon, 29 Sep 2014 20:40:40 GMT

LunMinLiang,

I have the same issue. I have provided my U-Boot. I believe that my ucode & rcw are updated (current rev 2 board). Please help.

-Robert Davis

U-Boot 2013.01QorIQ-SDK-V1.5 (Dec 15 2013 - 18:54:15)

CPU0: T4240E, Version: 2.0, (0x82480020)

Core: E6500, Version: 2.0, (0x80400120)

Clock Configuration:

CPU0:1666.667 MHz, CPU1:1666.667 MHz, CPU2:1666.667 MHz, CPU3:1666.667 MHz,

CPU4:1666.667 MHz, CPU5:1666.667 MHz, CPU6:1666.667 MHz, CPU7:1666.667 MHz,

CPU8:1666.667 MHz, CPU9:1666.667 MHz, CPU10:1666.667 MHz, CPU11:1666.667 MHz,

CCB:733.333 MHz,

DDR:933.333 MHz (1866.667 MT/s data rate) (Asynchronous), IFC:183.333 MHz

FMAN1: 733.333 MHz

FMAN2: 733.333 MHz

QMAN: 366.667 MHz

PME: 533.333 MHz

L1: D-cache 32 kB enabled

I-cache 32 kB enabled

Reset Configuration Word (RCW):

00000000: 16070019 18101916 00000000 00000000

00000010: 04383060 30548c00 ec020000 f5000000

00000020: 00000000 ee0000ee 00000000 000307fc

00000030: 00000000 00000000 00000000 00000028

Board: T4240QDS, Sys ID: 0x1e, Sys Ver: 0x14, vBank: 0

FPGA: v6 (T4240QDS_2014_0211_1852), build 547 on Wed Feb 12 00:52:40 2014

SERDES Reference Clocks: SERDES1=125MHz SERDES2=125MHz SERDES3=100MHz SERDES4=100MHz

I2C: ready

SPI: ready

DRAM: Initializing....using SPD

Detected UDIMM

22 GiB left unmapped

DDR: 24 GiB (DDR3, 64-bit, CL=13, ECC on)

DDR Controller Interleaving Mode: 3-way 4KB

DDR Chip-Select Interleaving Mode: CS0+CS1

VID: Core voltage 1030 mV

Flash: 128 MiB

L2: 2048 KB enabled

enable l2 for cluster 1 fec60000

enable l2 for cluster 2 feca0000

Corenet Platform Cache: 1536 KB enabled

Using SERDES1 Protocol: 1 (0x1)

Using SERDES2 Protocol: 28 (0x1c)

Using SERDES3 Protocol: 6 (0x6)

Using SERDES4 Protocol: 12 (0xc)

SRIO1: enabled

SRIO2: disabled

NAND: 512 MiB

MMC: FSL_SDHC: 0

EEPROM: CRC mismatch (11919b47 != 00000000)

PCIe1: Root Complex, no link, regs @ 0xfe240000

PCIe1: Bus 00 - 00

PCIe2: disabled

PCIe3: Root Complex, no link, regs @ 0xfe260000

PCIe3: Bus 01 - 01

PCIe4: disabled

In: serial

Out: serial

Err: serial

Net: Fman1: Uploading microcode version 106.4.10

Failed to connect

Fman2: Uploading microcode version 106.4.10

FM1@DTSEC5 [PRIME], FM2@DTSEC5

Hit any key to stop autoboot: 0

=> pri ipaddr

ipaddr=192.168.0.2

=> print

ipaddr=10.11.192.53

baudrate=115200

bdev=sda3

bootargs=root=/dev/ram rw console=ttyS0,115200

bootcmd=setenv bootargs root=/dev/ram rw console=$consoledev,$baudrate $othbootargs;bootm e8020000 e9300000 e8800000

bootdelay=10

bootfile=uImage

c=ffe

consoledev=ttyS0

eth0addr=00:04:9f:03:67:4a

eth10addr=00:04:9f:03:67:54

eth11addr=00:04:9f:03:67:55

eth12addr=00:04:9f:03:67:56

eth13addr=00:04:9f:03:67:57

eth14addr=00:04:9f:03:67:58

eth15addr=00:04:9f:03:67:59

eth1addr=00:04:9f:03:67:4b

eth2addr=00:04:9f:03:67:4c

eth3addr=00:04:9f:03:67:4d

eth4addr=00:04:9f:03:67:4e

eth5addr=00:04:9f:03:67:4f

eth6addr=00:04:9f:03:67:50

eth7addr=00:04:9f:03:67:51

eth8addr=00:04:9f:03:67:52

eth9addr=00:04:9f:03:67:53

ethact=FM1@DTSEC5

ethaddr=00:04:9f:03:67:4a

ethprime=FM1@DTSEC5

fdtaddr=c00000

fdtfile=t4240qds/t4240qds.dtb

fileaddr=1000000

filesize=200000

fman_ucode=0xeff40000

gatewayip=10.11.192.1

hwconfig=fsl_ddr:ctlr_intlv=3way_4KB,bank_intlv=auto;usb1:dr_mode=host,phy_type=utmi

ipaddr=192.168.0.2

loadaddr=1000000

netdev=eth0

netmask=255.255.248.0

ramdiskaddr=2000000

ramdiskfile=t4240qds/ramdisk.uboot

rootpath=/opt/nfsroot

sataboot=setenv bootargs root=/dev/sda1 rootdelay=5 rw console=$consoledev,$baudrate $othbootargs;bootm e8020000 - e8800000

serverip=10.11.199.103

stderr=serial

stdin=serial

stdout=serial

uboot="u-boot.bin"

ubootaddr=0xeff80000

Environment size: 2123/8188 bytes

=> ping 10.11.199.103

Using FM1@DTSEC5 device

ping failed; host 10.11.199.103 is not alive

Re: Ping is not working from u-boot

rscoelho — Thu, 18 Dec 2014 16:59:13 GMT

Hi all,

Any news about this issue? I have the same problem with the P3041.

Re: Ping is not working from u-boot

sharathchandra — Tue, 31 Mar 2015 11:39:01 GMT

Hi LunMinLiang,

I was also facing similar issue with my P4080DS board while trying to update with SDK 1.7 images, after this error, I cannot connect to any interface to download my images not even from tftp.

Please find my u-boot log details:

U-Boot 2014.07QorIQ-SDK-V1.7+g659b6a2 (Feb 27 2015 - 08:30:18)

CPU0: P4080E, Version: 3.0, (0x82080030)

Core: e500mc, Version: 3.1, (0x80230031)

Clock Configuration:

CPU0:1499.985 MHz, CPU1:1499.985 MHz, CPU2:1499.985 MHz, CPU3:1499.985 MHz,

CPU4:1499.985 MHz, CPU5:1499.985 MHz, CPU6:1499.985 MHz, CPU7:1499.985 MHz,

CCB:799.992 MHz,

DDR:649.994 MHz (1299.987 MT/s data rate) (Asynchronous), LBC:99.999 MHz

FMAN1: 599.994 MHz

FMAN2: 599.994 MHz

QMAN: 399.996 MHz

PME: 399.996 MHz

L1: D-cache 32 KiB enabled

I-cache 32 KiB enabled

Reset Configuration Word (RCW):

00000000: 105a0000 00000000 1e1e181e 0000cccc

00000010: 40464000 3c3c2000 fe800000 61000000

00000020: 00000000 00000000 00000000 008b6000

00000030: 00000000 00000000 00000000 00000000

Board: P4080DS, Sys ID: 0x17, Sys Ver: 0x01, FPGA Ver: 0x0c, vBank: 0

SERDES Reference Clocks: Bank1=100MHz Bank2=125MHz Bank3=125MHz

I2C: ready

SPI: ready

DRAM: Initializing....using SPD

Detected UDIMM i-DIMM

Testing 0x00000000 - 0x7fffffff

Testing 0x80000000 - 0xffffffff

Remap DDR

4 GiB (DDR3, 64-bit, CL=9, ECC on)

DDR Controller Interleaving Mode: cache line

DDR Chip-Select Interleaving Mode: CS0+CS1

POST memory PASSED

Flash: 128 MiB

L2: 128 KiB enabled

Corenet Platform Cache: 2 MiB enabled

SRIO1: disabled

SRIO2: disabled

MMC: FSL_SDHC: 0

EEPROM: CRC mismatch (ba9a52e2 != ffffffff)

PCIe1: Root Complex, no link, regs @ 0xfe200000

PCIe1: Bus 00 - 00

PCIe2: disabled

PCIe3: Root Complex, x1 gen1, regs @ 0xfe202000

02:00.0 - 1095:3132 - Mass storage controller

PCIe3: Bus 01 - 02

In: serial

Out: serial

Err: serial

Net: Fman1: Data at eff00000 is not a firmware

No ethernet found.

Hit any key to stop autoboot: 0

=> mdio list

FSL_MDIO0:

FM_TGEC_MDIO:

P4080DS_MDIO0:

P4080DS_MDIO8:

P4080DS_MDIO4:

P4080DS_MDIO12:

P4080DS_MDIO1:

P4080DS_MDIO3:

=> pri

baudrate=115200

bdev=sda3

bootcmd=setenv bootargs root=/dev/$bdev rw console=$consoledev,$baudrate $othbootargs;tftp $loadaddr $bootfile;tftp $fdtaddr $fdtfile;bootm $loadaddr - $fdtaddr

bootdelay=10

bootfile=uImage

consoledev=ttyS0

eth1addr=00:04:9F:03:56:DE

eth2addr=00:04:9F:03:56:DF

eth3addr=00:04:9F:03:56:E0

eth4addr=00:04:9F:03:56:E1

eth5addr=00:04:9F:03:56:E2

eth6addr=00:04:9F:03:56:E3

eth7addr=00:04:9F:03:56:E4

eth8addr=00:04:9F:03:56:E5

eth9addr=00:04:9F:03:56:E6

ethact=FM1@DTSEC2

ethaddr=00:04:9F:03:56:DD

ethprime=FM1@DTSEC2

fdtaddr=c00000

fdtfile=p4080ds/p4080ds.dtb

hwconfig=fsl_ddr:ctlr_intlv=cacheline,bank_intlv=cs0_cs1;usb1:dr_mode=host,phy_type=ulpi;usb2:dr_mode=peripheral,phy_type=ulpi

ipaddr=10.10.10.148

loadaddr=1000000

netdev=eth0

netmask=255.255.255.0

ramboot=setenv bootargs root=/dev/ram rw console=$consoledev,$baudrate $othbootargs;tftp $ramdiskaddr $ramdiskfile;tftp $loadaddr $bootfile;tftp $fdtaddr $fdtfile;bootm $loadaddr $ramdiskaddr $fdtaddr

ramdiskaddr=2000000

ramdiskfile=p4080ds/ramdisk.uboot

rootpath=/opt/nfsroot

serverip=10.10.10.155

stderr=serial

stdin=serial

stdout=serial

uboot=u-boot.bin

ubootaddr=0xeff40000

Environment size: 1703/8188 bytes

Could you please suggest anything that could I try as I messed up the alternate bank also with this?

Thanks,

Sharath Chandra

Re: Ping is not working from u-boot

lunminliang — Wed, 01 Apr 2015 08:09:06 GMT

Hi Sharath Chandra,

Do you mean ping works normal before you update to SDK 1.7?

Can you please try the available pre-built image provided in SDK 1.7?

Have a great day,
Lunmin

-----------------------------------------------------------------------------------------------------------------------
Note: If this post answers your question, please click the Correct Answer button. Thank you!
-----------------------------------------------------------------------------------------------------------------------

Re: Ping is not working from u-boot

sharathchandra — Wed, 01 Apr 2015 08:14:07 GMT

Hi Lumin,

Yes, ping used to work. After I update with u-boot, it looks like the memory layout has changed and it was not able to find the microcode in its address.

After flashing the microcode by hardware debugger to that required address,it is working fine now.

Thanks for help,

Sharath Chandra

Re: Ping is not working from u-boot

lunminliang — Wed, 01 Apr 2015 08:21:05 GMT

Hi Sharath Chandra,

Welcome. So ping works fine on fm1-gb1, with the pre-built image in SDK1.7?

But you still see the message in below post?

DPFM1 - invalid FM Controller action code: 54360

Have a great day,
Lunmin

Re: Ping is not working from u-boot

sharathchandra — Wed, 01 Apr 2015 08:25:48 GMT

Hi Lumin,

Ping works fine.

Just the kernel image is different from pre-built binaries of SDK 1.7.

The difference is that I rebuilt the kernel with Timer Interrupt Frequency set to 1000Hz( the default is 250 Hz).

and I used this image for the kernel.

Does this affect anything?

Thanks,

Sharath Chandra

Re: Ping is not working from u-boot

veerendranathj — Mon, 23 Nov 2015 09:18:04 GMT

Hi,

I am facing similar issue in P2041RDB. Please let me know how to re-flash the u-code? we are using lauterbach for debugging if you have any reference script to flash u-code please share.

Thanks and Regards,

Veerendranath

Re: Ping is not working from u-boot

fededc88 — Fri, 19 Apr 2019 14:01:03 GMT

Hi! Im working embedding U-Boot on a raspberry pi 3b and i have the same issue.

But look what i have discovered. If you ping from the PC to the Raspberry it fails, but if you ping from U-Boot to the PC it will success and you will be able to reach the PC. The most surprising thing is that the pc ping start functioning while the raspberry is pinging the host.

I dont have time to investigate this, but if you only are looking for checking u-boot network connection as i am, this will be useful.