[#5013] 2008.10: bf526-ezbrd "nand erase" command cannot work

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

[#5013] 2008.10: bf526-ezbrd "nand erase" command cannot work

Submitted By: Yi Li

Open Date

2009-03-23 03:07:18     Close Date

2009-04-13 22:38:04

Priority:

Medium High     Assignee:

Graf Yang

Category:

N/A     Fixed In Release:

N/A

Found In Release:

snaps     Status:

Closed

Board:

N/A     Processor:

BF526

Silicon Revision:

0.0     Resolution:

Fixed

Is the bug repeatable?:

N/A     

Summary: 2008.10: bf526-ezbrd "nand erase" command cannot work

Details:

 

Toolchain is 2009R1-4.

 

U-Boot 2008.10-svn1717 (ADI-2009R1-pre) (Mar 23 2009 - 12:45:49)               

                                                                               

CPU:   ADSP bf526-0.0 (Detected Rev: 0.0) (parallel flash boot)                

Board: ADI BF526 EZ-Board board                                                

       Support: http://blackfin.uclinux.org/                                   

Clock: VCO: 400 MHz, Core: 400 MHz, System: 80 MHz                             

RAM:   64 MB                                                                   

Flash:  4 MB                                                                   

NAND:  256 MiB                                                                 

In:    serial                                                                  

Out:   serial                                                                  

Err:   serial                                                                  

Hit any key to stop autoboot:  0                                               

bfin> nand info                                                                

                                                                               

Device 0: NAND 256MiB 1,8V 8-bit, sector size 128 KiB

 

bfin> nand erase

[snip]

...

Skipping bad block at  0x0fea0000                                              

Skipping bad block at  0x0fec0000                                              

Skipping bad block at  0x0fee0000                                              

Skipping bad block at  0x0ff00000                                              

Skipping bad block at  0x0ff20000                                              

Skipping bad block at  0x0ff40000                                              

Skipping bad block at  0x0ff60000                                              

Skipping bad block at  0x0ff80000                                              

Skipping bad block at  0x0ffa0000                                              

Skipping bad block at  0x0ffc0000                                              

Skipping bad block at  0x0ffe0000

 

 

u-boot skips all the block. This is not correct.

 

Follow-ups

 

--- Mike Frysinger                                           2009-03-23 03:12:15

'nand erase' is supposed to skip all bad blocks.  that is correct.

 

--- Yi Li                                                    2009-03-27 02:54:19

When running "flash_eraseall" in kernel on the same board, there is no

bad block. Is u-boot and kernel use different method to mark bad block? If so,

this may need to be documented in wiki.

 

--- Mike Frysinger                                           2009-03-27 11:51:03

the kernel and u-boot use the same exact mtd layer.  u-boot just rips it out of

the kernel and modifies it for its own use.  so the OOB layout is exactly the

same.  the only way it'd differ is if you select the BootROM OOB layout, but

that is already documented in that you need both u-boot and the kernel to use

that layout.

 

--- Graf Yang                                                2009-04-03 07:14:25

After scrub, erase is OK. Bug can't write properly.

 

--- Graf Yang                                                2009-04-07 22:34:18

Use U-Boot 2008.10-svn1805 (ADI-2009R1-pre) (Apr  7 2009 - 15:38:05), nand

operation, erase, scrub, and write.yaffs are all successful.

 

--- Yi Li                                                    2009-04-08 00:18:07

This need to be marked as "fixed", not "out of date", isn't

it?

 

--- Yi Li                                                    2009-04-13 22:38:04

fixed and close.

 

 

 

    Files

    Changes

    Commits

    Dependencies

    Duplicates

    Associations

    Tags

 

File Name     File Type     File Size     Posted By

No Files Were Found

Attachments

    Outcomes