[U-Boot-Users] What is wrong with "fec: rx error 0c10"?

Hi all,
I am struggling with porting u-boot on the custom board which is based on PQ2FADS_VR(MPC8670). Though I could ping to host from the target board, I got the following error when downloading the image from host through "tftpboot", which I had make sure that freescale evaluation board could work correctly.
According to the spec document, the error message "fec: rx error 0c10" means, BD_ENET_RX_NO, CRC check error in RxBD offset 0x0. I could not get what this message means correctly in this case and where I should look into it deeply. So it would be appricited if you tell me where I should look into deeply.
Thanks, -doyu
Details: - FCC1, 2 were connected PHY LXT971A each. - CONFIG_BITBANGMII was defined. - CFG_MDC_PIN/CFG_MDIO_PIN were configured. - u-boot is updated from CVS.
| U-Boot 1.1.3 (Apr 15 2005 - 15:00:26) | | MPC8260 Reset Status: External Soft, External Hard | | MPC8260 Clock Configuration | - Bus-to-Core Mult 5x, VCO Div 2, 60x Bus Freq 20-60 , Core Freq 100-300 | - dfbrg 1, corecnf 0x1b, busdf 7, cpmdf 1, plldf 0, pllmf 7 | - vco_out 400000000, scc_clk 100000000, brg_clk 25000000 | - cpu_clk 250000000, cpm_clk 200000000, bus_clk 50000000 | - pci_clk 100000000 | | CPU: MPC8260 (HiP7 Rev 14, Mask 1.0 1K49M) at 250 MHz | Board: Kyocera EVDO TAT | DRAM: 32 MB | Top of RAM usable for U-Boot at: 02000000 | Reserving 237k for U-Boot at: 01fc4000 | Reserving 4352k for malloc() at: 01b84000 | Reserving 76 Bytes for Board Info at: 01b83fb4 | Reserving 72 Bytes for Global Data at: 01b83f6c | Stack Pointer at: 01b83f48 | New Stack Pointer is: 01b83f48 | Now running in RAM - U-Boot at: 01fc4000 | FLASH: Manufacturer ID: 0001 | Manufacturer: AMD (Spansion) | Device ID: 22DA | flash_protect ON: from 0xFFF00000 to 0xFFF35FFF | flash_protect ON: from 0xFFF40000 to 0xFFF7FFFF | 1 MB | *** Warning - bad CRC, using default environment | | In: serial | Out: serial | Err: serial | Reset Ethernet PHY | U-Boot relocated to 01fc4000 | Net: FCC2 ETHERNET | ### main_loop entered: bootdelay=5 | | ### main_loop: bootcmd="bootm fff80000" | Hit any key to stop autoboot: 0 | => ping 192.168.1.10 | Trying FCC2 ETHERNET | Using FCC2 ETHERNET device | host 192.168.1.10 is alive | => tftpboot | Trying FCC2 ETHERNET | Using FCC2 ETHERNET device | TFTP from server 192.168.1.10; our IP address is 192.168.1.20 | Filename 'vmlinuz.uboot-freescale-pq2fads'. | Load address: 0x400000 | Loading: #fec: rx error 2c10 | fec: rx error 0c10 | #fec: rx error 0c10 | ##fec: rx error 0c10

In message 20050415155231.38d39b3b.Hiroshi_DOYU@montavista.co.jp you wrote:
According to the spec document, the error message "fec: rx error 0c10" means, BD_ENET_RX_NO, CRC check error in RxBD offset 0x0. I could not get what this message means correctly in this case and where I should
Most probably this is a hardware problem.
Best regards,
Wolfgang Denk
participants (2)
-
Hiroshi DOYU
-
Wolfgang Denk