• State
  • Locked Locked
  • Replies 5 replies
  • Subscribers 99 subscribers
  • Views 2270 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.

Verifying Checksum ... Bad Data CRC

Andre16038
Expert 1915 points

Hi I download the image file from here.

http://arago-project.org/files/releases/davinci-psp_03.01.01.38/images/dm365-evm

and using this boot comands,

 

setenv bootcmd 'nand read 0x82000000 0xC00000 0x300000; nboot 0x80700000 0 0x400000; bootm'
setenv bootargs 'mem=116M console=ttyS0,115200n8 root=/dev/ram0 rw initrd=0x82000000,4M ip=dhcp'



tftp 0x80700000 uImage-dm365-evm.bin
nand erase 0x400000 0x200000
nand write 0x80700000 0x400000 0x200000


tftp 0x82000000 arago-demo-image-dm365-evm.ext2.gz
nand erase 0xC00000 0x300000
nand write 0x82000000 0xC00000 0x300000

when I start the boards I get this error

 

U-Boot 1.3.4-svn31 (May 25 2010 - 20:23:33)                                    
                                                                               
I2C:   ready                                                                   
DRAM:  128 MB                                                                  
NAND:  NAND device: Manufacturer ID: 0x2c, Chip ID: 0xda (Micron NAND 256MiB 3,)
Bad block table found at page 131008, version 0x01                             
Bad block table found at page 130944, version 0x01                             
256 MiB                                                                        
In:    serial                                                                  
Out:   serial                                                                  
Err:   serial                                                                  
Ethernet PHY: GENERIC @ 0x00                                                   
Hit any key to stop autoboot:  0                                               
                                                                               
NAND read: device 0 offset 0xc00000, size 0x300000                             
 3145728 bytes read: OK                                                        
                                                                               
Loading from NAND 256MiB 3,3V 8-bit, offset 0x400000                           
   Image Name:   Arago/2.6.32.17-r38+gitr74f19831                              
   Image Type:   ARM Linux Kernel Image (uncompressed)                         
   Data Size:    2211120 Bytes =  2.1 MB                                       
   Load Address: 80008000                                                      
   Entry Point:  80008000                                                      
## Booting kernel from Legacy Image at 80700000 ...                            
   Image Name:   Arago/2.6.32.17-r38+gitr74f19831                              
   Image Type:   ARM Linux Kernel Image (uncompressed)                         
   Data Size:    2211120 Bytes =  2.1 MB                                       
   Load Address: 80008000                                                      
   Entry Point:  80008000                                                      
   Verifying Checksum ... Bad Data CRC                                         
ERROR: can't get kernel image!                                                 
Leopard 365 :>

  • 0
    Expert 1915 points

    nevermind the size of my uImage is 2.2M and I put 2.0M

  • 0 in reply to Andre16038
    TI__Genius 9510 points

    Okay - glad you were able to figure it out.

  • 0
    Prodigy 30 points

    Hi Andre,

      Now u solve that issue (Bad Data CRC)????

    because am also getting the same issue while running the uImage from u-boot...

    then..I did some modification in u-boot  board / dm355_evm / nand.c file

    Line Number : 475

    that is...

          case NAND_ECC_READSYN:
                    /*
                     * Our ECC calculation has already been terminated, so no need
                     * to do anything here.
                     */
                    val = (*(dv_reg_p) NAND4BITECC1);
                    break;
            case NAND_ECC_WRITESYN:
            default:
                    break;


    Now It's working fine...

    But..I don't know the technical reason behind it...

    If u know let me update immediately..


    ERROR: can't get kernel image! 

      means..there is no image on that particular location that u mention in the "Boot cmd" 


  • 0 in reply to JPR
    Expert 1915 points

    HI Raana I did resolved by changing the size it was

    tftp 0x80700000 uImage-dm365-evm.bin
    nand erase 0x400000 0x200000
    nand write 0x80700000 0x400000 0x200000

    and I changed to

    tftp 0x80700000 uImage-dm365-evm.bin
    nand erase 0x400000 0x230000
    nand write 0x80700000 0x400000 0x230000

    I don't know if are running the same error.

     

  • 0 in reply to Andre16038
    Prodigy 30 points

    Hi Andre,

    I want to know your boot arguments and all...

    and my booting environment is...

    setenv bootargs 'mem=116M console=ttyS0,115200n8 root=/dev/ram0 rw initrd=0x82000000,4M ip=dhcp bootm'

    setenv bootcmd 'nand read.e 0x82000000 0xC00000 0x500000;nand read.e 0x80700000 0x500000 0x200000; bootm'

    Here, I mentioned initrd as 4M but my ramdisk is 4994KB .....Is it the reason for that issue (Bad Data CRC)????????

    Let me update please...

     

    Thanks,

    JP Raana