From: "Xue weihua" <snowweihua@msn.com>
To: gary@mlbassoc.com
Cc: ecos-discuss@sources.redhat.com
Subject: Re: [ECOS] Very strange: fis create/write fail Err = 92
Date: Fri, 07 Nov 2003 16:03:00 -0000 [thread overview]
Message-ID: <BAY4-F16WIh0xz1nF7Z00027a10@hotmail.com> (raw)
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset=gb2312; format=flowed, Size: 2687 bytes --]
I use the command like "fis unlock -f 0x50040000 -l 0x100000".
I think it is good.because it is work on some sectors.
Yes,I have problem when I do "fis init",it say "Warning: device contents
not erased, some blocks may not be usable".
maybe,my hw have problem,because it is new one.I have check it with our hw
engineer and he
say he will help me check it.
>From: Gary Thomas <gary@mlbassoc.com>
>To: Xue weihua <snowweihua@msn.com>
>CC: ecos-discuss@sources.redhat.com
>Subject: Re: [ECOS] Very strange: fis create/write fail Err = 92
>Date: 07 Nov 2003 07:39:58 -0700
>
>On Thu, 2003-11-06 at 23:20, Xue weihua wrote:
> > Hi everyone:
> > I have meet a very strange problem on my Intel ixp422 board.
> > Flash is Intel TE28F128J3C. After do "fis init ",it show like
> > RedBoot> fis list
> > Name FLASH addr Mem addr Length Entry point
> > RedBoot 0x50000000 0x50000000 0x00040000 0x00000000
> > RedBoot config 0x50FC0000 0x50FC0000 0x00001000 0x00000000
> > FIS directory 0x50FE0000 0x50FE0000 0x00020000 0x00000000
> >
> > Then I can't use "fis create/write" to write flash.
> >
> > RedBoot> load -r -v -b 0x01008000 zImage
> > Using default protocol (TFTP)
> > -
> > Raw file loaded 0x01008000-0x010bbad3, assumed entry at 0x01008000
> > RedBoot> fis create kernel -b 0x01008000 -l 0x100000 -f 0x50040000
> > ... Erase from 0x50040000-0x50140000: ........
> > ... Program from 0x01008000-0x01108000 at 0x50040000: Err = 92
> >
> >
> > Can't program region at 0x50040000: Error trying to program
> >
> > But I can use "fis create/write" on "RedBoot config" or "FIS
directory".
> > so it means hw has no problem. I can write . but only write some
sectors.
> > It seems these sectors have been done something on by initialize, but I
> > don't
> > know what it is . I have try "fis unlock " before "fis create/write",
it is
> > no helpful.
> >
>
>Did you actually unlock the pages that will be written during the
>"fis create"? What was the command that you used?
>
>What happens if you try this in some other region of the FLASH?
>If you do "fis init -f" (to erase all of the FLASH) - does every
>block get erased?
>
>Finally, there was a small change to the StrataFlash lock/unlock code
>just last week. If you've not tried it, maybe that will help.
>
>--
>Gary Thomas <gary@mlbassoc.com>
>MLB Associates
>
_________________________________________________________________
ÓëÁª»úµÄÅóÓѽøÐн»Á÷£¬ÇëʹÓà MSN Messenger: http://messenger.msn.com/cn
--
Before posting, please read the FAQ: http://sources.redhat.com/fom/ecos
and search the list archive: http://sources.redhat.com/ml/ecos-discuss
next reply other threads:[~2003-11-07 16:03 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-07 16:03 Xue weihua [this message]
2003-11-07 17:37 ` Gary Thomas
[not found] ` <00d401c3a5c4$b02dcaf0$1f00a8c0@PredNotebook>
2003-11-08 6:51 ` Pred
-- strict thread matches above, loose matches on Subject: below --
2003-11-09 15:40 Xue weihua
2003-11-07 6:20 Xue weihua
2003-11-07 14:40 ` Gary Thomas
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=BAY4-F16WIh0xz1nF7Z00027a10@hotmail.com \
--to=snowweihua@msn.com \
--cc=ecos-discuss@sources.redhat.com \
--cc=gary@mlbassoc.com \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).