public inbox for
 help / color / mirror / Atom feed
Subject: [Bug 1001837] Rich FlexBus RAM layout
Date: Sat, 04 May 2013 16:20:00 -0000	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

Please do not reply to this email, use the link below.

--- Comment #16 from Mike Jones <> ---
Created attachment 2227
FXM Specific Exception

This test case will generate an exception on FXM hardware that cannot be
generated on non-FXM hardware. It manifests like the description in Bug 1001764
- Enhancement of MMC/SD over SPI driver. The zip contains an ecm file, code,
and all patches used.

When the application is run, a loop will open a file on an SD card, develop
strings with snprintf, write them to the file, flush the filesystem, and close
the file. When it is run, the problem always occurs when the variable "dev" in
the SPI code is 0xFFFFFFFF and results in an exception 5. It has to be run for
many minutes to cause failure, but typically it will fail in less than 10 mins.


If you have time to run this, it might eliminate or confirm if the problem is
related/unrelated to hardware reliability. Once we know it is not related to
bad hardware, perhaps we can form some theories about the cause of the

Please note that all I2C code is commented out, so this only uses FXM and SD
card and should run on any FXM hardware with SD support. I ran it on a K60
100Mhz, so there is no cache. I have disabled the cache in the ecm as well.

I put the attachment here rather than the SPI bug because I cannot reproduce it
on non-FXM hardware. If it really is a MMC bug, we can move it.

You are receiving this mail because:
You are on the CC list for the bug.

  parent reply	other threads:[~2013-05-04 16:20 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-30 13:22 [Bug 1001837] New: " bugzilla-daemon
2013-04-30 13:24 ` [Bug 1001837] " bugzilla-daemon
2013-04-30 13:25 ` bugzilla-daemon
2013-05-02  8:44 ` bugzilla-daemon
2013-05-02  8:45 ` bugzilla-daemon
2013-05-03  5:40 ` bugzilla-daemon
2013-05-03  9:05 ` bugzilla-daemon
2013-05-03 16:51 ` bugzilla-daemon
2013-05-03 16:52 ` bugzilla-daemon
2013-05-03 16:52 ` bugzilla-daemon
2013-05-03 16:53 ` bugzilla-daemon
2013-05-03 17:10 ` bugzilla-daemon
2013-05-03 17:24 ` bugzilla-daemon
2013-05-03 17:48 ` bugzilla-daemon
2013-05-03 18:00 ` bugzilla-daemon
2013-05-03 18:01 ` bugzilla-daemon
2013-05-03 18:06 ` bugzilla-daemon
2013-05-04 16:20 ` bugzilla-daemon [this message]
2013-05-05 16:16 ` bugzilla-daemon
2013-05-18 19:14 ` bugzilla-daemon
2013-06-01 22:46 ` bugzilla-daemon
2013-06-01 22:50 ` bugzilla-daemon
2013-06-01 22:54 ` bugzilla-daemon
2013-06-02 17:12 ` bugzilla-daemon

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \

* 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).