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.

Problem with the u-boot ETH PHY is not getting detected

Other Parts Discussed in Thread: TVP5146

Hi all,

I am trying to boot DM368 leopard board from SDcard .I need MMC/SDcard
support at the u-boot level.

u-boot source provided by the leopard people doesnt have support for
MMC/SDcard .i am using the u-boot source from the Arago project .

when i am booting the DM368 board with the u-boot from Arago ,i have
this problem .No ETH PHY detected!!!


DM365 EVM # DM36x initialization passed!
TI UBL Version: 1.50
Booting Catalog Boot Loader
BootMode = SD/MMC
Starting SDMMC Copy...
  DONE
Jumping to entry point at 0x81080000.


U-Boot 2010.12-rc2 (May 05 2011 - 14:23:13)

Cores: ARM 432 MHz
DDR:   340 MHz
I2C:   ready
DRAM:  128 MiB
NAND:  512 MiB
MMC:   davinci: 0, davinci: 1
Bad block table found at page 131008, version 0x01
Bad block table found at page 262080, version 0x01
Bad block table found at page 130944, version 0x01
Bad block table found at page 262016, version 0x01
nand_bbt: ECC error while reading bad block table
nand_read_bbt: Bad block at 0x000001f00000
nand_read_bbt: Bad block at 0x000001f20000
nand_read_bbt: Bad block at 0x000001f40000
nand_read_bbt: Bad block at 0x000001f60000
nand_read_bbt: Bad block at 0x000001f80000
nand_read_bbt: Bad block at 0x000001fa0000
nand_read_bbt: Bad block at 0x000001fc0000
nand_read_bbt: Bad block at 0x000001fe0000
nand_read_bbt: Bad block at 0x000002000000
nand_read_bbt: Bad block at 0x000002020000
nand_read_bbt: Bad block at 0x000002040000
nand_read_bbt: Bad block at 0x000002060000
nand_read_bbt: Bad block at 0x000002080000
nand_read_bbt: Bad block at 0x0000020a0000
nand_read_bbt: Bad block at 0x0000020c0000
nand_read_bbt: Bad block at 0x0000020e0000
nand_bbt: ECC error while reading bad block table
nand_read_bbt: Bad block at 0x000011f00000
nand_read_bbt: Bad block at 0x000011f20000
nand_read_bbt: Bad block at 0x000011f40000
nand_read_bbt: Bad block at 0x000011f60000
nand_read_bbt: Bad block at 0x000011f80000
nand_read_bbt: Bad block at 0x000011fa0000
nand_read_bbt: Bad block at 0x000011fc0000
nand_read_bbt: Bad block at 0x000011fe0000
nand_read_bbt: Bad block at 0x000012000000
nand_read_bbt: Bad block at 0x000012020000
nand_read_bbt: Bad block at 0x000012040000
nand_read_bbt: Bad block at 0x000012060000
nand_read_bbt: Bad block at 0x000012080000
nand_read_bbt: Bad block at 0x0000120a0000
nand_read_bbt: Bad block at 0x0000120c0000
nand_read_bbt: Bad block at 0x0000120e0000
*** Warning - bad CRC, using default environment

Net:   Read from EEPROM @ 0x50 failed
No ETH PHY detected!!!
DaVinci-EMAC
Hit any key to stop autoboot:  0


I am not concerned about the bad blocks on nand flash but concerned
about ETH PHY is not getting detected .

when i boot the same board with the leopard u-boot source ,ETH  PHY is
getting detected .also our DM368 board doesn't have  EEPROM onboard ,i
wonder how the MAC address will be assigned .

can anyone help me in understanding where the problem is ,why the ETH
PHY is not getting detected ?

