Home > OS >  The kernel boot print Bad Data CRC is how to return a responsibility
The kernel boot print Bad Data CRC is how to return a responsibility

Time:05-07

start to print the following
 NAND write: device zero offset 0 x21400000, size 0 x4f5000 
5197824 bytes written: OK

Loading the from nand0, offset 0 x1000000
Image Name: Linux - 2.6.18 _pro500 - davinci1.0.0
Created: the 2014-10-07 6:16:37 UTC
Image Type: ARM Linux Kernel Image (uncompressed)
The Data Size: 4203040 Bytes=4 MiB
The Load Address: 80008000
Entry Point: 80008000
# # Booting the kernel from Legacy Image at 80700000...
Image Name: Linux - 2.6.18 _pro500 - davinci1.0.0
Created: the 2014-10-07 6:16:37 UTC
Image Type: ARM Linux Kernel Image (uncompressed)
The Data Size: 4203040 Bytes=4 MiB
The Load Address: 80008000
Entry Point: 80008000
Verifying Checksum 1... Bad Data CRC
ERROR: can 't get kernel image!


environment variables as follows
 LD # printenv 
Baudrate=115200
Bootargs=noinitrd rw mem=128 m root=/dev/mtdblock4 rootfstype=cramfs console=ttyS0, 115200 n8 init=/linuxrc
Bootcmd=x80700000 nboot 0 0 0 x1000000; Bootm
Bootdelay=3
Bootfile="uImage"
Ethact=DaVinci - EMAC
duringEthaddr=fc: 3 f: ab: 88:18:02
Fileaddr=80700000
The filesize=4 f5000
Ipaddr=192.168.0.12
Serverip=192.168.0.7
Stderr=serial
Stdin=serial
Stdout=serial
Ver 2010.12 rc2=U - the Boot (May 5, 2021-14:17:49)

The Environment the size: 437/262140 bytes


See online many kernel size super, but this doesn't seem to be super I didn't get the rest of the abnormal, who know what's the problem?

CodePudding user response:

I tried nand the scrub to repair the bad block, running effect, still can print CRC ERROR, confirm the nandflash is no problem
  • Related