From: fcipaq <daniel.kammer@web.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] ACER n310 NAND write protection issue
Date: Wed, 11 May 2011 01:29:06 -0700 (PDT) [thread overview]
Message-ID: <31592314.post@talk.nabble.com> (raw)
Hey everyone,
I've got an ACER n310 (n300 series). It features a s3c2440 running at 300
MHz, 64 MB SDRAM and 128 MB NAND ROM (it's Samsung k9f1g08). It's not
equipped with any NOR-Flash. Apart from that it's got quite a similar
configuration as FriendlyARM's Mini2440.
I downloaded the sources of u-boot and configured it according to my PDA's
hardware. So far, u-boot is running and I'm able to read the whole
NAND-Flash. But when I'm trying to unlock the NAND-Flash, I get the
following error message:
n310 # nand unlock
device 0 whole chip
nand_unlock: start: 00000000, length: 134217728!
nand_unlock: Device is write protected!
Error unlocking NAND flash, write and erase will probably fail
What I conclude from that is: the (NOT)WP-Pin is set to ground. The Mini2440
is not effected by this kind of issue as (according to the schematics) the
(NOT)WP-Pin is connected to VCC.
However there must be a way to toggle this pin, as the original
ACER-bootloader and WM5 respectively are able to write to the flash.
Any ideas how to cancel the write protection or how to figure out what pin
is connected to WP (schematics are not available)?
Thanks in advance and best regards
Daniel
--
View this message in context: http://old.nabble.com/ACER-n310-NAND-write-protection-issue-tp31592314p31592314.html
Sent from the Uboot - Users mailing list archive at Nabble.com.
next reply other threads:[~2011-05-11 8:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-11 8:29 fcipaq [this message]
2011-05-12 7:48 ` [U-Boot] ACER n310 NAND write protection issue fcipaq
-- strict thread matches above, loose matches on Subject: below --
2011-05-11 8:24 Daniel Kammer
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=31592314.post@talk.nabble.com \
--to=daniel.kammer@web.de \
--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