[U-Boot-Users] AM29LV160DB flash + cfi-driver

[Andre Puschmann <andre.puschmann@stud.tu-ilmenau.de>]

Hey Folks,
we got a custom PPC-based board with a 2MB AM29LV160DB flash chip. I am
trying to use U-Boots CFI driver but it seems that there are still some
problems with this configuration, reading e.g. the wrong vendor id.
This is my output if I boot the board:


    0.01> U-Boot 1.1.6-ge4bbd8da-dirty (Dec  8 2006 - 12:25:48)
    0.01>
    0.01> CPU:   MPC5200 v1.2, Core v1.1 at 396 MHz
    0.03>        Bus 132 MHz, IPB 132 MHz, PCI 33 MHz
    0.03> Board: MPC5200 ECU
    0.03> I2C:   85 kHz, ready
    0.03> DRAM:   8 MB
    0.03> Top of RAM usable for U-Boot at: 00800000
    0.03> Reserving 164k for U-Boot at: 007d6000
    0.04> Reserving 129k for malloc() at: 007b5c00
    0.04> Reserving 68 Bytes for Board Info at: 007b5bbc
    0.04> Reserving 56 Bytes for Global Data at: 007b5b84
    0.04> Stack Pointer at: 007b5b68
    0.06> New Stack Pointer is: 007b5b68
    0.10> Now running in RAM - U-Boot at: 007d6000
    0.10> FLASH: flash detect cfi
    0.12> fwc addr ffe00000 cmd 0 0 8bit x 8 bit
    0.12> fwc addr ffe00055 cmd 98 98 8bit x 8 bit
    0.12> is= cmd 51(Q) addr ffe00010 is= ff 51
    0.12> fwc addr ffe00000 cmd 0 0000 16bit x 8 bit
    0.14> fwc addr ffe000aa cmd 98 9898 16bit x 8 bit
    0.14> is= cmd 51(Q) addr ffe00020 is= ffff 5151
    0.14> fwc addr ffe00000 cmd 0 0000 16bit x 16 bit
    0.14> fwc addr ffe000aa cmd 98 0098 16bit x 16 bit
    0.15> is= cmd 51(Q) addr ffe00020 is= ffff 0051
    0.15> fwc addr ffe00000 cmd 0 00000000 32bit x 8 bit
    0.15> fwc addr ffe00154 cmd 98 98989898 32bit x 8 bit
    0.15> is= cmd 51(Q) addr ffe00040 is= ffffffff 51515151
    0.17> fwc addr ffe00000 cmd 0 00000000 32bit x 16 bit
    0.17> fwc addr ffe00154 cmd 98 00980098 32bit x 16 bit
    0.17> is= cmd 51(Q) addr ffe00040 is= ffffffff 00510051
    0.18> fwc addr ffe00000 cmd 0 00000000 32bit x 32 bit
    0.18> fwc addr ffe00154 cmd 98 00000098 32bit x 32 bit
    0.18> is= cmd 51(Q) addr ffe00040 is= ffffffff 00000051
    0.18> fwrite addr ffe00000 cmd 0 0000000000000000 64 bit x 8 bit
    0.20> fwrite addr ffe002a8 cmd 98 9898989898989898 64 bit x 8 bit
    0.20> is= cmd 51(Q) addr ffe00080 is= ffffffffffffffff
5151515151515151
    0.21> fwrite addr ffe00000 cmd 0 0000000000000000 64 bit x 16 bit
    0.21> fwrite addr ffe002a8 cmd 98 0098009800980098 64 bit x 16 bit
    0.21> is= cmd 51(Q) addr ffe00080 is= ffffffffffffffff
0051005100510051
    0.23> fwrite addr ffe00000 cmd 0 0000000000000000 64 bit x 32 bit
    0.23> fwrite addr ffe002a8 cmd 98 0000009800000098 64 bit x 32 bit
    0.23> is= cmd 51(Q) addr ffe00080 is= ffffffffffffffff
0000005100000051
    0.25> fwrite addr ffe00000 cmd 0 0000000000000000 64 bit x 64 bit
    0.25> fwrite addr ffe002a8 cmd 98 0000000000000098 64 bit x 64 bit
    0.25> is= cmd 51(Q) addr ffe00080 is= ffffffffffffffff
0000000000000051
    0.26> not found
    0.26> ## Unknown FLASH on Bank 0 - Size = 0x00000000 = 0 MB
    0.26> flash_protect ON: from 0xFFF00000 to 0xFFF23FFF
    0.26> flash_protect ON: from 0xFFE0FA00 to 0xFFE0FDFF
    0.26> *** failed ***
    0.28> ### ERROR ### Please RESET the board ###



There already was a discussion about this flash chip and u-boot but this
 thread doesn't came to an end.

http://www.nabble.com/Help%3A-flash-driver-for-CFI-complient-flash-t893564.html#a2318022


Any hints?


Best regards,

Andre