public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: John Dallaway <john@dallaway.org.uk>
To: Valentin BOUSSON <ml-ecos@belphegor.eu>
Cc: eCos Discussion <ecos-discuss@sourceware.org>
Subject: [ECOS] Re: STM32F4 and Dynamic loading.
Date: Fri, 28 Feb 2014 17:47:00 -0000	[thread overview]
Message-ID: <5310CB98.9060503@dallaway.org.uk> (raw)
In-Reply-To: <531061B5.7080700@belphegor.eu>

Hi Valentin

On 28/02/14 10:15, Valentin BOUSSON wrote:

> Actually, yes it could be sufficient for my project, and digging around
> my problem, I tried to compile the CYGPKG_OBJLOADER package too.
> And this is with this one I have a conflict problems :
> 
> This package requires CYGINT_SERVICES_OBJLOAD_RELOCATOR == 1,
> which is implemented by :
> - CYGBLD_OBJLOADER_ARCHITECTURE_{POWERPC,I386,ARM}
> 
> The problem now is the template for stm32f4discovery seems to "inherit"
> from CYGPKG_HAL_CORTEXM while CYGBLD_OBJLOADER_ARCHITECTURE_ARM is
> calculated from CYGPKG_HAL_ARM only.
> 
> Is there a structural incompatibility between HAL_ARM and HAL_CORTEXM ?
> Or that's a thing I can modify/hack in the ecos.
> 
> Or (I don't hope so, I'm still a beginner) do I have to implement
> something to create the CYGBLD_OBJLOADER_ARCHITECTURE_CORTEXM ?

Good question. It depends whether relocate_arm.c supports the various
relocation types used with Cortex-M targets. The code calls CYG_ASSERT
if it encounters relocation types it does not support, so you might try
experimenting with cdl_option CYGBLD_OBJLOADER_ARCHITECTURE_ARM modified
as follows and see if it works:

    calculated CYGPKG_HAL_ARM || CYGPKG_HAL_CORTEXM

Of course, you should enable CYGDBG_USE_ASSERTS.

If you decide to experiment, please report back to the ecos-discuss list.

I hope this helps...

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

  reply	other threads:[~2014-02-28 17:47 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-20 16:13 [ECOS] Specific needs on stm32 Valentin BOUSSON
2014-01-20 20:04 ` "Ilija Kocho [Илија Кочо]"
     [not found]   ` <52E24132.2020505@belphegor.eu>
2014-01-26  2:51     ` "Ilija Kocho [Илија Кочо]"
     [not found]       ` <530C6522.7020704@belphegor.eu>
     [not found]         ` <530C9551.1060603@belphegor.eu>
     [not found]           ` <530DF5CB.9060909@belphegor.eu>
2014-02-26 16:01             ` "Ilija Kocho [Илија Кочо]"
2014-02-27 12:49               ` [ECOS] STM32F4 and Dynamic loading Valentin BOUSSON
2014-02-27 17:12                 ` [ECOS] " John Dallaway
2014-02-28 10:15                   ` Valentin BOUSSON
2014-02-28 17:47                     ` John Dallaway [this message]
2014-01-21  0:05 ` [ECOS] Specific needs on stm32 "Ilija Kocho [Илија Кочо]"

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=5310CB98.9060503@dallaway.org.uk \
    --to=john@dallaway.org.uk \
    --cc=ecos-discuss@sourceware.org \
    --cc=ml-ecos@belphegor.eu \
    /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).