On 12/02/07, Chandru <
chandrasekar@aelixsystems.com> wrote:
> Thanks Brad.
No problem :)
> Can you suggest me a few steps for debugging this issue ? Like I would like
> to read this nand device contents. I couldn't do it with nanddump. Is thr
> any other way to get the contents of the nand ? I would like to read a
> particular location on the nand, the contents on that particular location ?
I may have missed a previous message of yours, but you say that
nanddump doesn't work? Can you give the error output? I think
getting nanddump and nandwrite working are probably the first steps in
ensuring a working MTD nand driver.
Most (all?) NAND chips guarentee that block 0 will always be a good
block. I would start my driver debugging by using nandwrite to write
a few bytes to block 0, verify them with nanddump and then erase &
verify the block. This will test the data path to your chip via the
MTD driver.
If that step is failing, then you must get that working properly first.
Good luck!
Brad
>
> Thanks,
> Chandru.
>
>
>
> -----Original Message-----
> From: yaffs-bounces@lists.aleph1.co.uk
> [mailto:yaffs-bounces@lists.aleph1.co.uk] On Behalf Of
> yaffs-request@lists.aleph1.co.uk
> Sent: Friday, February 09, 2007 5:31 PM
> To: yaffs@lists.aleph1.co.uk
> Subject: yaffs Digest, Vol 21, Issue 3
>
> Send yaffs mailing list submissions to
> yaffs@lists.aleph1.co.uk
>
> To subscribe or unsubscribe via the World Wide Web, visit
> http://lists.aleph1.co.uk/cgi-bin/mailman/listinfo/yaffs
> or, via email, send a message with subject or body 'help' to
> yaffs-request@lists.aleph1.co.uk
>
> You can reach the person managing the list at
> yaffs-owner@lists.aleph1.co.uk
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of yaffs digest..."
>
>
> Today's Topics:
>
> 1. Re: Bad blocks - DMESG (Brad Beveridge)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Thu, 8 Feb 2007 17:05:11 -0800
> From: "Brad Beveridge" <brad.beveridge@gmail.com>
> Subject: Re: [Yaffs] Bad blocks - DMESG
> To: yaffs@lists.aleph1.co.uk
> Message-ID:
> <de95dc6f0702081705w5692aa08l37d316a6c9816649@mail.gmail.com>
> Content-Type: text/plain; charset=ISO-8859-1; format=flowed
>
> Hi Chandru,
> Blocks on NAND chips can and do go bad, and chips often come from the
> factory with bad blocks.
> It looks like Yaffs has marked four blocks bad, which is probably to
> be expected if this is the first time you've run yaffs on this device.
> In my experience, after an initial flurry of blocks being marked as
> bad, things will settle down and blocks will stay good for a long
> time.
>
> If you can read and write files reliably to the Yaffs partition
> without excessive numbers of blocks being marked bad, then I would
> believe that you have set Yaffs up correctly.
>
> NAND drivers are often all or nothing, either it works properly, or it
> really doesn't work at all.
>
> Hope that helps,
> Brad
>
>
>
> ------------------------------
>
> _______________________________________________
> yaffs mailing list
> yaffs@lists.aleph1.co.uk
> http://lists.aleph1.co.uk/cgi-bin/mailman/listinfo/yaffs
>
>
> End of yaffs Digest, Vol 21, Issue 3
> ************************************
>
>
> __________ NOD32 2045 (20070208) Information __________
>
> This message was checked by NOD32 antivirus system.
> http://www.eset.com
>
>
>
> _______________________________________________
> yaffs mailing list
> yaffs@lists.aleph1.co.uk
> http://lists.aleph1.co.uk/cgi-bin/mailman/listinfo/yaffs
>
(text/plain)