public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
* [ECOS] why application can not run on ecos correctly?
@ 2003-11-25  2:06 zheng wujun
  2003-11-25  8:38 ` Andrew Lunn
  0 siblings, 1 reply; 3+ messages in thread
From: zheng wujun @ 2003-11-25  2:06 UTC (permalink / raw)
  To: ecos-discuss

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?

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
   
$T0a0f:30038001;0d:fbefffff;#b3$T0a0f:30038001;0d:fbefffff;#b3$T0a0f:30038001;
0




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,
.....
.....
.....

If it is releative to file as such sentence "#include_next" in file 
"stddef.h" or
"stdarg.h" and so on?

why?

Would you please give me some hints?Thank you very much!

Best regards!

_________________________________________________________________
Help STOP SPAM with the new MSN 8 and get 2 months FREE*  
http://join.msn.com/?page=features/junkmail


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

^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, other threads:[~2003-11-25 11:07 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2003-11-25  2:06 [ECOS] why application can not run on ecos correctly? zheng wujun
2003-11-25  8:38 ` Andrew Lunn
2003-11-25 11:07   ` Nick Garnett

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).