From: Timur Tabi <timur@freescale.com>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] Sector size with CFI driver?
Date: Tue, 31 Oct 2006 15:40:40 -0600 [thread overview]
Message-ID: <4547C2D8.2090307@freescale.com> (raw)
In-Reply-To: <4547B7C8.1070202@orkun.us>
Tolunay Orkun wrote:
> It looks like you are using a bottom boot block flash and there are 8
> smaller sectors of 8KiB and 127 larger sectors of 64KiB. You will have
> to debug the 1.1.5 version to see why it is not seeing the 8 small
> sectors. If both builds are using cfi_driver.c then a bug must have been
> introduced recently.
I defined CFG_FLASH_EMPTY_INFO and ran some tests. I tried erasing the last
two sectors, both 0x10000 bytes in size, at FEFE0000 and FEFF0000.
After I erase FEFE0000 and do "flinfo", an "E" appears after the FEFE0000.
When I copy data to FEFE0000 and do "flinfo" again, the E disappears. So far
so good.
However, no matter what I do, I can't get an "E" to appears after the
FEFF0000. In addition, the only way I can erase that sector is with "erase
feff0000 feffffff". Any other end-value gets me a "end address not on sector
boundary" message.
Could this be a hardware problem?
--
Timur Tabi
Linux Kernel Developer @ Freescale
next prev parent reply other threads:[~2006-10-31 21:40 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-31 20:00 [U-Boot-Users] Sector size with CFI driver? Timur Tabi
2006-10-31 20:53 ` Tolunay Orkun
2006-10-31 21:40 ` Timur Tabi [this message]
2006-10-31 21:59 ` Tolunay Orkun
2006-10-31 23:08 ` Timur Tabi
2006-11-01 13:05 ` Stefan Roese
2006-11-01 16:34 ` Timur Tabi
2006-11-01 16:44 ` Ben Warren
2006-11-01 16:58 ` Timur Tabi
2006-11-01 17:02 ` Stefan Roese
2006-11-01 17:08 ` Timur Tabi
2006-11-01 17:41 ` Tolunay Orkun
2006-11-01 17:52 ` Timur Tabi
2006-11-01 17:47 ` Tolunay Orkun
-- strict thread matches above, loose matches on Subject: below --
2006-11-01 17:47 Yogi
2006-11-01 18:29 Yogi
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=4547C2D8.2090307@freescale.com \
--to=timur@freescale.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