This is the mail archive of the
ecos-discuss@sources.redhat.com
mailing list for the eCos project.
Re: redboot w/o ether-related codes.
- From: Jonathan Larmour <jifl at eCosCentric dot com>
- To: Tokutaro Nishioka <nishioka at activebrains dot co dot jp>
- Cc: ecos-discuss at sources dot redhat dot com
- Date: Wed, 30 Jul 2003 11:37:27 +0100
- Subject: Re: [ECOS] redboot w/o ether-related codes.
- References: <007901c355a1$002eab60$e600a8c0@nt2000svr.activebrains.co.jp>
Tokutaro Nishioka wrote:
> Hi all,
>
> I'm trying to run redboot (included in eCos v2.0)
> upon MIPS based board which provides RTL-8019AS
> (almost same as NS-DP83902a) ethernet controller.
>
> I wrote definitions in ecos.db, introduced codes from
> ~/packages/devs/eth/ns/dp83902a/*,
> and I edit CDL files for these (LANC & board).
> Then I run 'ecosconfig', and run 'make'.
> Compiling result is OK, also linking result is OK.
> I can make dis-assemble file from ./install/bin/redboot.elf.
>
> When I see the dis-assemble file, all the ether-related symbols
> and codes (such as 'eth_drv_init' etc...) are lacked !
Did you see in the build output if the package is even built? Did you add
the package to ecos.db and to your configuration?
> Off cource, these ether-related symbols are existing in
> './install/lib/libtarget.a' library file,
> but they are NOT linked within redboot.elf.
>
> I checked generated 'ecos.ecc' and confirmed that ether-related
> valiables within it are ENABLED.
If the package isn't being built, searching ecos.ecc for its associated
CDL should help: it will say if it's inactive or off and why.
Jifl
--
eCosCentric http://www.eCosCentric.com/ The eCos and RedBoot experts
--[ "You can complain because roses have thorns, or you ]--
--[ can rejoice because thorns have roses." -Lincoln ]-- Opinions==mine
--
Before posting, please read the FAQ: http://sources.redhat.com/fom/ecos
and search the list archive: http://sources.redhat.com/ml/ecos-discuss