public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Umar Qureshey <umarq@quartics.com>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] LAN chip dead on ARM Integrator/CP board
Date: Wed, 21 Dec 2005 16:21:43 -0800	[thread overview]
Message-ID: <43A9F197.9010603@quartics.com> (raw)
In-Reply-To: <20051221234605.6DFF3354040@atlas.denx.de>

Wolfgang Denk wrote:

>In message <43A9B85D.6070200@quartics.com> you wrote:
>  
>
>>link lights and a "dhcp" command results in:
>>
>>SMC91111: PHY auto-negotiate timed out
>>
>>*** ERROR: ethaddr is not set properly!!
>>    
>>
>  ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
>
>  Now isn't this is clear hint?!?
>
>  
>
>>I compiled u-boot using the integrator cp config file.  I have modified 
>>it somewhat to include some extra commands but the network portion 
>>remains the same.  Also, the docs for the board state that the board has 
>>a LAN91C111 ethernet chip.  Anyone encontered this issue?  I did not 
>>find anything in list archives.
>>    
>>
>
>Two questions:
>
>1) What does the above error message tell you, and why did you ignore it?
>
>2) Why didn't you try current code? 
>
>Best regards,
>
>Wolfgang Denk
>
>  
>
1) I have tried setting up the MAC address.  However that does not fix 
the problem.  Output:

SMC91111:  PHY auto-negotiate timed out

Warning:  MAC addresses don't match:
          HW MAC address: 01:00:01:00:00:00
          "ethaddr" value: 00:05:1B:00:10:4A
Using MAC Address 00:05:1B:00:10:4A
ping failed: host 192.168.168.157 is not alive

I have given the board a static IP address in order to bypass DHCP.
Something is funky with the PHY layer because I do not see the link 
lights so I am not surprised no traffic is traversing the wireline.  It 
looks as if the chip is still in reset.

2) I did download u-boot 1.1.4 but the compilation failed with my 
arm-linux-gcc 3.4.2 (linked w/ uclibc) compiler.  Output:

make[1]: Leaving directory 
`/home/umar/buildroot/bootloader-arm/u-boot-1.1.4/tools'
make -C examples all
make[1]: Entering directory 
`/home/umar/buildroot/bootloader-arm/u-boot-1.1.4/examples'
arm-linux-gcc -g  -Os   -fno-strict-aliasing  -fno-common -ffixed-r8 
-msoft-float  -D__KERNEL__ -DTEXT_BASE=0x01000000 
-I/home/umar/buildroot/bootloader-arm/u-boot-1.1.4/include -fno-builtin 
-ffreestanding -nostdinc -isystem 
/home/umar/buildroot/build_arm_nofpu/staging_dir/bin-ccache/../lib/gcc/arm-linux-uclibc/3.4.2/include 
-pipe  -DCONFIG_ARM -D__ARM__ -march=armv4 -mabi=apcs-gnu -Wall 
-Wstrict-prototypes -c -o hello_world.o hello_world.c
cc1: error: invalid option `abi=apcs-gnu'
make[1]: *** [hello_world.o] Error 1
make[1]: Leaving directory 
`/home/umar/buildroot/bootloader-arm/u-boot-1.1.4/examples'
make: *** [examples] Error 2

Regards,
umar

  reply	other threads:[~2005-12-22  0:21 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-12-21 20:17 [U-Boot-Users] LAN chip dead on ARM Integrator/CP board Umar Qureshey
2005-12-21 23:46 ` Wolfgang Denk
2005-12-22  0:21   ` Umar Qureshey [this message]
2005-12-22  0:33     ` Wolfgang Denk
2005-12-22  3:10       ` Umar Qureshey
2005-12-22  3:34         ` Umar Qureshey

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=43A9F197.9010603@quartics.com \
    --to=umarq@quartics.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox