public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Andrew Lunn <andrew@lunn.ch>
To: zheng wujun <wj_zheng10@hotmail.com>
Cc: ecos-discuss@sources.redhat.com
Subject: Re: [ECOS] why application can not run on ecos correctly?
Date: Tue, 25 Nov 2003 08:38:00 -0000	[thread overview]
Message-ID: <20031125083824.GE21161@lunn.ch> (raw)
In-Reply-To: <BAY13-F71jnj7LXaz5F0000124a@hotmail.com>

On Tue, Nov 25, 2003 at 02:06:40AM +0000, zheng wujun wrote:
> Hi,all:
> I'm a newbie to ecos,and I have already installed ecos on my PC running 
> Linux OS
> ,and built a redboot image for my board--samsung snds corectly.But there is 
> some
> 
> questions want to get your kindly response.
> 
> 1.
> When powered,redboot can executed correctly,but there no those commands 
> which pre
> 
> fix is 'f-',such  as 'fis','fconfig',why?

You have not included the flash package. Hence it does not offer you
any of the flash commands.

 
> 2.I also built a executeable application according to ecos mannul,and 
> downloaded
> 
> by tftp to address 0xX on board,but when type comamnd 'go 0xX',then the 
> board was
> 
> died.why?
> 
> the information displayed as below:
>   RedBoot> load -v -r -h 192.168.20.172 -m tftp -b 0x800040 /tftpboot/hello
>   -
>   Raw file loaded 0x00800040-0x0091fcae, assumed entry at 0x00800040
>   RedBoot> go 0x00800040

See previous email.

> 3.when I build redboot image or kernel with ecosconfig command,the steps
> below is correct:
> (1) %ecosconfig new snds redboot
> (2) %ecosconfig tree
> but!!!
> (3) make
> cannot passed.and information below was displayed on:
> 
>                 from /usr/local/arm-elf/stlport/stddef.h:23,
>                 from 
> /home/examples/kernel/install/include/../include/stddef.h:64,
>                 from /usr/local/arm-elf/stlport/stddef.h:23,
>                 from 
> /home/examples/kernel/install/include/../include/stddef.h:64,
>                 from /usr/local/arm-elf/stlport/stddef.h:23,
>                 from 
> /home/examples/kernel/install/include/../include/stddef.h:64,
>                 from /usr/local/arm-elf/stlport/stddef.h:23,
>                 from 
> /home/examples/kernel/install/include/../include/stddef.h:64,
>                 from /usr/local/arm-elf/stlport/stddef.h:23,
>                 from 
> /home/examples/kernel/install/include/../include/stddef.h:64,
>                 from /usr/local/arm-elf/stlport/stddef.h:23,
>                 from 
> /home/examples/kernel/install/include/../include/stddef.h:64,

What toolchain are you using? Did you follow the installation
instructions and are using an eCosCentric toolchain or have you built
your own?

             Andrew

-- 
Before posting, please read the FAQ: http://sources.redhat.com/fom/ecos
and search the list archive: http://sources.redhat.com/ml/ecos-discuss

  reply	other threads:[~2003-11-25  8:38 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-11-25  2:06 zheng wujun
2003-11-25  8:38 ` Andrew Lunn [this message]
2003-11-25 11:07   ` Nick Garnett

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=20031125083824.GE21161@lunn.ch \
    --to=andrew@lunn.ch \
    --cc=ecos-discuss@sources.redhat.com \
    --cc=wj_zheng10@hotmail.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).