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.

boot??????

and after configure the S3 switch to 0000 111111
I turned on the board and got this messages on console window:
DM644x initialization passed!                       

     
TI UBL Version: 1.50                   
Booting Catalog Boot Loader                          
BootMode = NAND              
Starting NAND Copy...                    
Valid magicnum, 0xA1ACED66, found in block 0x00000006.                                                     
   DONE      
Jumping to entry point at 0x81080000.                                    


U-Boot 2009.03 (Jun 21 2010 - 16:30:08)

I2C:   ready
DRAM:  256 MB
NAND:  NAND device: Manufacturer ID: 0xec, Chip ID: 0x36 (Samsung NAND 64MiB 1,8
V 8-bit)
64 MiB
*** Warning - bad CRC or NAND, using default environment

In:    serial
Out:   serial
Err:   serial
ARM Clock: 297MHz
DDR Clock: 162MHz
Ethernet PHY: LXT972 @ 0x01
Hit any key to stop autoboot:  0
Wrong Image Format for bootm command
ERROR: can't get kernel image!
after that,
U-Boot > setenv bootfile "uImage-dm6446-evm.bin"

U-Boot > tftp

I got this error:
*** ERROR: `serverip' not set
then I did this:
after set server ip to 192.168.112.151
it says ipaddr is not set
after running dhcp,I got this:
BOOTP broadcast 1
WARN: emac_send_packet: No link
BOOTP broadcast 2
WARN: emac_send_packet: No link
BOOTP broadcast 3
WARN: emac_send_packet: No link
BOOTP broadcast 4
WARN: emac_send_packet: No link
BOOTP broadcast 5
WARN: emac_send_packet: No link
BOOTP broadcast 6
WARN: emac_send_packet: No link
BOOTP broadcast 7
WARN: emac_send_packet: No link
BOOTP broadcast 8
WARN: emac_send_packet: No link
BOOTP broadcast 9
WARN: emac_send_packet: No link
BOOTP broadcast 10
WARN: emac_send_packet: No link
now what must do?
  • Hi,

    Looking at the output dhcp is not working. Try setting a static ip

    to your board, ie set ipaddr=<some ip which you that is not used>

    set the serverip and the say tftp and bootm.

    Regards,

    --Prabhakar Lad

  • I did but still the same eroor

  • Hi,

    Once you are done with the setenv and saveenv. can you paste the log of 'printenv' .

    Regards,

    --Prabhakar Lad

  • the log is:

    bootargs=mem=120M console=ttyS0,115200n8 root=/dev/hda1 rw noinitrd ip=dhcp
    bootcmd=setenv setboot setenv bootargs \$(bootargs) video=dm64xxfb:output=\$(vid
    eostd);run setboot; bootm 0x2050000
    bootdelay=3
    baudrate=115200
    stdin=serial
    stdout=serial
    stderr=serial
    ethaddr=00:0E:99:02:43:97
    videostd=ntsc
    ver=U-Boot 2009.03 (Jun 21 2010 - 16:30:08)
    bootfile=uImage-dm6446-evm.bin
    ipaddr=192.168.1.1
    serverip=192.168.112.151

    Environment size: 420/16380 bytes

  • what's the meaning of "Wrong Image Format for bootm command
    ERROR: can't get kernel image!"

    I did the following steps:

    Turn off the board, make sure that NAND CS is selected on CS2 jumper.Configure the S3 Switch for UART boot mode (1 = ON = to the rigth)
    S3 = 1100 111111
    S3:1    S3:2    S3:3    S3:4    S3:5    S3:6    S3:7    S3:8    S3:9    S3:10
    ON     ON    OFF    OFF    ON    ON    ON     ON    ON    ON

    - The serial flasher "sfh_DM644x.exe" and the  UBL "ubl_DM644x_nand.bin" are in ${DVSDK}/PSP_03_01_00_37/board_utilities/serial_flash/dm644x. The U-Boot binary "u-boot-dm6446-evm.bin" is in ${DVSDK}/PSP_03_01_00_3. Copy these three files in a windows machine and issue the following command in DOS:

    > sfh_DM644x -nanderase
    > sfh_DM644x -nandflash ubl_DM644x_nand.bin u-boot-dm6446-evm.bin

    - Turn off the board and change the board cofiguration to NAND boot mode :
    - the S3 Switch is set for the NAND boot mode (1 = ON = to the rigth)
    S3 = 0000 111111
    S3:1     S3:2     S3:3     S3:4     S3:5     S3:6     S3:7     S3:8     S3:9     S3:10
    OFF     OFF     OFF     OFF     ON     ON     ON     ON     ON     ON

    - Open the console window (hyperterminal in Windows) configured with com1: 115200 8-N-1 none

    - Power cycle the EVM. You will see console messages, UBL identifying the U-Boot magic number and giving control to U-Boot

    -----------------------
    DM644x initialization passed!
    TI UBL Version: 1.50
    Booting Catalog Boot Loader
    BootMode = NAND
    Starting NAND Copy...
    Valid magicnum, 0xA1ACED66, found in block 0x00000006.
       DONE
    Jumping to entry point at 0x81080000.

    U-Boot 2009.03 (Jun 21 2010 - 16:30:08)
    -------------------------

    - From U-Boot, flash the kernel :

    U-Boot > setenv bootfile "uImage-dm6446-evm.bin"
    U-Boot > tftp
    U-Boot > nand erase 0x2060000 0x1ce800
    U-Boot > nand write 0x80700000 0x2060000 0x1ce800