[microblaze-uclinux] MTD + Spansion Flash

[mak visp <mak.visp@xxxxxxxxx>]

Hello,

I am using non standard Spansion Flash (WS256N) on my board. As the
support not there for such flash in either u-boot and petalinux
kernel, I myself modified some of the cfi related files. The change is
in the address (instead of 0x55, made it 0x555). My u-boot works fine.
but when the kernel boots, it is not happy. it gives the message
mentioning "kobject_add failed for physmap-flash.0 with -EEXIST, don't
try to register things with the same name in the same directory".

I have attached the log below:

physmap platform flash device: 04000000 at 8c000000
Number of erase regions: 3
Primary Vendor Command Set: 0002 (AMD/Fujitsu Standard)
Primary Algorithm Table at 0040
Alternative Vendor Command Set: 0000 (None)
No Alternate Algorithm Table
Vcc Minimum:  1.7 V
Vcc Maximum:  1.9 V
No Vpp line
Typical byte/word write timeout: 64 µs
Maximum byte/word write timeout: 1024 µs
Typical full buffer write timeout: 512 µs
Maximum full buffer write timeout: 8192 µs
Typical block erase timeout: 1024 ms
Maximum block erase timeout: 8192 ms
Chip erase not supported
Device size: 0x2000000 bytes (32 MiB)
Flash Device Interface description: 0x0001
  - x16-only asynchronous interface
Max. bytes in buffer write: 0x40
Number of Erase Block Regions: 3
  Erase Region #0: BlockSize 0x8000 bytes, 4 blocks
  Erase Region #1: BlockSize 0x20000 bytes, 254 blocks
  Erase Region #2: BlockSize 0x8000 bytes, 4 blocks
physmap-flash.0: Found 2 x16 devices at 0x0 in 32-bit bank
 Amd/Fujitsu Extended Query Table at 0x0040
physmap-flash.0: CFI does not contain boot bank location. Assuming top.
number of CFI chips: 1
cfi_cmdset_0002: Disabling erase-suspend-program due to code brokenness.
7 cmdlinepart partitions found on MTD device physmap-flash.0
Creating 7 MTD partitions on "physmap-flash.0":
0x00000000-0x00040000 : "boot"
0x00040000-0x00080000 : "bootenv"
0x00080000-0x000c0000 : "config"
0x000c0000-0x01ec0000 : "image"
0x01ec0000-0x028c0000 : "jffs2"
0x028c0000-0x032c0000 : "backup"
0x032c0000-0x03fc0000 : "spare"
kobject_add failed for physmap-flash.0 with -EEXIST, don't try to
register things with the same name in the same directory.

Stack:
  7ffc1ea8 00000000 4016bc94 40d3e4f8 4028b590 4016bca0 40242a00 4028b594
  4014c2b8 4028b5a3 000041ed ffffffff 00000000 4028b528 ffffffea 4028b590
  40170970 4028b520 402459c4 4028b5cc 8c000000 8c000000 ffffffff 00000000
Call Trace:
[<4016bc94>] device_add+0x84/0x4f8
[<4016bca0>] device_add+0x90/0x4f8
[<4014c2b8>] kobject_release+0x0/0x1c
[<40170970>] platform_device_add+0x108/0x188
[<40170a0c>] platform_device_register+0x1c/0x34
[<40170a04>] platform_device_register+0x14/0x34
[<402a6188>] physmap_init+0x34/0x50
[<402a616c>] physmap_init+0x18/0x50
[<402a613c>] map_rom_init+0x14/0x2c
[<400001fc>] init+0x100/0x358
[<400001fc>] init+0x100/0x358
[<40001254>] kernel_thread_helper+0xc/0x20
[<40001248>] kernel_thread_helper+0x0/0x20

uclinux[mtd]: RAM probe address=0x402ce58c size=0x191000
Creating 1 MTD partitions on "RAM":
0x00000000-0x00191000 : "ROMfs"
uclinux[mtd]: set ROMfs to be root filesystem index=7
Generic platform RAM MTD, (c) 2004 Simtec Electronics
block2mtd: version $Revision: 1.30 $

Even though this message it works fine and my system boots properly.
Can anybody suggest, what has gone wrong, and how to fix it?

-- 
Thanks
Mak

___________________________
microblaze-uclinux mailing list
microblaze-uclinux@xxxxxxxxxxxxxx
Project Home Page : http://www.itee.uq.edu.au/~jwilliams/mblaze-uclinux
Mailing List Archive : http://www.itee.uq.edu.au/~listarch/microblaze-uclinux/