Quantcast
Channel: Processors forum - Recent Threads
Viewing all articles
Browse latest Browse all 17527

OMAP-L137 Bad Data CRC during kernel boot

$
0
0

The products being developed using the OMAP-L137 to the following error:

Loading from NAND 512MiB 3,3V 8-bit, offset 0xc0000
Image Name: Linux-2.6.18_pro500-da830_omapl1
Image Type: ARM Linux Kernel Image (uncompressed)
Data Size: 1673452 Bytes = 1.6 MB
Load Address: c0008000
Entry Point: c0008000
## Booting kernel from Legacy Image at c0700000 ...
Image Name: Linux-2.6.18_pro500-da830_omapl1
Image Type: ARM Linux Kernel Image (uncompressed)
Data Size: 1673452 Bytes = 1.6 MB
Load Address: c0008000
Entry Point: c0008000
Verifying Checksum ... Bad Data CRC
ERROR: can't get kernel image!

This problem does not happen often, it appears once every few months.

While searching a solution, I found a post with a similar issue in TI forum.

http://e2e.ti.com/support/embedded/linux/f/354/t/73788

The content of the post,Richard Counts wrote that there is a problem with the U-BOOT.

Processor and U-Boot is different. But the problem is similar.

I would like to know that there arn no problem in the U-BOOT code of OMAPL137.

I am using the code and hardware information is as follows.


OMAPL-137 custom board with a NAND FLASH(MT29F4G08ABADAWP).

The codes used were downloaded from the site below.

http://processors.wiki.ti.com/index.php/Installing_the_Software_for_OMAP-L137

REL_LSP_02_20_00_07.tgz(UBL, U-BOOT)

mvl_5_0_0_demo_lsp_setuplinux_02_20_00_07.bin(KERNEL)


Viewing all articles
Browse latest Browse all 17527

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>