public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: C B <csb_80@hotmail.com>
To: <ecos-discuss@ecos.sourceware.org>
Subject: RE: [ECOS] RE: networking support for my eCos application
Date: Fri, 09 Nov 2007 18:48:00 -0000	[thread overview]
Message-ID: <BAY105-W33A3C34CCB1D6B724097D7EA840@phx.gbl> (raw)
In-Reply-To: <BAY105-W41B3A2290F34C3DE7B56BEEA840@phx.gbl>


So of course once I was able to compile and link everything I attempted to run a simple HelloWorld program on my target hardware.

Using the older eCos config that I inherited I was able use arm-elf-egb to load the program and then execute it and view the output in RedBoot.  I tried following the same process only this time I compiled & linked against my new eCos config and I got no output.  I noticed that the older version was getting a different start address that than new and took a look at the target.ld files for each of the two and they were more different than I expected.  In particular I was surprised that the specification of the memory layout was

MEMORY
{
    ram : ORIGIN = 0x20000000, LENGTH = 0x00C00000
    rom : ORIGIN = 0x20C00000, LENGTH = 0x00400000
    sram : ORIGIN = 0x00000100, LENGTH = 0x00023F00
}

versus this for the older (working) version:

MEMORY
{
    ram : ORIGIN = 0x20000000, LENGTH = 0x02000000
    sram : ORIGIN = 0x00000000, LENGTH = 0x00024000
}


Can anyone provide a little clarification on how these files are generated and what I may have screwed up in my config.

Thank you.


> From: csb_80@hotmail.com
> To: jld@ecoscentric.com
> CC: ecos-discuss@ecos.sourceware.org
> Date: Fri, 9 Nov 2007 08:32:07 -0500
> Subject: [ECOS] RE: networking support for my eCos application
>
>
> Ugh. I had somehow specified arm-elf-ld rather than arm-elf-gcc as the linker. Using arm-elf-gcc fixed the problem. Thanks again for everyone's help.
>
> Chris
>
>
>
>> Date: Fri, 9 Nov 2007 09:21:54 +0000
>> From: jld@ecoscentric.com
>> To: csb_80@hotmail.com
>> CC: ecos-discuss@ecos.sourceware.org
>> Subject: Re: networking support for my eCos application
>>
>> Chris
>>
>> C B wrote:
>>
>>> But, when I try to compile and link my own code I still get these undefined references when I try to link with the eCos libs I've built:
>>>
>>>>>> undefined reference to 'init_all_network_interfaces'
>>>>>> undefined reference to 'eth0_up'
>>>>>> undefined reference to 'eth0_bootp_data'
>>>>>> undefined reference to 'inet_ntoa'
>>>
>>> The command that gives those errors:
>>> arm-elf-ld -L"C:\cygwin\opt\ecos\ecos-cvs\tmp\install\lib" -L"C:\cygwin\opt\ecos\ecos-cvs\tmp\net\common\current" -L"C:\cygwin\opt\ecos\gnutools\arm-elf\arm-elf\lib" -L"C:\cygwin\opt\ecos\gnutools\arm-elf\lib\gcc-lib\arm-elf\3.2.1" -Ttarget.ld -o"Simple.exe" ./simple.o
>>>
>>> The ping_test calls init_all_network_interfaces() so I'm not sure why it's not found.
>>
>> I suggest you look at the command line arguments which the eCos build
>> system used to successfully link the ping test. Try linking your own
>> code similarly at a command line prompt and, assuming the linker
>> succeeds, work backwards to see which switches make the difference.
>>
>> For a start, you should be using "-nostdlib" in your link command and
>> you should need to explicitly reference only the lib directory in your
>> eCos install tree.
>>
>> John Dallaway
>> eCosCentric Limited
>
> _________________________________________________________________
> Peek-a-boo FREE Tricks & Treats for You!
> http://www.reallivemoms.com?ocid=TXT_TAGHM&loc=us
>
> --
> Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
> and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss
>

_________________________________________________________________
Windows Live Hotmail and Microsoft Office Outlook – together at last.  Get it now.
http://office.microsoft.com/en-us/outlook/HA102225181033.aspx?pid=CL100626971033

--
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:[~2007-11-09 18:48 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-02 18:54 [ECOS] " C B
2007-11-02 19:08 ` Gary Thomas
2007-11-05 16:12   ` C B
2007-11-05 18:43     ` Andrew Lunn
     [not found]       ` <BAY105-W2585C1EB05E16C54EA73C5EA890@phx.gbl>
2007-11-06  8:34         ` Andrew Lunn
2007-11-08 20:01   ` C B
2007-11-08 21:05     ` Andrew Lunn
2007-11-09  9:22     ` [ECOS] " John Dallaway
2007-11-09 13:32       ` [ECOS] " C B
2007-11-09 18:48         ` C B [this message]
2007-11-09 18:55           ` Andrew Lunn
2007-11-12 11:52             ` C B
2007-11-12 12:27               ` Gary Thomas
2007-11-12 18:11                 ` C B
2007-11-14 13:30                   ` [ECOS] Adding xscale support to my eCos config C B
2007-11-14 14:05                     ` Andrew Lunn
2007-11-14 14:13                       ` Mark Salter
2007-11-14 15:23                       ` C B
2007-11-14 15:24                         ` Gary Thomas
2007-11-14 20:11                           ` C B
2007-11-14 20:42                             ` C B
2007-11-16 18:15                               ` [ECOS] Performance timing C B
2007-11-16 19:47                                 ` Gary Thomas
2007-11-16 19:55                                   ` C B
2007-11-17  7:07                                     ` Mike Arthur
2007-11-19  5:19                                       ` C B
2007-11-19 14:36                                         ` Gary Thomas
2007-11-22 13:39                                           ` [ECOS] eCos compatible with arm-elf-gcc version 4.1.1? C B
2007-11-22 14:28                                             ` Lars Poeschel
2007-11-22 16:42                                               ` C B
2007-11-27 14:38                                               ` C B
2007-11-28 13:24                                                 ` C B
     [not found]             ` <BAY105-W28BEA5A1C91693C8BE5C8FEA870@phx.gbl>
2007-11-12 12:07               ` [ECOS] RE: networking support for my eCos application Andrew Lunn
2007-11-12 18:05                 ` C B

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=BAY105-W33A3C34CCB1D6B724097D7EA840@phx.gbl \
    --to=csb_80@hotmail.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).