From: Tolunay Orkun <listmember@orkun.us>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] Sector size with CFI driver?
Date: Tue, 31 Oct 2006 14:53:28 -0600 [thread overview]
Message-ID: <4547B7C8.1070202@orkun.us> (raw)
In-Reply-To: <4547AB63.8090802@freescale.com>
Timur Tabi wrote:
> When using the CFI driver, how is the sector size determined?
>
> The reason I ask is that I have two different versions of U-Boot for my board,
> both developed in-house. One version is based on 1.1.3, and the other on
> 1.1.5. The 1.1.5 version cannot erase/program the last sector on the first
> flash bank. Also, the 1.1.3 says this when I do flinfo:
>
> Bank # 1: CFI conformant FLASH (16 x 16) Size: 8 MB in 135 Sectors
> Erase timeout 16384 ms, write timeout 1 ms, buffer write timeout 1 ms,
> buffer size 1
> Sector Start Addresses:
> FE000000 FE002000 FE004000 FE006000 FE008000
> FE00A000 FE00C000 FE00E000 FE010000 FE020000
>
> And the 1.1.5 version says:
>
> Bank # 1: CFI compatible FLASH (16 port width with 16 chip width)
> Command set is AMD/Fujitsu standard. Driver is polling DQ6 for status checking.
> Size: 8 MB in 135 Sectors
> Erase timeout 16384 ms, write timeout 0 ms, buffer write timeout 1 ms,
> buffer size 1
> Sector Start Addresses:
> FE000000 FE010000 FE020000 FE030000 FE040000
> FE050000 FE060000 FE070000 FE080000 FE090000
>
> As you can see the sector sizes are different, but everything else is the same.
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.
next prev parent reply other threads:[~2006-10-31 20:53 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 [this message]
2006-10-31 21:40 ` Timur Tabi
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=4547B7C8.1070202@orkun.us \
--to=listmember@orkun.us \
--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