From: Vanalme Filip <F.Vanalme@TELEVIC.com>
To: "barebox@lists.infradead.org" <barebox@lists.infradead.org>
Subject: UART
Date: Tue, 1 Mar 2011 13:24:05 +0100 [thread overview]
Message-ID: <6EE7D1502C48E44E92DCADF9DD3E0DB9017FF3B00E60@SRV-VS06.TELEVIC.COM> (raw)
(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
next reply other threads:[~2011-03-01 12:24 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-01 12:24 Vanalme Filip [this message]
2011-03-01 12:47 ` UART Vanalme Filip
2011-03-01 13:09 ` UART Vanalme Filip
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=6EE7D1502C48E44E92DCADF9DD3E0DB9017FF3B00E60@SRV-VS06.TELEVIC.COM \
--to=f.vanalme@televic.com \
--cc=barebox@lists.infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox