From: Andrew Lunn <andrew@lunn.ch>
To: Joe Porthouse <jporthouse@toptech.com>
Cc: ecos-discuss@ecos.sourceware.org
Subject: Re: [ECOS] Network driver problem only with larger programs (cache issues?)
Date: Thu, 31 Aug 2006 06:46:00 -0000 [thread overview]
Message-ID: <20060831064608.GM25688@lunn.ch> (raw)
In-Reply-To: <MDAEMON-F200608310018.AA1843500md50000000049@toptech.com>
On Thu, Aug 31, 2006 at 12:18:36AM -0400, Joe Porthouse wrote:
> Ok, I'm positive I'm going nuts now.... Code seems good, if I can only get
> the processor to correctly execute it.
>
> Started seeing the code lock up after 10-30 minutes without a JTAG attached
> so I started to look further into the possible cache issues.
There was once a problem with the EBSA285 setup of the SDRAM
controller. The controller had been initialised for 1/2 the actual
memory. This resulted in the top address line being left to
float. Most of the time it floated one way, but occassionally, it
floated the other way, and so it seemed to forget things.....
See if you can make packages/hal/arm/ebsa286/current/tests/sdram0.cxx
work on your target. Also try running the
packages/hal/common/current/tests/cache.c
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
next prev parent reply other threads:[~2006-08-31 6:46 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-30 15:20 [ECOS] Network driver problem only with larger programs (ARM adv needed) Jay Foster
2006-08-31 4:18 ` [ECOS] Network driver problem only with larger programs (cache issues?) Joe Porthouse
2006-08-31 6:46 ` Andrew Lunn [this message]
2006-08-31 20:38 ` Joe Porthouse
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=20060831064608.GM25688@lunn.ch \
--to=andrew@lunn.ch \
--cc=ecos-discuss@ecos.sourceware.org \
--cc=jporthouse@toptech.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).