From: Dawid Prus - praca <dawid.prus@o2.pl>
To: linux-mtd@lists.infradead.org
Subject: Problem with NAND on MIPS32 board (mtd 20050122)
Date: Thu, 29 Nov 2012 23:12:31 +0100 [thread overview]
Message-ID: <4716786.20121129231231@o2.pl> (raw)
Hello.
I'm trying to use a MIPS32-24KE (from Vitesse 7429) with NAND flash SAMSUNG K9F1G08U0B / Micron 29F2G08AAD,
and I have problem with reading it. Software I'm using is KAMIKAZE 8.09.2 (mtd 20050122)
Problem is when i try to read also the ID or any data from chip.
When I read ID for SAMSUNG I getting:
NAND device: Manufacturer ID: 0xFF, Chip ID: 0xEC (next readed byte is 0xF1) - 0xFF in mfc field makes
that my NAND is not recognized
Same situation with Micron (first byte 0xFF)
I changed nand_base.c and put one extra read command before reading first ID byte:
chip->cmdfunc(mtd, NAND_CMD_READID, 0x00, -1);
read_byte(mtd); // added command
*maf_id = chip->read_byte(mtd);
NAND is now recognized and I have log (dmesg) like this:
.....
RedBoot partition parsing not available
Using physmap partition information
Creating 4 MTD partitions on "physmap-flash.0":
0x00000000-0x00040000 : "redboot"
0x00040000-0x00080000 : "config"
0x007c0000-0x008c0000 : "linux"
0x008c0000-0x00bc0000 : "rootfs"
mtd: partition "rootfs" set to be root filesystem
block2mtd: version $Revision: 1.30 $
NAND device: ec,f1,80,15,40 // this is my exta function
NAND device: Manufacturer ID: 0xec, Chip ID: 0xf1 (Samsung NAND 128MiB 3,3V 8-b)
Scanning device for bad blocks
Creating 1 MTD partitions on "gen_nand":
0x00000000-0x08000000 : "rootfs_data"
TCP cubic registered
NET: Registered protocol family 17
VFS: Mounted root (squashfs filesystem) readonly.
Freeing unused kernel memory: 108k freed
......
After this, when NAND is recognized I have still problem with reading
(first byte is FF and other are shifted to right)
You can see it when I do nandtest (from mtd-utils)
root@OpenWrt:/# nandtest /dev/mtd4
ECC corrections: 0
ECC failures : 0
Bad blocks : 0
BBT blocks : 0
00000000: reading...
ECC failed at 00000000
00000000: checking...
compare failed. seed 1797617246
Byte 0x0 is ff should be 0a
Byte 0x1 is 0a should be 6e
Byte 0x2 is 6e should be 7e
Byte 0x3 is 7e should be 8e
Byte 0x4 is 8e should be aa
Byte 0x5 is aa should be 23
Byte 0x6 is 23 should be 91
From myself I can add that NAND i permanently selected - CS pin goes to GND (through 10k)
Please help me to find some solution to fix this issue.
Sorry about my english
Best Regards
Dawid
next reply other threads:[~2012-11-29 22:14 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-29 22:12 Dawid Prus - praca [this message]
2012-11-30 5:18 ` Problem with NAND on MIPS32 board (mtd 20050122) Calvin Johnson
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4716786.20121129231231@o2.pl \
--to=dawid.prus@o2.pl \
--cc=linux-mtd@lists.infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox