From: Stefano Babic <sbabic@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] Problems flashing kernel
Date: Tue, 08 Jun 2010 16:31:15 +0200 [thread overview]
Message-ID: <4C0E5433.4050704@denx.de> (raw)
In-Reply-To: <20100608132128.GA28991@boggieman>
Kristoffer Ericson wrote:
> You are quite correct in that, thx. that also explains why it
> took a good while longer than usual.
>
> I cannot seem to shake the "Flash not Erased" problem though. Was thinking
> to increase timeout of erase/write but they dont change even when I change
> the CONFIG_SYS_FLASH_WRITE_TOUT. Any thoughts on that?
CONFIG_SYS_FLASH_WRITE_TOUT is used on some board specific driver, but
not by the CFI driver. It seems you are using the CFI driver and you
probably can drop this CONFIG_ switch.
However, I have not understood from you previous message when the flash
has not been erased. You say that an erase command for quite the whole
flash (from 512KB to the end of the flash, as CFI reports 64MB) works.
Do you try to erase the flash to store only the kernel ? Something like
"erase 0x80000 +13CA64" ?
Best regards,
Stefano Babic
--
=====================================================================
DENX Software Engineering GmbH, MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: +49-8142-66989-0 Fax: +49-8142-66989-80 Email: office at denx.de
=====================================================================
next prev parent reply other threads:[~2010-06-08 14:31 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-08 12:40 [U-Boot] Problems flashing kernel Kristoffer Ericson
2010-06-08 13:05 ` Stefano Babic
2010-06-08 13:21 ` Kristoffer Ericson
2010-06-08 14:31 ` Stefano Babic [this message]
2010-06-08 14:41 ` Kristoffer Ericson
2010-06-08 15:01 ` Stefano Babic
2010-06-08 16:34 ` Kristoffer Ericson
2010-06-08 17:34 ` Kristoffer Ericson
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=4C0E5433.4050704@denx.de \
--to=sbabic@denx.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