public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Ilija Kocho <ilijak@siva.com.mk>
To: Davide Pippa <thepyper@gmail.com>
Cc: ecos-discuss@sourceware.org
Subject: Re: [ECOS] ecos on TWR-K70F120 "hangs" on startup in cyg_hal_invoke_constructors()
Date: Thu, 14 Feb 2013 11:42:00 -0000	[thread overview]
Message-ID: <511CCDAD.9000504@siva.com.mk> (raw)
In-Reply-To: <CAJuNW1MTuvk95Rk_K93NVmdYKkqfZb-vGmoSx1r1xxJNmoE_cA@mail.gmail.com>

On 14.02.2013 12:29, Davide Pippa wrote:
> Thanks for the help!
>
> I just tried to compile things with the eCos Gnutools 4.6.3, and things
> seems to behave better,
> as I can go further with my debugging session, to the point that I get into
> "cyg_start", and even more.
> Still cannot get into my main() function, but I get no sticky errors at all
> and I just need to debug
> further to see what I'm missing...
> A question: does that compiler support hardware floating point for
> cortex-m4?

Sure. You can even see VFP floating point registers with GDB 7.4.1 that
comes with eCos Gnutools 4.6.3 provided that GDB server supports them.
Only, for the time being eCos floating point support is not yet
committed to CVS so you shall have to apply the patches from eCos'
Bugzilla http://bugs.ecos.sourceware.org/show_bug.cgi?id=1001607

I will appreciate feedback.

Ilija


-- 
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:[~2013-02-14 11:42 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-09 11:19 Davide Pippa
2013-02-10 21:01 ` Ilija Kocho
     [not found]   ` <CAJuNW1M4EaYC4BSr171fKwtWZeZRgv4+41Bf=VFw24_F4g0XBw@mail.gmail.com>
2013-02-14 11:30     ` Davide Pippa
2013-02-14 11:42       ` Ilija Kocho [this message]

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=511CCDAD.9000504@siva.com.mk \
    --to=ilijak@siva.com.mk \
    --cc=ecos-discuss@sourceware.org \
    --cc=thepyper@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).