UART

UART

[Vanalme Filip]

(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


_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox

RE: UART

[Vanalme Filip]

> -----Original Message-----
> From: barebox-bounces@lists.infradead.org [mailto:barebox-
> bounces@lists.infradead.org] On Behalf Of Vanalme Filip
> Sent: dinsdag 1 maart 2011 13:24
> To: barebox@lists.infradead.org
> 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@lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/barebox

_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox

RE: UART

[Vanalme Filip]

> -----Original Message-----
> From: barebox-bounces@lists.infradead.org [mailto:barebox-
> bounces@lists.infradead.org] On Behalf Of Vanalme Filip
> Sent: dinsdag 1 maart 2011 13:47
> To: barebox@lists.infradead.org
> Subject: RE: UART
> 
> > -----Original Message-----
> > From: barebox-bounces@lists.infradead.org [mailto:barebox-
> > bounces@lists.infradead.org] On Behalf Of Vanalme Filip
> > Sent: dinsdag 1 maart 2011 13:24
> > To: barebox@lists.infradead.org
> > 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]  I noticed I used the wrong Subject ! Of course, it should be FEC instead of UART.... Sorry !


Meanwhile, I even noticed other problems while transferring files with tftp. Sometimes, in the middle of a transfer, file transfer stops. With a network monitoring tool, I can see that my board is still sending Acknowledgments to the server for a certain block number, but the server can't send any packet anymore to my device (Destination unreachable (Port unreachable)). The device (Barebox) stays in this condition forever (showing rotating bar) until I interrupt with ctrl-c


> >
> > Filip
> >
> >
> > _______________________________________________
> > barebox mailing list
> > barebox@lists.infradead.org
> > http://lists.infradead.org/mailman/listinfo/barebox
> 
> _______________________________________________
> barebox mailing list
> barebox@lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/barebox

_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox