MPC5200B boot failure help needed
[ Susheel Raj writes: ] > now the problem is that if i use MPC5200 Rev A then > the kernel boots without any problem and gets into the > command > > but when i am using MPC5200 Rev B it shows like this If you're using rev.B1 silicon (mask M08A), you'll need to set the as of yet undocumented TXW_MASK bit (13 in PPC bit ordering) in the Rx FIFO control register (MBAR + 0x318c). Thus, set &fec->rfifo_cntrl to 0x0f04 in mpc5xxx_fec_setup(). Rev.B2 (mask M62C) forces TXW_MASK to zero, but also masks the TXW interrupt (0x4000) in the status register resulting in no change from rev.A (L25R) silicon. If you're still having problems with Ethernet, I would suggest debugging it with a root file system on something other than NFS. E.g. ramdisk, MTD or ATA. -- David Wolfe Infotainment, Multimedia and Telematics Division Freescale Semiconductor
MPC5200, Hang in send() to a socket
[ I?igo Lopez Barranco writes: ] > Hi. I'm testing a program to send files thru a TCP socket on an MPC5200. > programs stops forever in one of the writings to the socket after > having sent a random number of packets. Strace says that it stops on a > send(), and netstat shows that the connection is stablished, and stays > this way: I see this problem too during a FTP put operation. The network remains up as a concurrently executing ping has no problem and I can restart the FTP transfer which will happily transfer an random number of packets before halting again. I also noticed a nasty memory leak associated with this -- if I rerun the FTP transfer enough times the system will run out of memory. It may be related to lost RX packets. The RX error count seen from "ifconfig" adds up very quickly on a put. FTP get doesn't provoke this bug nearly as much. I'm looking into the driver, though I am quite unfamiliar with Linux networking kernel code. -- David Wolfe Digital Audio, Radio & Telematics Freescale Semiconductor ** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
Lite5200 USB with Vbus=1.7V
[ I?igo Lopez Barranco writes: ] > The only strange thing is that in Motorola's schematics says that > pins 3 and 5 of the Micrel 2025 are Not Connected and 4 is GND, and > Micrel's 2025 datasheet says that 3 is GND and 4 and 5 NC. Then, in > the Lite5200 GND pin 3 is connected to GND through an 1k resistor, > instead of directly as I suppose they pretended in the schematic, and That is correct and an error in our Lite5200 layout. Thanks for the feedback. We are replacing R164 with a 0 Ohm resistor. Our Total5200 platform does not share this problem. -- David Wolfe Digital Audio, Radio & Telematics Freescale Semiconductor ** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
