T1040RDB: ping from u-boot fails with Tx Error

cancel
Showing results for 
Search instead for 
Did you mean: 

T1040RDB: ping from u-boot fails with Tx Error

340 Views
sandeepk1980
Contributor I

I have fused the u-boot.bin using code warrior and USB TAP onto the board.Now i am getting this error when i try to ping from u-boot

ping 192.168.119.1                                                                         
 brmmemac_set_interface_mode, if_mode = 9002                                                  
 brmmemac_set_interface_mode, if_status = 2000                                                
Using FM1@DTSEC3 device                                                                       
FM1@DTSEC3: Tx buffer not ready                                                               
FM1@DTSEC3: Tx buffer not ready                                                               
ping failed; host 192.168.119.1 is not alive    

Labels (1)
0 Kudos
6 Replies

175 Views
ufedor
NXP TechSupport
NXP TechSupport

Please provide complete U-Boot booting log as textual attachment.

0 Kudos

175 Views
sandeepk1980
Contributor I

I am providing boot log and output of printenv command

Welcome to minicom 2.7

OPTIONS: I18n
Compiled on Apr 22 2017, 09:14:19.
Port /dev/ttyUSB2, 08:15:10

Press CTRL-A Z for help on special keys

2 GiB (DDR3, 64-bit, CL=11, ECC off)
Flash: 256 MiB
L2: 256 KiB enabled
Corenet Platform Cache: 256 KiB enabled
Using SERDES1 Protocol: 105 (0x69)

ifc ccr value:b008000

writing IFC_CCR

ifc ccr value:b008000:
PHY_INTERFACE_MODE_RGMII
PHY_INTERFACE_MODE_SGMII
PHY_INTERFACE_MODE_SGMII
PHY_INTERFACE_MODE_RGMII
NAND: 1024 MiB
MMC: FSL_SDHC: 0
Not a microcode
PCIe1: Root Complex, no link, regs @ 0xfe240000
PCIe1: Bus 00 - 00
PCIe2: Root Complex, no link, regs @ 0xfe250000
PCIe2: Bus 01 - 01
PCIe3: Root Complex, no link, regs @ 0xfe260000
PCIe3: Bus 02 - 02
In: serial
Out: serial
Err: serial
Net: Initializing Fman
Configuring phy addresses.....gcr
RGMII--DTSEC2,phy_addr=3
SGMII--DTSEC3,phy_addr=0
SGMII--DTSEC4,phy_addr=0
RGMII--DTSEC5,phy_addr=2
Fman1: Uploading microcode version 0.0.1
brmmemac_set_interface_mode, if_mode = 9002
brmmemac_set_interface_mode, if_status = 2000
Phy not found
SGMII-PHYLESS-MAC : phydev->addr=0
FM1@DTSEC1 connected to Generic PHY
FM1@DTSEC2 connected to Micrel ksz9031
MIcrel skew settings address-3
brmmemac_set_interface_mode, if_mode = 9002
brmmemac_set_interface_mode, if_status = 2000
SGMII-PHYLESS-MAC : phydev->addr=0
FSL_MDIO0:0 is connected to FM1@DTSEC1. Reconnecting to FM1@DTSEC3
FM1@DTSEC3 connected to Generic PHY
brmmemac_set_interface_mode, if_mode = 9002
brmmemac_set_interface_mode, if_status = 2000
SGMII-PHYLESS-MAC : phydev->addr=0
FSL_MDIO0:0 is connected to FM1@DTSEC3. Reconnecting to FM1@DTSEC4
FM1@DTSEC4 connected to Generic PHY
FM1@DTSEC5 connected to Micrel ksz9031
MIcrel skew settings address-2
FM1@DTSEC1, FM1@DTSEC2, FM1@DTSEC3, FM1@DTSEC4 [PRIME], FM1@DTSEC5
Hit any key to stop autoboot: 0
=>

=> printenv
FUSE_DTB=tftp $fdtaddr $dtbfile && protect off $dtb_saddr $dtb_eaddr && erase $dtb_saddr $dtb_eaddr && cp.b $fdtaddr $dtb_saddr $dtb_size && protect on $dtr
FUSE_KER=tftp $loadaddr $uImagefile && protect off $uImage_saddr $uImage_eaddr && erase $uImage_saddr $uImage_eaddr && cp.b $loadaddr $uImage_saddr $uImager
FUSE_LINUX= run FUSE_KER; run FUSE_RFS; run FUSE_DTB;
FUSE_RFS=tftp $ramdiskaddr $rfsfile && protect off $rfs_saddr $rfs_eaddr && erase $rfs_saddr $rfs_eaddr && cp.b $ramdiskaddr $rfs_saddr $rfs_size && protecr
FUSE_UBOOT=tftpboot $loadaddr $uboot && protect off $ubootaddr +$filesize && erase $ubootaddr +$filesize && cp.b $loadaddr $ubootaddr $filesize && protect oe
baudrate=115200
bdev=sda
bootcmd=bootm e8020000 e9300000 e8800000
bootdelay=10
bootfile=uImage
consoledev=ttyS0
dtb_eaddr=e88fffff
dtb_saddr=e8800000
dtb_size=a000
dtbfile=guest/gcr/GCR.dtb.VER2
eth1addr=00:04:9F:03:40:47
eth2addr=00:04:9F:03:40:48
eth3addr=00:04:9F:03:40:49
eth4addr=00:04:9F:03:40:4a
ethact=FM1@DTSEC4
ethaddr=00:04:9F:03:40:46
ethprime=FM1@DTSEC4
fdtaddr=6000000
fman_ucode=eff00000
gatewayip=192.168.119.1
hwconfig=fsl_ddr:bank_intlv=null;usb1:dr_mode=host,phy_type=utmi;usb2:dr_mode=host,phy_type=utmi
ipaddr=192.168.119.241
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,$baur
ramboot=setenv bootargs root=/dev/ram rw console=$consoledev,$baudrate $othbootargs;tftp $ramdiskaddr $ramdiskfile;tftp $loadaddr $bootfile;tftp $fdtaddr $fr
ramdiskaddr=2000000
ramdiskfile="t104xrdb/ramdisk.uboot"
rfs_eaddr=ebefffff
rfs_saddr=e9300000
rfs_size=1f00000
rfsfile=guest/gcr/GCR.rfs.VER2
rootpath=/opt/nfsroot
serverip=192.168.119.56
setenv bootargs root=/dev/ram rw console=$consoledev,$baudrate $othbootargs
uImage_eaddr=e86fffff
uImage_saddr=e8020000
uImage_size=600000
uImagefile=guest/gcr/GCR.uImage.VER2
uboot="u-boot-gcr.bin"
ubootaddr=0xeff40000

Environment size: 2390/8188 bytes
=>

0 Kudos

175 Views
ufedor
NXP TechSupport
NXP TechSupport

Which FMan microcode revision is used?

0 Kudos

175 Views
sandeepk1980
Contributor I

i have used this file

fsl_fman_ucode_t1040_r1.1_107_4_2.bin

0 Kudos

175 Views
sandeepk1980
Contributor I

I have also tried this file

fsl_fman_ucode_t1040_r1.1_108_5_9.bin

Are these correct files? i got these files from github provided by NXP itself

0 Kudos

175 Views
ufedor
NXP TechSupport
NXP TechSupport

Why in the provided log it is printed:

Fman1: Uploading microcode version 0.0.1

?

0 Kudos