• State TI Thinks Resolved
  • Locked Locked
  • Replies 5 replies
  • Answers 1 answer
  • Subscribers 99 subscribers
  • Views 7739 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.

About "Sending DHCP requests ...... timed out!"

liangxiao zhang
Expert 1430 points

hi,I have a strange question.my chip is DM6467.

after I burn uImage and ramdisk,the board log in linux.everything is normal.

but after I turn off the electrical source and turn on,it rest on "Sending DHCP requests ...... timed out!".

I cann't understand why.

and atfer I turn off and on electrical source ,I have to afresh burn the Image and ramdisk.this way ,it work normally again.

my uboot print as follows:

bootdelay=3
baudrate=115200
addclk=setenv bootargs ${bootargs} clkref=${clkref}
ethaddr=00:0e:99:02:b6:a3
ethact=DaVinci EMAC
bootfile=ramdisk.gz
filesize=248448
fileaddr=82000000
ipaddr=192.168.1.119
serverip=192.168.1.191
bootcmd=nand read 0x82000000 0x600000 0x300000; nboot 0x80700000 0 0x200000; boo
tm
bootargs=mem=116M console=ttyS0,115200n8 root=/dev/ram0 rw initrd=0x82000000,4M
ip=dhcp video=davincifb:vid0=720x576x16,2500K:vid1=720x576x16,2500K:osd0=720x576
x16,2025K davinci_enc_mngr.ch0_output=COMPOSITE davinci_enc_mngr.ch0_mode=ntsc
stdin=serial
stdout=serial
stderr=serial
ver=U-Boot 2009.08 (Apr 13 2010 - 10:03:49)

Environment size: 631/16380 bytes

I doubt that uboot environment variable.but I cann't find the reason.

  • 0
    TI__Expert 6735 points

    liangxiao:

    Since you have set ipaddr as the IP address of the target you should set ip=none instead of ip-dhcp.

    Also, bootargs has PAL resolution, so change

    .ch0_mode=ntsc

    to

    .ch0_mode=pal

    Regards,

    Michael T

  • 0 in reply to Michael T
    Expert 1100 points

    I had a strange problem once I added a daughter card and ended up getting stuck in this dhcp loop.  Adding eth0:off to turn off the auto protocol negotiation made it work for me.  It would then use the IP information I passed in on the bootargs:

    setenv bootargs 'console=ttyO2,115200n8 root=/dev/nfs rw nfsroot=192.168.1.5:/home/hutch/downloads/Integra/rootfs mem=166M earlyprink vram=50M ti816xfb.vram=0:16M,1:16M,2:6M ip=192.168.1.1:192.168.1.5::255.255.255.0::eth0:off noinitrd'

    The above is what I use for NFS.

    Regards,

    Brian

  • 0
    Guru 26430 points

    Usually a DHCP timeout is due the network not coming up. Your ip address looks okay, static 192.168.1.119 for u-boot and dhcp for Linux. Can you compare the u-boot environment variables between a good boot and a bad boot? Maybe some u-boot environment variable needs to be saveenv'ed.

    When you programming the kernel and filesystem, you are probably TFTPing them directly into the correct RAM locations before writing to NAND. I assume you "bootm" without power cycling. That skips the NAND read commands.

    Power cycling will lose the TFTP images in memory. The images in memory are reloaded from NAND. If the NAND was not programmed properly, you will load up a corrupt image into memory. You might want to compare the Linux boot log between a good boot and bad boot to see if there are kernel or file system error messages.

    Most NAND programming instructions have hard-coded sizes. Perhaps you should double check that TFTP'ed sizes are smaller than the nand read and write sizes.

     

  • 0
    TI__Expert 5685 points

    Hello,

    Just to get clarification on the problem: does this mean that if you use Ethernet from U-Boot (e.g., TFTP), the DHCP in kernel works and if you directly boot using RAMDISK and uImage in NAND (without using network from U-Boot), the kernel gets stuck at DHCP?

    Thanks.

       Hemant

  • 0 in reply to hutchman
    Intellectual 885 points

    I was also getting "Sending DHCP requests ...... timed out!" when using DM6467 Arago 2009.11 kernel.  I added ":eth0" to the bootargs as suggested and now the ethernet comes up properly.

    bootargs=console=ttyS0,115200n8 root=/dev/ram0 rw initrd=0x85000000,16M eth=00:0E:99:02:B5:A0 ip=192.168.2.101:192.168.2.6:192.168.2.6:255.255.255.0:DM6467:eth0::off mem=100M