[#6009] Can't bootm uClinux image which writed to nand flash from RAM on BF526ezbrd.

Document created by Aaronwu Employee on Sep 25, 2013
Version 1Show Document
  • View in full screen mode

[#6009] Can't bootm uClinux image which writed to nand flash from RAM on BF526ezbrd.

Submitted By: Hank Lee

Open Date

2010-04-16 05:56:38     Close Date

2010-04-16 06:17:38

Priority:

High     Assignee:

Nobody

Category:

N/A     Fixed In Release:

N/A

Found In Release:

2009R1.1     Status:

Closed

Board:

Ezbrd     Processor:

BF526

Silicon Revision:

    Resolution:

Duplicated

Is the bug repeatable?:

yes     

Summary: Can't bootm uClinux image which writed to nand flash from RAM on BF526ezbrd.

Details:

 

Hi,

 

I want to boot uClinux from Nand Flash on BF526ezbrd. And I refer http://docs.blackfin.uclinux.org/doku.php?id=bootloaders:u-boot:nand-flash to write uImage to nand flash.

 

If I used u-boot-bf527-ezkit-nand-2009R1.1-rc1.ldr on snaps to boot into U-boot on BF527ezkit.  I can write uImage and boot into uClinux normally.

 

But now I change board to bf526ezbrd .  I download u-boot-trunk-svn.src.tar.bz2 sourcecode and build a U-boot.ldr for BF526 with u-boot-2010.03 version. When I boot into U-boot , I can write uImage to nand flash . But if I want to boot into uClinux , it will show this error message as below.

 

TFTP from server 172.18.121.119; our IP address is 172.18.121.97

Filename 'uImage'.

Load address: 0x1000000

Loading: #################################################################

         #################################################################

         #################################################################

         #################################################################

         ############################################################

done

Bytes transferred = 4693330 (479d52 hex)

 

bfin> nand scrub

 

NAND scrub: device 0 whole chip

Warning: scrub option will erase all factory set bad blocks!

         There is no reliable way to recover them.

         Use this command only for testing purposes if you

         are sure of what you are doing!

 

Really scrub this NAND flash? <y/N>

Erasing at 0xffe0000 -- 100% complete.

OK

bfin> nand erase clean

 

NAND erase: device 0 whole chip

Erasing at 0xffe0000 -- 100% complete. Cleanmarker written at 0xffe0000.

OK

bfin> nand write.jffs2 0x1000000 0x0 0x480000

 

NAND write: device 0 offset 0x0, size 0x480000

4718592 bytes written: OK

bfin> nboot 0x2000000 0x0

 

Loading from NAND 256MiB 1,8V 8-bit, offset 0x0

   Image Name:   Linux-2.6.28.10-ADI-2009R1.1

   Created:      2010-04-09   6:17:06 UTC

   Image Type:   Blackfin Linux Kernel Image (gzip compressed)

   Data Size:    4693266 Bytes =  4.5 MB

   Load Address: 00001000

   Entry Point:  001d3940

bfin> bootm 0x2000000

## Booting kernel from Legacy Image at 02000000 ...

   Image Name:   Linux-2.6.28.10-ADI-2009R1.1

   Created:      2010-04-09   6:17:06 UTC

   Image Type:   Blackfin Linux Kernel Image (gzip compressed)

   Data Size:    4693266 Bytes =  4.5 MB

   Load Address: 00001000

   Entry Point:  001d3940

   Verifying Checksum ... Bad Data CRC

ERROR: can't get kernel image!

bfin>

 

If I use 'cmp 0x1000000 0x2000000 0x480000' . Only OOB is different.

 

Hank

 

Follow-ups

 

--- Mike Frysinger                                           2010-04-16 06:15:58

dupe of [#6008]

 

 

 

    Files

    Changes

    Commits

    Dependencies

    Duplicates

    Associations

    Tags

 

File Name     File Type     File Size     Posted By

No Files Were Found

Attachments

    Outcomes