Forums » Software Development »
NAND Flash
Added by Marcin Grzelak almost 5 years ago
Hello,
I have a board based on MityDSP-L138 with 4 Gb NAND Flash (MT29F4G08ABADAWP). And I use MityDSP-L138 u-boot (U-Boot 2009.11). But I probably have problem with ECC calculation. After some time during booting I get message:
Verifying Checksum ... Bad Data CRC ERROR: can't get kernel image!
Do you have any ideas what exactly is wrong?
Replies (6)
RE: NAND Flash - Added by Jonathan Cormier almost 5 years ago
Please attach a complete boot log. And the output of 'printenv'
RE: NAND Flash - Added by Marcin Grzelak almost 5 years ago
Boot log
OMAP-L138 initialization passed! Booting TI User Boot Loader UBL Version: 1.65 UBL Flashtype: NAND Starting NAND Copy... Valid magicnum, 0x55424CBB, found in block 0x00000006. DONE Jumping to entry point at 0xC1080000. U-Boot 2009.11-svn (cze 19 2019 - 11:54:40) I2C: ready DRAM: 128 MB NAND: 512 MiB MMC: davinci: 0 Bad block table not found for chip 0 Bad block table not found for chip 0 Bad block table written to 0x00001ffe0000, version 0x01 Bad block table written to 0x00001ffc0000, version 0x01 In: serial Out: serial Err: serial error reading I2C Configuration Block Error - unable to probe SPI flash. ARM Clock : 399360000 Hz DDR Clock : 145920000 Hz EMIFA CLock : 99840000 Hz DSP Clock : 399360000 Hz ASYNC3 Clock : 199680000 Hz Enet config : 0 MMC 0 Enable : 0 Net: No ETH PHY detected!!! Hit any key to stop autoboot: 0 Loading from nand0, offset 0x200000 Image Name: Linux-2.6.34-rc1 Image Type: ARM Linux Kernel Image (uncompressed) Data Size: 1429428 Bytes = 1.4 MB Load Address: c0008000 Entry Point: c0008000 ## Booting kernel from Legacy Image at c0700000 ... Image Name: Linux-2.6.34-rc1 Image Type: ARM Linux Kernel Image (uncompressed) Data Size: 1429428 Bytes = 1.4 MB Load Address: c0008000 Entry Point: c0008000 Verifying Checksum ... Bad Data CRC ERROR: can't get kernel image!
printenv
bootargs=mem=32M@0xc0000000 mem=64M@0xc4000000 console=ttyS0,115200n8 ubi.mtd=5,2048 root=ubi0:rootfs rootfstype=ubifs rootflags=sync bootcmd=nboot 0xc0700000 0 0x200000; bootm 0xc0700000 bootdelay=1 baudrate=115200 bootfile="uImage" flashuboot= mw.b 0xC0700000 0xFF 0x40000; loady 0xC0700000 115200; nand erase 0xc0000 0x40000; nand write 0xC0700000 0xc0000 0x40000; flashkernel= mw.b 0xC2000000 0xFF 0x400000; loady 0xC2000000 115200; nand erase 0x200000 0x200000; nand write 0xC2000000 0x200000 0x200000; flashrescue= mw.b 0xC2000000 0xFF 0x3000000; loady 0xC2000000 115200; nand erase 0x400000 0x400000; nand write 0xC2000000 0x400000 0x400000; autoload=no mtdids=nand0=nand mtdparts=mtdparts=nand:128M(rootfs),-(userfs) bootargsbase=mem=96M console=ttyS1,115200n8 flashargs=setenv bootargs ${bootargsbase} ${mtdparts} root=/dev/mtdblock0 rw,noatime rootfstype=jffs2 rescue=set bootargs initrd=0xc4000000,4174336 console=ttyS0,115200n8; nand read 0xc4000000 0x400000 0x400000; nboot 0xc0700000 0 0x200000; bootm 0xc0700000 stdin=serial stdout=serial stderr=serial ver=U-Boot 2009.11-svn (cze 19 2019 - 11:54:40) Environment size: 1116/131068 bytes
RE: NAND Flash - Added by Jonathan Cormier almost 5 years ago
Could you provide all the information on the barcode located on the module? Serial number, model number, etc.
It looks like you have a custom version of the UBL and u-boot.
Some oddities are that your clocks are non standard. U-boot is complaining about missing the NOR. And we don't recommend booting u-boot and kernel from the nand. They should be stored in the NOR.
See our architecture page.
https://support.criticallink.com/redmine/projects/arm9-platforms/wiki/MityDSP-L138_Architecture#Non-Volatile-Storage
UBL Flashtype: NAND
Starting NAND Copy...
I'm also confused how you managed to load the UBL from nand. This is not a boot mode we support.
We also don't recommend using the 2.6 kernel for new designs.
RE: NAND Flash - Added by Marcin Grzelak almost 5 years ago
This is not SOM. But our module, similar to the MityDSP-L138 only with one memory (NAND) and we use the U-Boot 2009.11.
I am looking for information about what may be the cause of wrong ECC calculation. Can I path this u-boot or use a different version?
Thank you for your advice.
RE: NAND Flash - Added by Bob Duke almost 5 years ago
Marcin,
If you are using a Critical Link product in your design we are happy to help in this forum. From your comments, it looks like you are not using a Critical Link product. Our U-Boot is customized for our specific SOM. I would not recommend it for a different design.
TI's Processor SDK would be a better starting point <http://www.ti.com/tool/PROCESSOR-SDK-OMAPL138> .
If you have questions about a custom design based on the OMAP-L138, you should direct your questions to TI's e2e forum <https://e2e.ti.com/> .
Thanks,
-Bob
RE: NAND Flash - Added by Marcin Grzelak almost 5 years ago
OK, I will try with TI's Processor SDK.
Thank you for your time.
Best regards