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.

omapl137 No ETH PHY detected!!!

Other Parts Discussed in Thread: OMAP-L137

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,is that phy chip damage?how can i do with it.

above is tera term view

  • Very anxious, hoping to provide help. a big help before any help

  • Xining,

    From your email it is not clear if you use the OMAP-L137 EVM or a custom board.

    Could be an issue with HW or SW (for example the device is not initialized correctly to talk to the PHY). In any case you will need to do some debugging.

    - On way to narrow down the issue would be to use the Booard support lib provided by spectrum digital. There is an ethernet test example (none OS based) that requires CCS and a JTAG emulator to run:
    http://support.spectrumdigital.com/boards/evmomapl137/revg/
    With this you might be able to identify if the PHY is functionnal and if the EMAC to PHY inerface can talk together.

    - For a Linux system at boot time first the UBL is loaded. It does the HW init and load u-boot in DDR. Then u-boot starts. I am not sure for OMAP-L13 but for the davinci devices (like DM644x) the U-boot fct that print this message (No ETH PHY detected!!!) is davinci_eth_hw_init(). This fct is called after the u-boot board_init() is called.


    Hope it helps.

    Anthony