Hi all!
I have custom designed ARM board, based on AT91RM9200EK reference design. Hardware works fine. And I have following problem: When U-boot loads Kernel image from tftp, everything fine. When U-Boot starts kernel from flash, then Linux cannot communicate to ethernet device. I understand, that this is because MAC address was not set by U-Boot. But I could not find a command to initialise Ethernet. Please advice, how to act.
Best regards, Jevgeni
In message e8i8ho$5ch$1@sea.gmane.org you wrote:
And I have following problem: When U-boot loads Kernel image from tftp, everything fine. When U-Boot starts kernel from flash, then Linux cannot communicate to ethernet device. I understand, that this is because MAC address was not set by U-Boot. But I could not find a command to initialise Ethernet. Please advice, how to act.
Please read the FAQ: http://www.denx.de/wiki/view/DULG/EthernetDoesNotWorkInLinux
Best regards,
Wolfgang Denk
There are many ways to set the MAC address with U-boot. you can hard code the MAC address in include/configs/xxx.h where xxx.h is your board configuration file.
You can also develop command to accept the MAC address and put in EEPROM of MAC controller. It is not so difficult. Go through the drivers directory and check the file for your MAC controller.
One more way of assigning the MAC address is asign it in your boot scripts using the command ifconfig eth0 hw ether MACADDR
Best Regards Kiran Jammula.
From: "Jevgeni Zolotarjov" zhenja@zlo.ee To: u-boot-users@lists.sourceforge.net Subject: [U-Boot-Users] MAC address setting Date: Thu, 6 Jul 2006 08:53:17 +0300
Hi all!
I have custom designed ARM board, based on AT91RM9200EK reference design. Hardware works fine. And I have following problem: When U-boot loads Kernel image from tftp, everything fine. When U-Boot starts kernel from flash, then Linux cannot communicate to ethernet device. I understand, that this is because MAC address was not set by U-Boot. But I could not find a command to initialise Ethernet. Please advice, how to act.
Best regards, Jevgeni
Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&da... _______________________________________________ U-Boot-Users mailing list U-Boot-Users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/u-boot-users
_________________________________________________________________ Sexy, sultry, sensuous. - see why Bipasha Basu is all that and more. Try MSN Search http://server1.msn.co.in/Profile/bipashabasu.asp
In message BAY121-F10E8C00BC2499BA458BAC9C3770@phx.gbl you wrote:
There are many ways to set the MAC address with U-boot.
True. But the fact is, that U-Boot normally doies NOT set the MAC address at all - not unless it needs it for U-0Boot operations like network related commands.
you can hard code the MAC address in include/configs/xxx.h where xxx.h is your board configuration file.
I'm sorry, but thisis a really stupid idea. You will end up with many systems all using the same MAC address which is in violation of the standards and will cause lots of nasty trouble later.
DON'T DO THIS!
You can also develop command to accept the MAC address and put in EEPROM of MAC controller.
Of course. But please understand that this is not U-Boot's responsibility. It's a Linux driver issue.
From: "Jevgeni Zolotarjov" zhenja@zlo.ee To: u-boot-users@lists.sourceforge.net Subject: [U-Boot-Users] MAC address setting Date: Thu, 6 Jul 2006 08:53:17 +0300
And please don't top post / full quote!!
See http://www.netmeister.org/news/learn2quote.html
Best regards,
Wolfgang Denk
Hi all!
I have custom designed ARM board, based on AT91RM9200EK reference design. Hardware works fine. And I have following problem: When U-boot loads Kernel image from tftp, everything fine. When U-Boot starts kernel from flash, then Linux cannot communicate to ethernet device. I understand, that this is because MAC address was not set by U-Boot. But I could not find a command to initialise Ethernet.
I have the same problem with an other AT91RM9200 based board, but this is not an u-boot issue. The kernel driver for the emac should initialize this correctly, but this is obviously not the case. I worked around this problem by doing a ping manually before booting linux or by inserting the eth_init() function call in start_armboot().
Regards
Mirco
In message 44ACCBE1.32244.109A0E@mircofuchs.web.de you wrote:
initialize this correctly, but this is obviously not the case. I worked around this problem by doing a ping manually before booting linux or by inserting the eth_init() function call in start_armboot().
I just want to point out that this is a really bad idea. Instead, you should fixe the problem where it existis, i. e. in the Linux driver. If you want, implement a way to pass the MAC address from U-Boot to Linux, either as a boot argument or by your platform-specific way of passing such parameters [I never understood why nobody came up with an ATAG for the MAC address yet. But maybe this would just be too simple.]
Best regards,
Wolfgang Denk
Hi, as you can read here in the thread, you are sitting exactly between the chairs of Wolfgang and rmk ;) ...
http://lists.arm.linux.org.uk/pipermail/linux-arm-kernel/2004-July/thread.ht...
So you can either start a general discussion again, or put in the hack with eth_init() as suggested, or look for another bootloader ;) ...
Best regards Peter
In message 44ACDAB8.1000101@mw-itcon.de you wrote:
as you can read here in the thread, you are sitting exactly between the chairs of Wolfgang and rmk ;) ...
Only as far as the ATAG for MAC address is concerned [and actually I don't complain of propose anything - I just don't understand RMK here.]
So you can either start a general discussion again, or put in the hack with eth_init() as suggested, or look for another bootloader ;) ...
Or pass some "ethaddr=" boot argument, which is IMHO the most sensible thing to do as it is architecture-independent (guess which options are available on - say - MIPS systems?)
Best regards,
Wolfgang Denk
Hello Jevgeni,
1. EMAC-address doesn't matter for Linux. 2. One of the uncountable ways of init Ethernet before Linux bootstrap, is to call ping from the module, which implements the user command "loadm".
Regards, Andrew Zhukov
participants (6)
-
Jevgeni Zolotarjov -
Kiran Jammula -
Mirco Fuchs -
Peter Menzebach -
Wolfgang Denk -
Zhukov