OMAP-L138 not booting up.

Hi,

The Linux Kernel Image has not been written properly to NAND flash. Please erase the NAND completely and then flash the kernel image.

Regards, Sudhakar

Hi Sudhakar,

Actually before writing the kernel image I am erasing nand completely from 0x0 to 0xFFFFFFF and i am writing the kernel image at address 0x100000.

Thanks & Regards,

Niharika

Hi,

Yesterday I made some changes in environment variable 'bootcmd' command, instead of using address 0xc0800000, now I was using address 0xc0700000

bootcmd = nboot 0xc0700000 0 0x100000; bootm

Now after writting the kernal image in nand for omap-l138 board using lauterbach when I started the board it gave me NAND read error and BAD DATA CRC error.

Booting with TI UBL
Device OPP (300MHz, 1.2V)

U-Boot 2012.04.01-svn23 (Jun 19 2012 - 16:13:42)

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
NAND read from offset 100000 failed -74
** Read error
## Booting kernel from Legacy Image at c0700000 ...
   Image Name:   Linux-2.6.37+
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    2304176 Bytes = 2.2 MiB
   Load Address: c0008000
   Entry Point:  c0008000
   Verifying Checksum ... Bad Data CRC
ERROR: can't get kernel image!
U-Boot >

But when I tried to load the same kernal image using tftp, the board booted up properly.

Please help.

Hi,

Some time what happens is that NAND may have bad blocks,

what I feel is that the address at which uImage has been written

might have bad blocks please try with some other address and try.

Thx,

--Prabhakar Lad

Thanks Prabhakar for your suggestion.

Actually Prabhakar when I am loading the image in nand using tftp and giving nandboot command that time the board is booting up properly.

Still I will try your suggestion and let u know the result.

Hi Sudhakar Rajashekhara/Niharika Chouhan,

Currently I am using serial flasher utility (sfh_AM1808.exe) to flash ubl/uboot in nand and its working fine; after that I am flashing uImage and file system from uboot command prompt (nand write command).

If I change uboot & kernel-2.6.33-rc1 ECC asper this patch, will existing serial flasher utility work ? or some changes required in serial flasher utility related to ECC.

Thanks,

Jignesh

Hi Jignesh,

Up to my knowledge serial flasher utility is provided from ti, so it should be compatible with this ECC changes. I think this patch-up should work with the currently being used serial flasher utility.

Please let me know your observation.

Thanks & Regards,

Niharika

Hi Niharika,

I am able to flash ubl & uboot using serial flasher without any modification in serial flasher code, and its works fine.

Thanks & Regards,

Jignesh