• State TI Thinks Resolved
  • Locked Locked
  • Replies 3 replies
  • Answers 2 answers
  • Subscribers 100 subscribers
  • Views 718 views
  • Users 0 members are here
Support feedback
Options
Options
Related

This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

TI814x - UBoot does not give MAC address to the kernel

Manisha Agrawal
Mastermind 22946 points

My board look to came with a MAC already program in EFUSE

Uboot
Net: Detected MACID:90:d7:eb:30:e2:16

When the kernel boot, it generate a random each time instead of taking the one from EFUSE?

eth0 Link encap:Ethernet HWaddr AE:7A:18:B2:4F:43

Even if you define ethaddr in uboot, the kernel MAC driver will not use this MAC.

What is the preferred way of passing the MAC from uboot to the kernel?

  • 0
    TI__Intellectual 2750 points

    Hi Manisha

    The issue is fixed with the patch - http://arago-project.org/git/projects/?p=linux-omap3.git;a=commit;h=dceca30b7cbf3d7ab0d626233432bfbe24b72ec7

    with regards

    Mugunthan V N

  • 0 in reply to Mugunthan V N
    TI__Mastermind 22946 points

    Mugunthan,

    This patch takes the MAC burn in e-fuse, not the MAC set in the uboot env. Customers MAC are not burn in the efuse but in the uboot config.

    Regards,

    Manisha

  • 0 in reply to Manisha Agrawal
    TI__Intellectual 2750 points

    Manisha

    The earlier method of passing ethernet address through bootrags is deprecated. The current approach relies on reading the MAC at init time from non-volatile storage - depending on the platform this information can come from internal E-fuse location,  EEPROM or NAND/SPI Flash. The value is read separately during uboot and kernel init times and there is no direct means for uboot to relay this information to kernel

    If you are working  on platform where the MAC address is not programmed through means described above, the kernel driver will resort to auto-generation of random MAC address at init time.

    with regards

    Mugunthan V N