LAN chip dead on ARM Integrator/CP board
Hi,
I am using an ARM Integrator/CP board with u-boot 1.1.3. It's working well except that the ethernet interface never comes up. I don't see the link lights and a "dhcp" command results in:
SMC91111: PHY auto-negotiate timed out
*** ERROR: ethaddr is not set properly!!
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.
Regards,
umar
Quoted 6 lines · In message <[email protected]> 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?!?
Quoted 5 lines
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
Signature · 4 lines
Software Engineering: Embedded and Realtime Systems, Embedded Linux Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd at denx.de "We Americans, we're a simple people... but piss us off, and we'll bomb your cities." - Robin Williams, _Good Morning Vietnam_
Quoted 26 lines · Wolfgang Denk
Quoted 7 lines · In message <[email protected]> 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?!?
Quoted 7 lines
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:
Quoted 10 lines
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:4AUsing 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
Quoted 8 lines · In message <[email protected]> you wrote:
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
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Where is this MAC address coming from? You are aware that this is an address which will NOT work?
Quoted 3 lines
"ethaddr" value: 00:05:1B:00:10:4AUsing MAC Address 00:05:1B:00:10:4A
ping failed: host 192.168.168.157 is not alive
Did you see any packets on the wire?
Quoted 1 line
I have given the board a static IP address in order to bypass DHCP.
And which one was this?
Quoted 3 lines
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.
Given the fact that your hardware MAC address is illegal (has the multicast bit set) you should not be surprised. I'm not sure what your hardware does in such a situation.
I recommend to fix your MAC addresses first.
Quoted 2 lines
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:
Patches have been posted on the list; see the archives.
Best regards,
Wolfgang Denk
Signature · 5 lines
Software Engineering: Embedded and Realtime Systems, Embedded Linux Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd at denx.de There's no honorable way to kill, no gentle way to destroy. There is nothing good in war. Except its ending. -- Abraham Lincoln, "The Savage Curtain", stardate 5906.5
Quoted 8 lines · Wolfgang Denk
Quoted 5 lines · In message <[email protected]> you wrote:
1) I have tried setting up the MAC address. However that does not fix the problem. Output:
SMC91111: PHY auto-negotiate timed out
Quoted 11 lines
Quoted 4 lines
Warning: MAC addresses don't match:
HW MAC address: 01:00:01:00:00:00^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^Where is this MAC address coming from? You are aware that this is an address which will NOT work?
Code inspection of smc91111.c shows that the driver is reading the MAC address from the ROM, if it detects one.
Quoted 9 lines
Quoted 5 lines
"ethaddr" value: 00:05:1B:00:10:4AUsing MAC Address 00:05:1B:00:10:4A
ping failed: host 192.168.168.157 is not aliveDid you see any packets on the wire?
I did not snoop the line but the link lights are dead. I doubt sniffing packets would reveal much else.
Quoted 16 lines
Quoted 5 lines
I have given the board a static IP address in order to bypass DHCP.
And which one was this?
Quoted 5 lines
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.
Quoted 8 lines
Given the fact that your hardware MAC address is illegal (has the multicast bit set) you should not be surprised. I'm not sure what your hardware does in such a situation.
I recommend to fix your MAC addresses first.
The 'ethaddr' environment variable would override any other MAC address, real or bunk. If the chip is in a reset state then all bets are off as to the values being returned from the ROM. This could explain why the MAC address from the ROM is bad.
The chip looks dead.
Anyone know if there are certain FPGA settings that might need to be set on the Integrator/CP with ARM926EJS core module to wake up the LAN chip?
Quoted 9 lines
Quoted 4 lines
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:
Patches have been posted on the list; see the archives.
I applied the patch but the compiler still puked when compiling cpu/arm926ejs/start.S. It complained:
cc1: invalid option 'abi=apcs-gnu'
So I changed the cpu/arm926ejs/config.mk:
config.mk.orig 2005-12-21 15:47:45.421844207 -0800 renamed from config.mk 2005-12-21 18:07:33.773204149 -0800 +1 -1
@@ -30,5 +30,5 @@ # Supply options according to compiler version # # ========================================================================= -PLATFORM_CPPFLAGS +=$(call cc-option,-mapcs-32) +PLATFORM_CPPFLAGS +=$(call cc-option,-mapcs-32,-mabi=apcs-gnu) PLATFORM_RELFLAGS +=$(call cc-option,-mshort-load-bytes,$(call cc-option,-malignment-traps,))
This got it to compile but 1.1.4 exhibits the same LAN problem.
Regards,
umar
Quoted 21 lines
Quoted 1 line
I applied the patch but the compiler still puked when compiling
cpu/arm926ejs/start.S. It complained:cc1: invalid option 'abi=apcs-gnu'
So I changed the
cpu/arm926ejs/config.mk:config.mk.orig 2005-12-21 15:47:45.421844207 -0800 renamed from config.mk 2005-12-21 18:07:33.773204149 -0800 +0
-0@@ -30,5 +30,5 @@ # Supply options according to compiler version # #=========================================================================
config.mk.orig 2005-12-21 15:47:45.421844207 -0800 renamed from config.mk 2005-12-21 18:07:33.773204149 -0800 +1
-1-PLATFORM_CPPFLAGS +=$(call cc-option,-mapcs-32) +PLATFORM_CPPFLAGS +=$(call cc-option,-mapcs-32,-mabi=apcs-gnu)
PLATFORM_RELFLAGS+=$(call cc-option,-mshort-load-bytes,$(call cc-option,-malignment-traps,))
Quoted 5 lines
This got it to compile but 1.1.4 exhibits the same LAN problem.
Regards,
umar
Oops! That patch is backwards. It should be:
config.mk 2005-12-21 18:07:33.773204149 -0800 renamed from config.mk.orig 2005-12-21 15:47:45.421844207 -0800 +1 -1
@@ -30,5 +30,5 @@ # Supply options according to compiler version # # ========================================================================= -PLATFORM_CPPFLAGS +=$(call cc-option,-mapcs-32,-mabi=apcs-gnu) +PLATFORM_CPPFLAGS +=$(call cc-option,-mapcs-32) PLATFORM_RELFLAGS +=$(call cc-option,-mshort-load-bytes,$(call
cc-option,-malignment-traps,))
Regards,
umar