All of lore.kernel.org
 help / color / mirror / Atom feed
From: Hinko Kocevar <hinko.kocevar@iskramedical.si>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] trizeps2 SMC lan91c96
Date: Wed, 09 Mar 2005 18:01:52 +0100	[thread overview]
Message-ID: <422F2C00.8040408@iskramedical.si> (raw)

Hi all,
I've successfully ported u-boot to trizeps2 cpu module from K&K that 
runs on pxa255 cpu, 32Mb FLASH and 64Mb SDRAM. Right no I get the 
command prompt.

Next I enabled CONFIG_DRIVER_LAN91C96 and set 'CONFIG_LAN91C96_BASE 
0x0C000300' - taken from linux kernel. After issuing tftp command I get 
following output:

U-Boot 1.1.3 (Mar  9 2005 - 16:32:01)

U-Boot code: A3080000 -> A30A9B40  BSS: -> A30AE1C4
RAM Configuration:
Bank #0: a0000000 64 MB
Flash: 32 MB
In:    serial
Out:   serial
Err:   serial
Hit any key to stop autoboot:  0
$ tftp
LAN91C96:smc_close
LAN91C96:smc_shutdown
LAN91C96:smc_open
LAN91C96:smc_reset
LAN91C96:smc_enable

Warning: MAC addresses don't match:
         HW MAC address:  00:18:00:10:14:18
         "ethaddr" value: 00:50:C2:0E:C8:D9
Using MAC Address 00:50:C2:0E:C8:D9
TFTP from server 192.168.0.77; our IP address is 192.168.0.98
Filename 'trizeps2_kernel.img'.
Load address: 0xa3000000
Loading: LAN91C96:smc_hardware_send_packet
LAN91C96: memory allocation, try 1 failed ...
LAN91C96: memory allocation, try 2 failed ...
LAN91C96: memory allocation, try 3 failed ...
LAN91C96: memory allocation, try 4 failed ...
LAN91C96: memory allocation, try 5 failed ...
LAN91C96:smc_rcv
RCV: STATUS    0 LENGTH    0
  Reading 32766 words and 0 byte(s)

Now, in linux kernel I had to set bit LAN91C96_CR_INT_SEL1 in 
LAN91C96_CONFIG to select correct int, but in u-boot we do not use 
interrupts last time I checked and I have them disabled in my config 
also, so this should not be mandatory here.
 From the bdi debug session I managed to pinpoint the location where it 
all hangs - tftp.c, TftpSend():

             *((ushort *)pkt)++ = htons(TFTP_RRQ);

Has anyone any experience with lan91c96 under u-boot? Would I be better 
off using smc9111 driver instead?

Any comments are welcome,

regards,
hk

-- 
hinko <dot> kocevar <at> iskramedical <dot> si
Hinko Kocevar, embedded systems developer
Iskra Medical d.o.o., Stegne 23, 1k LJ, SLO-EU

	"A? r?n"	|	[Analects XII:22]

             reply	other threads:[~2005-03-09 17:01 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-03-09 17:01 Hinko Kocevar [this message]
2005-03-09 19:28 ` [U-Boot-Users] trizeps2 SMC lan91c96 Matej Kupljen
2005-03-09 20:07   ` Hinko Kocevar

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=422F2C00.8040408@iskramedical.si \
    --to=hinko.kocevar@iskramedical.si \
    --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.