From: Nick Garnett <nickg@calivar.com>
To: ecos-discuss@ecos.sourceware.org
Subject: Re: [ECOS] ecos-3.0 current stm32 bug?
Date: Thu, 25 Aug 2011 10:38:00 -0000 [thread overview]
Message-ID: <4E5625FC.2030803@calivar.com> (raw)
In-Reply-To: <20110825084845.184240@gmx.net>
On 25/08/11 09:48, Philipp Meier wrote:
> Hello Christophe
>
> it is the SWI instruction ("svc 0" in disassem code) that triggers the exception (therefore breakpoint in hal_switch_state_vsr is never reached).
>
> Where does the SWI instruction get's it's information about where to jump to? Is it the hal_vsr_table (located at 0x20000000)? In entry 11 I have 0x8040025 which is the address for hal_switch_state_vsr - and yet it does not jumps to 0x8040025 but instead to 0x8040042 (hal_default_exception_vsr).
>
> Any idea about the reason for this behaviour?
The SWI is probably causing the CPU to take a HardFault exception
because BASEPRI is higher than the priority of the SWI exception.
If I understand correctly, both your bootloader and application are
configured for ROM startup. The ROM startup code in hal_misc.c expects
to find the CPU in its initial state. When your application runs, the
bootloader has already run this code and put it into a different state,
which will then cause the SWI to throw a HardFault.
For your application you really need a new startup type that does the
RAM initialization parts of a ROM startup, but omits parts of the
hardware initialization.
--
Nick Garnett eCos Kernel Architect
eCosCentric Limited http://www.eCosCentric.com The eCos experts
Barnwell House, Barnwell Drive, Cambridge, UK. Tel: +44 1223 245571
Registered in England and Wales: Reg No: 4422071
--
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:[~2011-08-25 10:38 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-24 10:34 Philipp Meier
2011-08-24 11:35 ` Sergei Gavrikov
2011-08-24 14:11 ` Philipp Meier
2011-08-24 14:26 ` Christophe Coutand
2011-08-24 14:58 ` Philipp Meier
2011-08-24 16:44 ` Christophe Coutand
2011-08-25 8:49 ` Philipp Meier
2011-08-25 9:37 ` Christophe Coutand
2011-08-25 10:01 ` Philipp Meier
2011-08-25 10:38 ` Nick Garnett [this message]
2011-08-25 11:25 ` Philipp Meier
2011-08-25 12:12 ` Nick Garnett
2011-08-25 12:13 ` Philipp Meier
2011-08-25 12:31 ` Nick Garnett
2011-08-25 12:52 ` Philipp Meier
2011-08-25 13:46 ` Nick Garnett
2011-08-24 18:54 ` Sergei Gavrikov
2011-08-25 8:54 ` Philipp Meier
2011-08-25 9:07 ` Philipp Meier
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=4E5625FC.2030803@calivar.com \
--to=nickg@calivar.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).