From: "Philipp Meier" <pme.neratec@gmx.ch>
To: ecos-discuss@ecos.sourceware.org
Subject: [ECOS] ecos-3.0 current stm32 bug?
Date: Wed, 24 Aug 2011 10:34:00 -0000 [thread overview]
Message-ID: <20110824103404.51600@gmx.net> (raw)
Hi all
I have a firmware split into two parts:
1. a "bootloader"
2. a "application"
I now need to move from Windows (cygwin) development environment to Linux development environment and at the same time use the current ecos version (i.e. what I get when I clone the ecos mercurial repository) instead of the "original" (back in 2009) ecos-3.0 version.
The situation is now as follows:
1. I download (to my stm32 device) the Linux/ecos-current built "bootloader"
2. I download (to my stm32 device) the Linux/ecos-current built "application"
3. I start the application and in line 187 of file 'hal/cortexm/arch/current/src/hal_msic.c' instead of branching to 'hal_switch_state_vsr' it branches to 'hal_default_exception_vsr' function!
To analyze the problem I then:
4. Downloaded (to my stm32 device) the cyginw/ecos-3.0 built "bootloader"
5. Still having the Linux/ecos-current built "application"
6. And in line 187 (of the above mentioned file) it branches (as it should) to 'hal_switch_state_vsr' and the application is starting up and running fine!
Who can give me a hint about
* what has been changed in ecos-current cortexm stm32 that could cause this problem
* or what else I could analyze to find out why ecos-current (built on Linux, arm-eabi-gcc (eCosCentric GNU tools 4.3.2-sw); under cygwin I also used the arm-eabi-gcc version 4.3.2 pre-built by eCosCentric)
Regards
Philipp
--
NEU: FreePhone - 0ct/min Handyspartarif mit Geld-zurück-Garantie!
Jetzt informieren: http://www.gmx.net/de/go/freephone
--
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 reply other threads:[~2011-08-24 10:34 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-24 10:34 Philipp Meier [this message]
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
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=20110824103404.51600@gmx.net \
--to=pme.neratec@gmx.ch \
--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).