• State Resolved
  • Locked Locked
  • Replies 3 replies
  • Subscribers 98 subscribers
  • Views 389 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.

OMAP-L138 is not booting up after reset command.

Niharika Chouhan
Intellectual 290 points
Other Parts Discussed in Thread: OMAP-L138

I am using omap-L138. Using tftp I am loading the kernal image. After loading the image if I give bootm command that time board is booting up. But if after loading the image through tftp i give reset command it is giving me an error 'Bad Header Checksum' .

After giving reset command I got this output,

Booting with TI UBL

Device OPP (300MHz, 1.2V)

 

U-Boot 2012.04.01-svn23 (Jun 19 2012 - 15:01:37)

 

I2C:   ready

DRAM:  128 MiB

WARNING: Caches not enabled

NAND:  512 MiB

Bad block table found at page 262080, version 0x01

Bad block table found at page 262016, version 0x01

In:    serial

Out:   serial

Err:   serial

SF: Detected M25P64 with page size 64 KiB, total 8 MiB

Default using MAC address from environment

Default using MAC address from environment

Net:   DaVinci-EMAC

Hit any key to stop autoboot:  0

 

Loading from nand0, offset 0x100000

   Image Name:   Arago/2.6.37,psp03.21.00.04.sdk/

   Image Type:   ARM Linux Kernel Image (uncompressed)

   Data Size:    2315088 Bytes = 2.2 MiB

   Load Address: c0008000

   Entry Point:  c0008000

## Booting kernel from Legacy Image at c0700000 ...

Bad Header Checksum

ERROR: can't get kernel image!

U-Boot >

PLease help.Thanks in advance.

  • 0
    TI__Expert 5170 points

    Hi,

    The Linux Kernel image has not been written properly to NAND flash. Erase the complete NAND, download the image through tftp and then flash it to NAND. The size of the image which is provided as an argument to "nand write" has to be proper.

    Regards, Sudhakar

  • 0 in reply to Sudhakar Rajashekhara
    Intellectual 290 points

    Hi Sudhakar,

    Thanks for your help. Actually I am following the same steps given by you.

    U-Boot > nand erase 0x100000 0x400000

    NAND erase: device 0 offset 0x100000, size 0x400000
    Erasing at 0x4e0000 -- 100% complete.
    OK
    U-Boot > tftp 0xc0800000 uImage
    Using DaVinci-EMAC device
    TFTP from server 192.168.x.124; our IP address is 192.168.x.144
    Filename 'uImage'.
    Load address: 0xc0200000
    Loading: #################################################################
             #################################################################
             ###########################
    done
    Bytes transferred = 2304240 (2328f0 hex)
    U-Boot > nand write 0xc0700000 0x100000 0x400000

    NAND write: device 0 offset 0x100000, size 0x400000
     4194304 bytes written: OK
    U-Boot > set bootcmd 'nboot 0xc0700000 0 0x100000; bootm'
    U-Boot > saveenv
    Saving Environment to NAND...
    Erasing Nand...
    Erasing at 0x0 -- 100% complete.
    Writing to Nand... done

    U-Boot > reset

    Regards,

    Niharika.



  • 0 in reply to Niharika Chouhan
    Intellectual 290 points

    Thanks Sudhakar,

    I got the problem actually I was loading image using tftp at address 0xc0200000 but during nand write I was giving address 0xc0700000.

    Now I am giving same address and its working for me.

    Thanks & Regards,

    Niharika.