From: rk.raggit@gmail.com (RK Raggit)
To: linux-arm-kernel@lists.infradead.org
Subject: cortex-m3 booting failure
Date: Mon, 10 May 2010 12:18:05 +0530 [thread overview]
Message-ID: <o2hec1f3d401005092348rcbf5b3eayc31eca6e15963e8b@mail.gmail.com> (raw)
In-Reply-To: <1273153908.2094.5.camel@e102109-lin.cambridge.arm.com>
Hi Catalin,
>
> I can't really tell what's happening but I'm going to release a new set
> of patches against 2.6.33 sometime next week and there are some improved
> error messages for Cortex-M3 support.
>
> Do you have KALLSYMS enabled in the kernel?
Yes. Debugging a bit further i enabled the hard fault processor
exception catch in
RVD. On doing this i notice that when running commands (like 'ls' or
'date') on console
the processor hard faults. The HFSR shows "0x40000000" while BFSR
reads "0x04" indicating an imprecise data access fault. Other U/MMFSR are 0x0.
I am wondering why an imprecise data access fault could happen at this stage ?
--RK
prev parent reply other threads:[~2010-05-10 6:48 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-06 10:30 cortex-m3 booting failure RK Raggit
2010-05-06 13:51 ` Catalin Marinas
2010-05-06 16:20 ` RK Raggit
2010-05-10 6:48 ` RK Raggit [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=o2hec1f3d401005092348rcbf5b3eayc31eca6e15963e8b@mail.gmail.com \
--to=rk.raggit@gmail.com \
--cc=linux-arm-kernel@lists.infradead.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 NNTP newsgroup(s).