• State
  • Locked Locked
  • Replies 8 replies
  • Subscribers 101 subscribers
  • Views 947 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.

Bringing up OMAPL137 Board

S.Chandrasekar
Prodigy 50 points
Other Parts Discussed in Thread: OMAP-L137

I have started using OMAP L137 EVM. Upon connecting to a Hyper Terminal with appropriate port settings I got U-Boot prompt with following error message:

EEPROM @ 0X50 read FAILED !!!

Ethernet switch start failed

No ETH PHY detected !!!

Error: Ethernet init failed !

Hit any key to stop autoboot: 0

U-Boot >

Let me know the solution to this problem.

Chandrsekar

  • 0
    TI__Mastermind 24340 points

    Hi,

    Can you please check the dip switches of your board?

    SW5 should be all low (off).

    SW2 -> 7 (off), 2 (on), 1(off), 0 (on), 3 (off),

  • 0 in reply to Mariana
    Intellectual 330 points

    Hi,

    I am having a similar problem where I get the EEPROM Failed error message:

    U-Boot 1.3.3 (Apr 23 2009 - 17:32:00)

     

    I2C:   ready
    DRAM:  64 MB
    In:    serial
    Out:   serial
    Err:   serial
    ARM Clock : 300000000 Hz

     

    EEPROM @ 0x50 read FAILED!!!
    Ethernet switch start failed!
    More than one PHY detected.
    Hit any key to stop autoboot:  0
    U-Boot >

     

    I have checked the dip switches as recommended and they are configured correctly. I have successfully reflashed the EVMs following the procedure provided in this link: http://tiexpressdsp.com/index.php/Restoring/Flashing_OMAP-L137_Bootloaders. I have tried setting the MAC address manually but that doesn't seem to work either. Typing 'dhcp' at the U-Boot prompt doesn't return an error.

    Is there anything else I can try to resolve this error? How do I determine if there is a EEPROM HW failure?

  • 0 in reply to hdp
    TI__Guru*** 125430 points

    How are you setting the MAC address?  Are you doing it through u-boot with "setenv ethaddr"?  I see the same issue listed here:

    http://tiexpressdsp.com/index.php/DaVinci_PSP_3.02_Linux_Installation_User_Guide

    They solved it (well, worked around it) by doing setenv ethaddr manually in u-boot.

  • 0 in reply to Brad Griffis
    Intellectual 330 points

    yes the mac address is set manually through u-boot using the 'setenv' command. A 'printenv' command does show that the mac address is correctly set.

    Here is the 'printenv' printouts:

    bootargs=mem=32M console=ttyS2,115200n8 root=/dev/mtdblock/2 rw noinitrd ip=dhcp

    bootcmd=
    bootdelay=3
    baudrate=115200
    bootfile="uImage"
    ethaddr=00:0E:99:02:xx:xx
    ipaddr=192.168.1.142
    stdin=serial
    stdout=serial
    stderr=serial
    ver=U-Boot 1.3.3 (Apr 23 2009 - 17:32:00)

  • 0 in reply to hdp
    TI__Guru*** 125430 points

    hdp said:
    bootcmd=

    How come there's no bootcmd?

    hdp said:
    ethaddr=00:0E:99:02:xx:xx

    Am I assuming correctly that you have scratched the last 2 bytes only for the purpose of posting to this thread?  It doesn't actually show up that way does it?

    Can you paste your whole "session" into the window?

  • 0 in reply to Brad Griffis
    Intellectual 330 points

    Brad,

    Below is a copy of the whole session. Yes I have scratched the last 2 bytes. I have confirmed that they are what I expect.  Should there be a bootcmd? Note that we are for now loading the kernel into memory from the tftp server.

     

    U-Boot 1.3.3 (Apr 23 2009 - 17:32:00)

    I2C:   ready
    DRAM:  64 MB
    In:    serial
    Out:   serial
    Err:   serial
    ARM Clock : 300000000 Hz

    EEPROM @ 0x50 read FAILED!!!
    Ethernet switch start failed!
    More than one PHY detected.
    Hit any key to stop autoboot:  0
    U-Boot > setenv ethaddr 00:0E:99:02:xx:xx
    Can't overwrite "ethaddr"
    U-Boot > printenv
    bootargs=mem=32M console=ttyS2,115200n8 root=/dev/mtdblock/2 rw noinitrd ip=dhcp

    bootcmd=
    bootdelay=3
    baudrate=115200
    bootfile="uImage"
    ethaddr=00:0E:99:02:xx:xx
    ipaddr=192.168.1.142
    stdin=serial
    stdout=serial
    stderr=serial
    ver=U-Boot 1.3.3 (Apr 23 2009 - 17:32:00)

    Environment size: 266/16380 bytes

  • 0 in reply to hdp
    TI__Mastermind 25876 points

    Might be a "shot in the dark" but I've had problems with various DaVinci uboot's until I did a:

    setenv serverip 192.168.1.100

    saveenv

    Even a dummy ip address was OK.  And for  your reference, I am able to boot on OMAP-L137 with the following command.  Just remember that even an extra space can mess up the boot:

    setenv bootargs mem=120M console=ttyS2,115200n8 root=/dev/nfs nfsroot=192.168.1.102:/joetemp/joe/montavista/pro/devkit/arm/v5t_le/target,nolock ip=dhcp noinitrd rw;setenv autoload no;dhcp;bootcmd dhcp;setenv serverip 192.168.1.101;tftpboot;bootm

     

  • 0
    Prodigy 30 points

    Booting with TI UBL
    Device OPP (300MHz, 1.2V)

    U-Boot 2009.11 (Dec 14 2011 - 00:25:49)

    I2C:   ready
    DRAM:  64 MB
    *** Warning - bad CRC, using default environment

    In:    serial
    Out:   serial
    Err:   serial
    ARM Clock : 300000000 Hz
    Net:   No ETH PHY detected!!!

    Hit any key to stop autoboot:  0
    4096 KiB W25X32 at 0:0 is now current device
    ## Booting kernel from Legacy Image at c0700000 ...
       Image Name:   Linux-2.6.18_pro500-da830_omapl1
       Image Type:   ARM Linux Kernel Image (uncompressed)
       Data Size:    1804628 Bytes =  1.7 MB
       Load Address: c0008000
       Entry Point:  c0008000
       Verifying Checksum ... Bad Data CRC
    ERROR: can't get kernel image!

    help me,ethernet can't work,no eth phy detected.how can i do with it.

    above is tera term view