From: "Caruso, Nick" <ncaruso@irobot.com>
To: "ppcembed" <linuxppc-embedded@ozlabs.org>
Subject: mpc5200: "len bad" messages from tftp (u-boot 1.1.1)
Date: Wed, 23 Feb 2005 09:12:06 -0500 [thread overview]
Message-ID: <712A2DEC228C7448978CBD7A7AD5B090592D27@fever.wardrobe.irobot.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1429 bytes --]
Hello,
We are seeing repeated errors during downloads using the tftp client built into u-boot version 1.1.1.
The error message we see is:
"len bad 494 < 544"
I believe the messages must be generated by the following snippet of code from u-boot-1.1.1/net/net.c:
case PROT_IP:
#ifdef ET_DEBUG
puts ("Got IP\n");
#endif
if (len < IP_HDR_SIZE) {
debug ("len bad %d < %d\n", len, IP_HDR_SIZE);
return;
}
if (len < ntohs(ip->ip_len)) {
printf("len bad %d < %d\n", len, ntohs(ip->ip_len));
return;
}
The error is recoverable and occurs erratically - sometimes we see long strings of "#"'s between errors, and other times errors occur every couple of "#"'s. We always seem to end up with a good download.
We don't see this problem using the freescale Lite5200 boards, but we do see it on our custom mpc5200 boards.
Can anyone suggest where we should look to diagnose this problem? Perhaps it's hardware related, although I suppose it could be a configuration problem in the way u-boot is setting up the ethernet device - once we boot into linux we don't see many errors -- according to ifconfig, anyway.
Pinging the board from another machine also shows no errors.
thanks and best regards
Nick Caruso
[-- Attachment #2: Type: text/html, Size: 2932 bytes --]
reply other threads:[~2005-02-23 14:12 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=712A2DEC228C7448978CBD7A7AD5B090592D27@fever.wardrobe.irobot.com \
--to=ncaruso@irobot.com \
--cc=linuxppc-embedded@ozlabs.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