From: Felix Radensky <felix@embedded-sol.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] Multiple chip support in ndfc driver
Date: Tue, 07 Dec 2010 12:50:14 +0200 [thread overview]
Message-ID: <4CFE1166.8030800@embedded-sol.com> (raw)
In-Reply-To: <201012061109.36445.sr@denx.de>
Hi Stefan,
Thanks for a prompt reply.
Stefan Roese wrote:
> Hi Felix,
>
> On Sunday 05 December 2010 15:27:02 Felix Radensky wrote:
>
>> On a custom 460EX board I have a 2Gbyte NAND device, 1Gbyte per chip
>> select. I'm trying to enable support for the second NAND CS, so far
>> without success.
>>
>> U-Boot properly detects both devices, (manufacturer, size, bus width).
>> First device
>> works as expected, on second device bad blocks are reported correctly,
>> but attempt
>> to erase the device results in I/O errors on every block. The bank
>> settings are identical
>> for both chips.
>>
>> What am I missing ?
>>
>
> Perhaps a misconfiguration in your board config header? How did you configure
> the NAND driver? Take a look at DU440.h or bamboo.h for example. Those boards
> use multiple NAND devices.
>
>
Thanks for the hint. I've looked at these boards, and I cannot see
what's wrong with my configuration.
Since second chip is properly detected, I think configuration is
correct. Read also works, only erase
and program fail. Looks like a hardware problem to me.
>> BTW, I was wandering why NAND TLB window size on Canyonlands is 16Mbytes.
>>
>
> Yes. This TLB could be smaller. 1KiB should be enough. Patch welcome. ;)
>
>
OK, I'll send the patch.
Felix.
prev parent reply other threads:[~2010-12-07 10:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-05 14:27 [U-Boot] Multiple chip support in ndfc driver Felix Radensky
2010-12-06 10:09 ` Stefan Roese
2010-12-07 10:50 ` Felix Radensky [this message]
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=4CFE1166.8030800@embedded-sol.com \
--to=felix@embedded-sol.com \
--cc=u-boot@lists.denx.de \
/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