From: Jerry Van Baren <gerald.vanbaren@ge.com>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] No ethernet link on Lubbock board.
Date: Wed, 09 Jul 2008 12:33:22 -0400 [thread overview]
Message-ID: <4874E852.1060008@ge.com> (raw)
In-Reply-To: <5a65fa170807090910y1fc587a2h165d68a050f31541@mail.gmail.com>
Victor wrote:
> Something more I have found out:
>
> I've looking at drivers/net/lan91c96.c:
>
> I have enabled Debug, and hardcoded my Mac address on get_rom_mac().
>
> I loaded u-boot on my board, and when I run a tftp command I get this:
>
> $ tftp
> LAN91C96:smc_close
> LAN91C96:smc_shutdown
> LAN91C96:smc_open
> LAN91C96:smc_reset
> LAN91C96:smc_enable
> Using MAC Address 00:02:B3:00:8F:3B
> *** Warning: no boot file name; using 'C0A80102.img'
> TFTP from server 192.168.1.1; our IP address is 192.168.1.2
> Filename 'C0A80102.img'.
> Load address: 0xa0008000
> Loading: LAN91C96: memory allocation, try 1 failed ...
Ahhh, that and grep ought to narrow down the error domain hugely. Bingo:
<http://git.denx.de/cgi-bin/gitweb.cgi?p=u-boot.git;a=blob;f=drivers/net/lan91c96.c;h=c23a4000a2860cfa596fd864c11da8ff4b22c4b6;hb=c956717ab25c962ef49d49064dfc73f4edcba1fb#l449>
Now you just have to figure out why the chip doesn't want to allocate
memory or perhaps you have a problem with the MEMORY_WAIT_TIME
definition? Maybe your CPU is too fast, maybe you need a delay in the
loop or need to make the loop (MEMORY_WAIT_TIME) longer?
Best regards,
gvb
next prev parent reply other threads:[~2008-07-09 16:33 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-08 17:39 [U-Boot-Users] No ethernet link on Lubbock board Victor
2008-07-08 17:42 ` Jerry Van Baren
2008-07-08 17:52 ` Victor
2008-07-09 0:52 ` Ben Warren
2008-07-09 15:40 ` Victor
2008-07-09 16:10 ` Victor
2008-07-09 16:33 ` Jerry Van Baren [this message]
2008-07-11 16:59 ` Victor
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=4874E852.1060008@ge.com \
--to=gerald.vanbaren@ge.com \
--cc=u-boot@lists.denx.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.