[#5003] spi flash at25df641 can't be probed by sf on bf537 stamp

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

[#5003] spi flash at25df641 can't be probed by sf on bf537 stamp

Submitted By: Mingquan Pan

Open Date

2009-03-19 03:05:10     Close Date

2010-06-04 16:49:41

Priority:

Medium     Assignee:

Mike Frysinger

Category:

N/A     Fixed In Release:

N/A

Found In Release:

2009R1     Status:

Closed

Board:

N/A     Processor:

BF537

Silicon Revision:

    Resolution:

Upstream

Is the bug repeatable?:

N/A     

Summary: spi flash at25df641 can't be probed by sf on bf537 stamp

Details:

 

spi flash at25df641 can't be probed by sf on bf537 stamp.

 

U-Boot 2008.10-svn1714 (ADI-2009R1-pre) (Mar 19 2009 - 14:20:48)

 

CPU:   ADSP bf537-0.2 (Detected Rev: 0.3) (bypass boot)

Board: ADI BF537 stamp board

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

Clock: VCO: 500 MHz, Core: 500 MHz, System: 125 MHz

RAM:   64 MB

Flash:  4 MB

In:    serial

Out:   serial

Err:   serial

Net:   Blackfin EMAC

MAC:   00:E0:22:FE:52:52

Hit any key to stop autoboot:  0

bfin> sf probe 1

SF: Got idcode 1f 48 00

SF: Unsupported manufacturer 1F

Failed to initialize SPI flash at 0:1

bfin> sf probe 2

SF: Got idcode ff ff ff

SF: Unsupported manufacturer FF

Failed to initialize SPI flash at 0:2

 

Follow-ups

 

--- Mike Frysinger                                           2009-03-19 03:11:34

probing CS2 wont work if there isnt actually a chip there ...

 

as for CS1, there is no information in the atmel driver for the flash with id

of 0x48.  the atmel_spi_flash_table[] needs to be filled out in

drivers/mtd/spi/atmel.c first.

 

--- Mike Frysinger                                           2009-03-28 06:32:06

no version of u-boot so far has supported this flash, so it isnt a regression to

hold up a release ...

 

--- Mike Frysinger                                           2010-06-04 01:19:49

i'm not sure this is something we should spend time on.  we arent atmel, we dont

make this part, so why should we write a driver for it ?  no one has asked for

it either, but even if they did, i'd be hard pressed to see why we should spend

time on it.

 

 

 

    Files

    Changes

    Commits

    Dependencies

    Duplicates

    Associations

    Tags

 

File Name     File Type     File Size     Posted By

No Files Were Found

Attachments

    Outcomes