FAQ: [#6271] "nand unlock" is an unsupported command in u-boot update in nand flash(2010)

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

[#6271] "nand unlock" is an unsupported command in u-boot update in nand flash

Submitted By: Vivi Li

Open Date

2010-09-21 06:51:36     Close Date

2010-09-26 03:18:23

Priority:

Medium     Assignee:

Mike Frysinger

Status:

Closed     Fixed In Release:

N/A

Found In Release:

2010R1     Release:

Category:

N/A     Board:

N/A

Processor:

BF548     Silicon Revision:

Is this bug repeatable?:

Yes     Resolution:

Fixed

Uboot version or rev.:

    Toolchain version or rev.:

gcc4.3_2010R1-RC2

App binary format:

N/A     

Summary: "nand unlock" is an unsupported command in u-boot update in nand flash

Details:

 

"nand unlock" is an unsupported command in update in bf548-ezkit nand flash.

 

Bellow is the log:

--

U-Boot 2010.06-svn2400 (ADI-2010R1-pre) (Sep 21 2010 - 06:05:51)

 

CPU:   ADSP bf548-0.0 (Detected Rev: 0.2) (nand flash boot)

Board: ADI BF548 EZ-Kit board

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

Clock: VCO: 525 MHz, Core: 525 MHz, System: 131.250 MHz

RAM:   64 MiB

Flash: 16 MiB

NAND:  256 MiB

MMC:  Blackfin SDH: 0

*** Warning - bad CRC or NAND, using default environment

 

In:    serial

Out:   serial

Err:   serial

KGDB:  [on serial] ready

Net:   smc911x-0

Hit any key to stop autoboot:  0

bfin> printenv update

update=tftp $(loadaddr) $(ubootfile);nand unlock 0 0x40000;nand erase 0 0x40000;nand write $(loadaddr) 0 0x40000

bfin> nand unlock 0 0x40000

nand - NAND sub-system

 

Usage:

nand info - show available NAND devices

nand device [dev] - show or set current device

nand read - addr off|partition size

nand write - addr off|partition size

    read/write 'size' bytes starting at offset 'off'

    to/from memory address 'addr', skipping bad blocks.

nand erase [clean] [off size] - erase 'size' bytes from

    offset 'off' (entire device if not specified)

nand bad - show bad blocks

nand dump[.oob] off - dump page

nand scrub - really clean NAND erasing bad blocks (UNSAFE)

nand markbad off [...] - mark bad block(s) at offset (UNSAFE)

nand biterr off - make a bit error at offset (UNSAFE)

bfin>

--

 

In u-boot source:

--

test@uboot36-518f:~/work/cruise/checkouts/u-boot> grep -nr "nand unlock" include/configs/|grep -v svn

include/configs/bfin_adi_common.h:178:          "nand unlock 0 0x40000;" \

include/configs/devkit8000.h:219:       "eraseenv=nand unlock 0x260000 0x20000; nand erase 0x260000 0x20000\0" \

test@uboot36-518f:~/work/cruise/checkouts/u-boot>

--

 

Follow-ups

 

--- Mike Frysinger                                           2010-09-21 19:34:15

ive enabled the CONFIG_CMD_NAND_LOCK_UNLOCK option in trunk

 

--- Vivi Li                                                  2010-09-26 03:18:23

OK. Close it.

 

 

 

    Files

    Changes

    Commits

    Dependencies

    Duplicates

    Associations

    Tags

 

File Name     File Type     File Size     Posted By

No Files Were Found

Attachments

    Outcomes