From: John Dallaway <john@dallaway.org.uk>
To: Samuel Charnet <samcharnet@gmail.com>
Cc: ecos-discuss@sourceware.org
Subject: [ECOS] Re: STM32 ROMINT don't run
Date: Thu, 23 Jan 2014 17:06:00 -0000 [thread overview]
Message-ID: <52E14C04.30308@dallaway.org.uk> (raw)
In-Reply-To: <CACra8jX2N2HkH2QnmTh+6u76bUGOT8AyGALQiSB_g0jEXhvHFA@mail.gmail.com>
Hi Samuel
On 22/01/14 17:24, Samuel Charnet wrote:
> I want to try the ecos OS. My board come from waveshare, it is based
> on stm32f407ig core ( http://www.wvshare.com/product/EVK407I.htm )
>
> After some days I have ecos from CVS compiled. With the configtool I
> have created my library with the stm3240 template and i have modified
> the startup type to ROMINT
>
> I have a simple thread which blink a led. I can upload the binary file
> to the stm32 (i use the last openocd from source and olimex
> arm-usb-ocd-h jtag device)
>
> Unfortunately the led don't blink. With gdb i can't break on any
> function and the stack seems broken.
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
Does that resolve the issue for you?
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-23 17:06 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 ` John Dallaway [this message]
2014-01-23 18:02 ` [ECOS] " Samuel Charnet
2014-01-24 8:57 ` John Dallaway
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=52E14C04.30308@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).