Thanks,
Siva

  • hi, Siva.

    which PHY chip are you trying with ?

    i get the same problem with KSZ8041NL/RNL...

    i cannot detect the PHY chip.. and also, i cannot read it's ID  form the MDIO interface.

     

    i doubt does 365 emac interface supports this chip.

     

    Would you guys get any more details on it ???

     

    reguards, Mike.

  • What PHY address are you using? We used 0, which worked on previous U-Boot versions, but didn't on the latest.

  • hi, Siva.

    what's your " previous U-Boot version"? we are trying with u-boot-2010.12-rc1-psp03.01.01.38,  however

    about, PHY address, it is always getting detected if successfully in the u-boot, right ?

    i had tried with address form  0 to 255 with a loop to read the PHY ID form the chip but without luck.

    by the way , would you please tell me which PHY chip are you trying with ?

    reguards, Mike.

  • Hi wen,

    i have used the latest u-boot from the arago project .

    http://arago-project.org/git/people/?p=sandeep/u-boot-davinci.git;a=summary

    we are using KS8001L ETH PHY chip.

    The main problem  with the U-boot source from arago is that ,there was not support for DM365 leopard Board.It has support for DM365EVM board.

    the leopard U-boot source was working fine for me ,but with the U-boot from arago project  ETH PHY chip is not getting detected .are u using DM365 Leopard board ?if it is so ,please check the Schematics and see which DM365 GPIO's are connected to ETH PHY chip .the GPIO's used in case of DM365EVM differ from that of DM365 Leopard Board.

    I was able to solve as they were using different GPIOs for conecting to ETH PHY chip ,this i changed as per my Leopard Board schematic connections .

    regards,

    Siva.

     

     

     

     

     

     

     

     

     

     

     

     

  • HI, Siva

    i had launched another post here , where you can see indetails what we had done with that PHY chip.

    since i had no info with DM365 leopard Board, i want to ask you about the difference between GPIOs for conecting to ETH PHY chip .

    thinks again for sharing your experience.

     

    regards, Mike.

  • Siva,

    Im having exactly the same problems can you please post your modification, I have the exact same chip and the problem presists.

     

    Best Regards,

     

    Sam

  • Hi Sam,

    are u using DM368 leopard board ?i have solved this problem on DM368 leopard board .i am posting the changes what i have done in the arago u-boot source .

    In board/davinci/dm365evm.c

    /* Configure PINMUX 3 to enable EMAC pins */
            writel((readl(PINMUX3) | 0x1affff), PINMUX3);
            writel(0x00000015, PINMUX2);// use GPIO 57 - 64

    also reset the ETH PHY chip ,GPIO23 is connected to the RESET pin of ETH PHY chip.

    the above changes will let U-boot to detect the ETH PY chip.

     

    Thanks,

    SIvaramkrishna.

     

     

     

  • hey sorry ,its GPIO60 thats connected to the ETH PHY chip.

  • Hi Siva,

     

    Thanks for your reply, I have the Leopard DM365 and not the 368, however the problem is similar. I will try these changes to see if it has any effect and let you know. I will also look at the schematics to see if something else needs changing. Can you zip and post your U-boot aswell? Im also having a problem with nand not being able to save so im guessing that also needs changing of some form. Thanks for your help

     

    Best Regards,

     

    Sam

  • Hi Siva,

     

    I just tested this and it works!!!!....... Thanks alot!!!. It might be worthwhile to give this information to leopard dm365 and dm368 boards on their forums and Im guessing other people would have the same problem once they try to update their u-boot to support mmc if nothing else.

     

    Thanks again.

     

    Best Regards,

     

    Sam

  • Hi Siva,

     

    Whoever faces this problem im attaching my modified file for the dm365 evm as Siva has mentioned this file is located in: uboot/board/davinci/dm365evm/dm365evm.c

     

    The problems is the pinouts for the NAND,ethernet controller and for the TVP5146 composite video input board. These dont work with the configuration in the dm365evm.c for the leopards. These have been modified so now they all work and should for the 368 aswell.

     

    Both the modified and unmodified files can be found at:

     

    http://www.zshare.net/download/93535562e435cb72/

    http://www.zshare.net/download/93535573b626109b/

     

    Best Regards,

     

    Sam

  • Samer Tufail said:

    Hi Siva,

     

    Whoever faces this problem im attaching my modified file for the dm365 evm as Siva has mentioned this file is located in: uboot/board/davinci/dm365evm/dm365evm.c

     

    The problems is the pinouts for the NAND,ethernet controller and for the TVP5146 composite video input board. These dont work with the configuration in the dm365evm.c for the leopards. These have been modified so now they all work and should for the 368 aswell.

     

    Both the modified and unmodified files can be found at:

     

    http://www.zshare.net/download/93535562e435cb72/

    http://www.zshare.net/download/93535573b626109b/

     

    Best Regards,

     

    Sam

    Thanks for sharing the valuable info...but i guess the zshare links are dead now...could you please update the link...:)

  • Please find the updated link for the modified file here:

    http://www.2shared.com/file/QoSxMdx5/dm365evm-Samer.html

  • When i am booting the leopard board with u-boot from RidgeRun ethernet port on the board is not getting detected. can anyone suggest its the hardware problem with the bard or i need to modify the u-boot code

  • Hi SIvaramkrishna,

          I use the DM368 Appro board,I also have to solve the problem of  "No ETH PHY detected!!!".

          I'm also trying to use your advise to change the dm365evm.c

          You said that in your board "GPIO60 is connected to the RESET pin of ETH PHY chip",but in my appro board,

    GPIO50 is connected to the RESET pin of ETH PHY chip.Can you help me to modify the changes?

    /* Configure PINMUX 3 to enable EMAC pins */
            writel((readl(PINMUX3) | 0x1affff), PINMUX3);
            writel(0x00000015, PINMUX2);// use GPIO 57 - 64

    Thanks so much!!!