From: John Dallaway <john@dallaway.org.uk>
To: Samuel Charnet <samcharnet@gmail.com>
Cc: eCos Discussion <ecos-discuss@sourceware.org>
Subject: [ECOS] Re: STM32 ROMINT don't run
Date: Fri, 24 Jan 2014 08:57:00 -0000 [thread overview]
Message-ID: <52E22ADF.1040109@dallaway.org.uk> (raw)
In-Reply-To: <CACra8jU0qa3i0xFD+o7FoPE7p4iAExz-pY9i5gJogdgE285MCQ@mail.gmail.com>
Hi Samuel
On 23/01/14 18:02, Samuel Charnet wrote:
> John Dallaway wrote:
>
>> You may be observing the following issue:
>>
>> http://bugs.ecos.sourceware.org/show_bug.cgi?id=1001864
>>
>> Try modifying hal/cortexm/arch/current/src/hal_misc.c to read as follows:
>>
>>> #if defined(CYG_HAL_STARTUP_ROM) || defined(CYG_HAL_STARTUP_ROMINT)
>>> // Relocate data from ROM to RAM
>
> Thanks for your quick answer.
>
> I had a hope but it is not enought, it still doesn't run.
>
> the stack is different :
>
> (gdb) target remote :3333
> Remote debugging using :3333
> 0x00000000 in ?? ()
> (gdb) c
> Continuing.
> Note: automatically using hardware breakpoints for read-only addresses.
> stm32f4x.cpu -- clearing lockup after double fault
> Program received signal SIGINT, Interrupt.
> 0x00000000 in ?? ()
> (gdb) where
> #0 0x00000000 in ?? ()
> #1 0x08001d3c in Cyg_Exception_Control::deliver_exception
> (this=<optimized out>, exception_number=<optimized out>,
> exception_info=<optimized out>)
> at /home/lucky/Devel/PLSee/ecos/ecos-3.0/packages/kernel/current/src/common/except.cxx:234
> #2 0x0800005e in hal_default_exception_vsr () at
> /home/lucky/Devel/PLSee/ecos/ecos-3.0/packages/hal/cortexm/arch/current/src/vectors.S:184
> #3 0x0800005e in hal_default_exception_vsr () at
> /home/lucky/Devel/PLSee/ecos/ecos-3.0/packages/hal/cortexm/arch/current/src/vectors.S:184
> Backtrace stopped: previous frame identical to this frame (corrupt stack?)
> (gdb)
If you have not already done so, disable compiler optimisation by
removing "-O2" from the CYGBLD_GLOBAL_CFLAGS option. Also enable
CYGPKG_INFRA_DEBUG. You should then be able to step into your code from
system reset and see where the exception is triggered.
Note that STM3240G-EVAL ROMINT startup is similar to STM32F4-Discovery
ROM startup which is working fine. So I don't think there is a major
problem here. Check all references to "CYG_HAL_STARTUP == ROM" and
"CYG_HAL_STARTUP_ROM". Modify these expressions if the code they control
is also relevant for ROMINT startup.
Good luck with your debugging...
John Dallaway
eCos maintainer
http://www.dallaway.org.uk/john
--
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:[~2014-01-24 8:57 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CACra8jX5=y1-7iRktxuvK11T8zTNBPfR38=5b57PK2EJNbQ1nA@mail.gmail.com>
2014-01-22 17:24 ` [ECOS] Fwd: " Samuel Charnet
2014-01-23 17:06 ` [ECOS] " John Dallaway
2014-01-23 18:02 ` Samuel Charnet
2014-01-24 8:57 ` John Dallaway [this message]
2014-01-24 11:19 ` Samuel Charnet
2014-01-25 11:07 ` Samuel Charnet
2014-01-25 13:41 ` Samuel Charnet
2014-01-28 20:36 ` Samuel Charnet
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=52E22ADF.1040109@dallaway.org.uk \
--to=john@dallaway.org.uk \
--cc=ecos-discuss@sourceware.org \
--cc=samcharnet@gmail.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).