my code run on the board reveal the info as following: Board: Motorola MPC8272ADS DRAM: 32 MB FLASH: 512 kB In: serial Out: serial Err: serial Net: FCC1 ETHERNET bb_miiphy_write() Hit any key to stop autoboot: 0 =>
after i enter words like "ping 192.168.0.100",show something like this PS. the line start as "chengmo" are debug infos chengmo : fec_init chengmo 0 : rtx.txbd[0].cbd_sc : 00004c00 chengmo 1 : rtx.txbd[1].cbd_sc : 00004c00 Using FCC1 ETHERNET device chengmo : fec_send chengmo_b : rtx.txbd[0].cbd_sc : 00004c00 chengmo_a : rtx.txbd[0].cbd_sc : 0000ec00 fec: tx error chengmo : fec_send fec: tx buffer not ready ping failed; host 192.168.0.100 is not alive eventually, show me that "fec: tx buffer not ready." this prompt is in fec_send() in ether_fcc.c i am not sure that at which the mistake happened, because the flow of initializing is: eth_initialize() => phy_reset() in eth_initialize(), insert the struct into the list of devices. phy_reset(), emulates MII transmit something to PHY, is it right? here i am not sure about it. after i input PING command, it will run by sequence fec_init(), fec_send() in fec_init(), configure some register about FCC, and setup ethernet buffer discriptors and allocate space for buffer used by Tx and Rx, then initialize Parameter RAM. that' all, something wrong ? where the mistakes could happen ? i really cant find it. -- View this message in context: http://www.nabble.com/LXT972-issue-on-MPC8247%3A-tx-error-tp22533735p22533735.html Sent from the Uboot - Users mailing list archive at Nabble.com. _______________________________________________ U-Boot mailing list U-Boot@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot