From: Gary Thomas <gary@mlbassoc.com>
To: Pred <pred@163.com>
Cc: Xue weihua <snowweihua@msn.com>, ecos-discuss@sources.redhat.com
Subject: Re: [ECOS] Fwd: Re: [ECOS] Very strange: fis create/write fail Err = 92
Date: Mon, 10 Nov 2003 04:02:00 -0000 [thread overview]
Message-ID: <1068436937.6577.127.camel@hermes> (raw)
In-Reply-To: <001b01c3a73d$c35d2150$88496fa6@PredNotebook>
On Sun, 2003-11-09 at 20:50, Pred wrote:
> I thought there is something wrong with the cache or lock/unlock procedure.
> Due to time limitation, I made a dirty patch to lock.c and made the fis
> create work. If you find the really reason, please feed back to the list.
> Thanks.
>
This code is known to work on all the platforms we've tested. If you
find a problem, or know of an error, we'd like to know about it - making
a change in your garage helps no one but you...
> Pred
>
>
>
> ----- Original Message -----
> From: "Xue weihua" <snowweihua@msn.com>
> To: <pred@163.com>
> Cc: <ecos-discuss@sources.redhat.com>
> Sent: Monday, November 10, 2003 9:52 AM
> Subject: [ECOS] Fwd: Re: [ECOS] Very strange: fis create/write fail Err = 92
>
>
> > I still waiting for our hw engineer's response. but I
> > turn off CYGSEM_REDBOOT_FLASH_LOCK_SPECIAL option
> > and then it work well. so just need hw engineer to fix this problem.
> > Thanks for everyone's help.
> >
> > >From: "Xue weihua" <snowweihua@msn.com>
> > >To: pred@163.com
> > >CC: ecos-discuss@sources.redhat.com
> > >Subject: Re: [ECOS] Very strange: fis create/write fail Err = 92
> > >Date: Sun, 09 Nov 2003 23:40:29 +0800
> > >
> > >Yes, I have try. I just can write a single block of the flash after
> > >unlock a single.
> > >I can't write two more continuous blocks in the same time.
> > >what is reason ? I don't think it is hw problem. do you ?
> > >
> > >
> > >>From: "Pred" <pred@163.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: Sat, 8 Nov 2003 14:50:36 +0800
> > >>
> > >>When you unlock a single block of the flash, can you successfully
> > >>write to
> > >>it?
> > >>If you can do this, but failed to unlock two more continuous blocks
> > >>and
> > >>write to them, I think there may be something wrong with the
> > >>lock/unlock
> > >>procedure.
> > >>
> > >>----- Original Message -----
> > >>From: "Gary Thomas" <gary@mlbassoc.com>
> > >>To: "Xue weihua" <snowweihua@msn.com>
> > >>Cc: <ecos-discuss@sources.redhat.com>
> > >>Sent: Saturday, November 08, 2003 1:37 AM
> > >>Subject: Re: [ECOS] Very strange: fis create/write fail Err = 92
> > >>
> > >>
> > >> > On Fri, 2003-11-07 at 09:03, Xue weihua wrote:
> > >> > > 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".
> > >> > >
> > >> >
> > >> > You only get this warning if you *don't* use the "-f" option
> > >>(which
> > >> > causes all blocks to be erased)
> > >> >
> > >> > > 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.
> > >> >
> > >> > It would be nice to find out what blocks work and which ones
> > >>fail.
> > >> > That might tell you if there is a hardware problem (and where).
> > >> >
> > >> > >
> > >> > >
> > >> > > >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
> > >> > --
> > >> > Gary Thomas <gary@mlbassoc.com>
> > >> > MLB Associates
> > >> >
> > >> >
> > >> > --
> > >> > Before posting, please read the FAQ:
> > >>http://sources.redhat.com/fom/ecos
> > >> > and search the list archive:
> > >>http://sources.redhat.com/ml/ecos-discuss
> > >> >
> > >> >
> > >>
> > >>
> > >>--
> > >>Before posting, please read the FAQ:
> > >>http://sources.redhat.com/fom/ecos
> > >>and search the list archive:
> > >>http://sources.redhat.com/ml/ecos-discuss
> > >>
> > >
> > >_________________________________________________________________
> > >ä¸èæºçæåè¿è¡äº¤æµï¼è¯·ä½¿ç¨ 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
> > >
> >
> > _________________________________________________________________
> > 享ç¨ä¸çä¸æ大ççµåé®ä»¶ç³»ç»â MSN Hotmailã http://www.hotmail.com
> >
> >
> > --
> > Before posting, please read the FAQ: http://sources.redhat.com/fom/ecos
> > and search the list archive: http://sources.redhat.com/ml/ecos-discuss
> >
> >
--
Gary Thomas <gary@mlbassoc.com>
MLB Associates
--
Before posting, please read the FAQ: http://sources.redhat.com/fom/ecos
and search the list archive: http://sources.redhat.com/ml/ecos-discuss
prev parent reply other threads:[~2003-11-10 4:02 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-10 1:52 Xue weihua
[not found] ` <001b01c3a73d$c35d2150$88496fa6@PredNotebook>
2003-11-10 3:50 ` Pred
2003-11-10 4:02 ` Gary Thomas [this message]
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=1068436937.6577.127.camel@hermes \
--to=gary@mlbassoc.com \
--cc=ecos-discuss@sources.redhat.com \
--cc=pred@163.com \
--cc=snowweihua@msn.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).