public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Nick Garnett <nickg@calivar.com>
To: ecos-discuss@ecos.sourceware.org
Subject: Re: [ECOS] ecos-3.0 current stm32 bug?
Date: Thu, 25 Aug 2011 12:12:00 -0000	[thread overview]
Message-ID: <4E563C1E.7030406@calivar.com> (raw)
In-Reply-To: <4E563112.9060608@gmx.ch>


> Sound logic but:
> Why would the code built under cygwin run (same architecture with 
> bootloader and application) but not work when built under Linux? On both 
> OS I use the same version of the arm-eabi tools. On both OS I use the 
> same ecos library (ecos-3.0) and the same source code for 
> bootloader/application.
> 
> Any idea about what would make the difference?

That is less easy to answer.

In theory your builds should produce similar, if not identical,
executables. Certainly as far as the initialization code is concerned.

Something you could try is to use arm-eabi-objdump with the -d option to
disassemble the ELF files. Then compare the resulting outputs, even run
them through diff. Any differences between the files might give a clue
as to what is going wrong. Concentrate in particular on hal_reset_vsr,
since this is the most likely site of any problem.



-- 
Nick Garnett                                       eCos Kernel Architect
eCosCentric Limited    http://www.eCosCentric.com       The eCos experts
Barnwell House, Barnwell Drive, Cambridge, UK.      Tel: +44 1223 245571
Registered in England and Wales:                         Reg No: 4422071

-- 
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:[~2011-08-25 12:12 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-24 10:34 Philipp Meier
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 [this message]
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=4E563C1E.7030406@calivar.com \
    --to=nickg@calivar.com \
    --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).