From: Jonathan Larmour <jlarmour@redhat.com>
To: Victor Tarasov <victor.tarasov@idealx.com>
Cc: ecos-discuss@sourceware.cygnus.com
Subject: Re: [ECOS] Hello_eCos_World on iPAQ.
Date: Mon, 23 Apr 2001 10:42:00 -0000 [thread overview]
Message-ID: <3AE46975.D208E43A@redhat.com> (raw)
In-Reply-To: <3AE439A5.581A651C@idealx.com>
Victor Tarasov wrote:
>
> Hi,
> It seems that I am not so intelligent to run alone my first RedBoot
> application on iPAQ.
> Can you help me, please?
Are you using the precompiled binaries available from
http://sources.redhat.com/ecos/boards/ipaq.html ?
Once you know you've got something working, then you will probably find it
easier to rebuild and be sure there aren't any problems with e.g. your
tools etc.
> Package installation was made by:
> >ecosconfig new ipaq redboot
> >ecosconfig import redboot_RAM.ecm
> >ecosconfig resolve
> >ecosconfig tree
> >make
>
> Hello_eCos was compiled with:
> >arm-elf-gcc -mcpu=strongarm -c -o hello.o -g -Wall
> -I/redboot/ecos-ram/install/include -ffunction-sections -fdata-sections
> hello.c
> >arm-elf-gcc -mcpu=strongarm -nostartfiles
> -L/redboot/ecos-ram/install/lib -Wl,--gc-sections -o hello hello.o
> -Ttarget.ld -nostdlib /redboot/ecos-ram/install/lib/version.o
>
> Then GDB:
> >arm-elf-gdb -nw hello
It looks what you are describing is that you are using the build tree
configured with "ecosconfig new ipaq redboot" to build your applications.
This isn't right - the redboot template is used solely for building redboot
itself. Instead start with a new clean build tree and just use a default
configuration like:
ecosconfig new ipaq
ecosconfig tree
make
In fact then do:
make tests
which will build some test applications under install/tests/ which you can
try out on the board, which may help avoid any pilot error in building the
hello world example.
> PS: How can I recompile RedBoot for iPAQ?
> "RedBoot" template with the imported configuration
> $ECOS_REPOSITORY/packages/hal/arm/sa11x0/ipaq/current/misc/redboot_Compaq.ecm
> (also redboot_rom.ecm)
> gives the binaries that are not working on the iPAQ.
> The templates "all", "default" and "stubs" give the error during
> compilation.
Do recompile RedBoot you must use the redboot template only. Make sure you
are using a new clean build tree when you build for a different template.
I take it you are following the instructions in the RedBoot user's guide on
installing for the ipaq, of course.
Jifl
--
Red Hat, Rustat House, Clifton Road, Cambridge, UK. Tel: +44 (1223) 271062
Maybe this world is another planet's Hell -Aldous Huxley || Opinions==mine
next prev parent reply other threads:[~2001-04-23 10:42 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-04-23 10:04 Victor Tarasov
2001-04-23 10:21 ` Gary Thomas
2001-04-23 10:42 ` Jonathan Larmour [this message]
[not found] <3AE5384E.779252B@idealx.com>
2001-04-24 5:54 ` Gary Thomas
2001-04-24 9:47 ` Jonathan Larmour
2001-04-26 7:30 ` Victor Tarasov
2001-04-26 17:28 ` Gary Thomas
2001-04-30 1:36 ` Victor Tarasov
2001-04-30 5:02 ` Gary Thomas
2001-04-30 8:39 ` Victor Tarasov
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=3AE46975.D208E43A@redhat.com \
--to=jlarmour@redhat.com \
--cc=ecos-discuss@sourceware.cygnus.com \
--cc=victor.tarasov@idealx.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).