> -----Original Message----- > From: barebox-bounces@xxxxxxxxxxxxxxxxxxx [mailto:barebox- > bounces@xxxxxxxxxxxxxxxxxxx] On Behalf Of Vanalme Filip > Sent: dinsdag 1 maart 2011 13:24 > To: barebox@xxxxxxxxxxxxxxxxxxx > Subject: UART > > (i.MX27 board) > > When I start a tftp transfer from the Barebox command prompt (or a ping), I (almost) > always first get an error message on the console output : > error frame: 0xa7b058f0 0x00000882 > After that, the tftp seems to continue as expected. File gets transferred and looks > ok. > As far as I can see (in fec_imx.c), the error indicates a FIFO overrun. Seems to > make no sense at the beginning of a transfer... > > Any idea if it's normal that this message appears at the beginning of a network > related command ? > I don't think it has any influence on the following communication. However, > sometimes I notice some delay between executing the command and the real start > of the communication. Maybe there's a kind of timeout to recover from that error ? > [Filip] It seems I don't get that "error frame" message if I execute network commands (i.e. ping or tftp) immediately one after the other. The moment there are some seconds between two commands, I have the message. As if invalid data is coming in during "idle" condition and filling the receive buffer. > > Filip > > > _______________________________________________ > barebox mailing list > barebox@xxxxxxxxxxxxxxxxxxx > http://lists.infradead.org/mailman/listinfo/barebox _______________________________________________ barebox mailing list barebox@xxxxxxxxxxxxxxxxxxx http://lists.infradead.org/mailman/listinfo/barebox
