[#3851] CFI flash on BF548-EZKIT is not detected due to query version being too new

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

[#3851] CFI flash on BF548-EZKIT is not detected due to query version being too new

Submitted By: Mike Frysinger

Open Date

2008-01-23 11:53:51     Close Date

2008-11-12 18:14:56

Priority:

Medium     Assignee:

Nobody

Status:

Closed     Fixed In Release:

N/A

Found In Release:

N/A     Release:

Category:

N/A     Board:

EZKIT Lite

Processor:

BF548     Silicon Revision:

Is this bug repeatable?:

Yes     Resolution:

Fixed

Uboot version or rev.:

    Toolchain version or rev.:

App binary format:

N/A     

Summary: CFI flash on BF548-EZKIT is not detected due to query version being too new

Details:

 

when booting the latest release, we see:

 

physmap platform flash device: 01000000 at 20000000

physmap-flash.0: Found 1 x16 devices at 0x0 in 16-bit bank

Intel/Sharp Extended Query Table at 0x010A

  Unknown Intel/Sharp Extended Query version 1.5.

gen_probe: No supported Vendor Command Set found

physmap-flash physmap-flash.0: map_probe failed                                                                                                                                   

 

the important part is about the version of the flash being 1.5 ... the mtd driver has this snippet of code in drivers/mtd/chips/cfi_cmdset_0001.c:

 

static inline struct cfi_pri_intelext *

read_pri_intelext(struct map_info *map, __u16 adr)

{

  ...

    if (extp->MajorVersion != '1' ||

        (extp->MinorVersion < '0' || extp->MinorVersion > '4')) {

        printk(KERN_ERR "  Unknown Intel/Sharp Extended Query "

               "version %c.%c.\n",  extp->MajorVersion,

               extp->MinorVersion);

        kfree(extp);

        return NULL;

    }

  ...

 

and since our version of 1.5 is newer than 1.4, the driver rejects it

 

Follow-ups

 

--- Sonic Zhang                                              2008-01-28 04:29:16

Which version of the BF548-ezkit do you use? We have already run regression

against the CFI NOR flash driver on BF548-ezkit v1.1.

 

--- Mike Frysinger                                           2008-01-28 04:50:43

true ... older boards may have older NOR flash and that's why it works

 

my BF548-EZKIT board:

BOM rev 1.6

PCB rev 1.3

Silicon rev 1.1

 

--- Mike Frysinger                                           2008-11-12 18:14:56

latest svn trunk supports version 1.5 so it works now

 

physmap platform flash device: 02000000 at 20000000

physmap-flash.0: Found 1 x16 devices at 0x0 in 16-bit bank

Intel/Sharp Extended Query Table at 0x010A

Intel/Sharp Extended Query Table at 0x010A

Intel/Sharp Extended Query Table at 0x010A

Intel/Sharp Extended Query Table at 0x010A

Intel/Sharp Extended Query Table at 0x010A

Using buffer write method

Using auto-unlock on power-up/resume

cfi_cmdset_0001: Erase suspend on write enabled

afs partition parsing not available

ar7part partition parsing not available

RedBoot partition parsing not available

Creating 3 MTD partitions on "physmap-flash.0":

0x00000000-0x00040000 : "bootloader(nor)"

0x00040000-0x00440000 : "linux kernel(nor)"

0x00440000-0x01000000 : "file system(nor)"

 

 

 

    Files

    Changes

    Commits

    Dependencies

    Duplicates

    Associations

    Tags

 

File Name     File Type     File Size     Posted By

No Files Were Found

Attachments

    Outcomes