From: "Syed Ismail" <ismail.riyaz@dyansys.com>
To: ecos-discuss@ecos.sourceware.org
Subject: Re: Re: [ECOS] nor flash issue
Date: Sun, 02 Dec 2007 17:04:00 -0000 [thread overview]
Message-ID: <20071202170149.64694.qmail@pro-237-182.rediffmailpro.com> (raw)
On Tue, 27 Nov 2007 Gary Thomas wrote :
> Andrew Lunn wrote:
> > On Mon, Nov 26, 2007 at 06:01:46PM -0000, Syed Ismail
> wrote:
> >> Hi
> >> I have an arm based processor and amd nor flash. I
> built redboot for mx31 ADS board and everything works
> fine. We have a custom board and are building redboot
> for it. Here is my problem.
> >> i do fis write and when i read the written space
> using x -b...., I get a corrupted data(for eg,"data" is
> listed as "dada" in flash).
> >> I read the data through debugging tool(not through
> redboot) and found that the data written using fis
> write in flash is actually fine. Any data in flash is
> not being read properly through redboot. write works
> just fine. What might be the problem. (Same code works
> fine in the ADS board).
> >
> > Try setting CYGSEM_IO_FLASH_READ_INDIRECT
>
> Also, try turning off data caching on the FLASH device.
>
Thanks for the suggestion. When I looked at the data cache code, I came across the configuration registers (WEIM) for the chipselect which connects nor flash in hal_platform_setup.h. Changing the configuration register values to those which worked when testing the flash separately, solved it. Now the redboot works fine. Thanks again Gary and Andrew.
--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss
reply other threads:[~2007-12-02 17:04 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20071202170149.64694.qmail@pro-237-182.rediffmailpro.com \
--to=ismail.riyaz@dyansys.com \
--cc=ecos-discuss@ecos.sourceware.org \
/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).