1 Aug 2004 10:40
1 Aug 2004 22:52
Re: memory saving scheme for stacks
Andrew Lunn <andrew <at> lunn.ch>
2004-08-01 20:52:49 GMT
2004-08-01 20:52:49 GMT
> If you have the ram, then obviously SST threads make no sense.
It seems to me that nearly everything you have been doing for the last
couple of months has been to do with shoehorning your code into a
system with too little RAM. eCos is meant to be small, but it also has
to be clean, maintainable and efficient.
It might be time to take a step back and take a look at your problem
from a wider angel. Consider how much time you have spent so far,
consider how much more time you would need to implement SST. Consider
the maintainance of such a system. Its always difficult to get a
stable system when you have extreamly tight memory since unexpected
things will happen in the field causing hard to reporduce bugs.
Talk to your hardware people and component supply people. It might
turn out cheaper in the long run to put bigger RAMs on the board and
save a huge amount of time and money on the software side of the
project.
Andrew
--
--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss
1 Aug 2004 23:40
Re: eCos FAT filesystem
Andrew Lunn <andrew <at> lunn.ch>
2004-08-01 21:40:57 GMT
2004-08-01 21:40:57 GMT
On Sat, Jul 31, 2004 at 12:52:19PM +0100, Iram wrote:
> Hi
>
> I am developing an SD interface driver for the LEON
> target. I have incorporated the FAT filesytem
> developed by Elactec to eCos and want to test the file
> system. I am looking for a program similar to
> "mk_romfs" that creates a FAT file system image that I
> can load into the target memory. Host machine has
> windows XP.
Your easiest solution might be to use a real floppy or vary small
partition and the use the cygwin dd to copy the filesystem into a file
and then upload it to the target.
Or you might consider using Linux. You can use mkfs.vfat to create the
filesystem in a file, then you the loop device to mount the filesystem
in a file and put files into the filesystem.
Andrew
--
--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss
2 Aug 2004 00:52
RE: binutils wizardry
Andrew Dyer <adyer <at> righthandtech.com>
2004-08-01 22:52:24 GMT
2004-08-01 22:52:24 GMT
> -----Original Message----- > From: ecos-discuss-owner <at> ecos.sourceware.org > [mailto:ecos-discuss-owner <at> ecos.sourceware.org]On Behalf Of Doyle, > Patrick > Sent: Friday, July 30, 2004 7:42 AM > To: ecos discuss list > Subject: [ECOS] binutils wizardry > > > I have an existing application that I load onto my device > with RedBoot. I > have a raw binary data file that I also load onto my device that my > application expects to find in memory at address 0x80000. I > would like to > figure out some method, preferably _after_ I've linked my > main application, > to glue these two pieces together into a single ELF file so > that I could > download both pieces in one swell foop. > > I'm reasonably sure I can do this with some subset of the programs in > binutils, but I'm not too sure where to start. I vaguely > remember looking > at how Linux gets gzip'ed for booting (10 or more years ago), so I'll > probably start there, but, in the mean time, I thought I > would ask for some > pointers. > > Any pointers?(Continue reading)
2 Aug 2004 07:35
Re: Suggestion needed for the support of ecos for my philips ARM board
Puneet <puneetgoel77 <at> yahoo.co.uk>
2004-08-02 05:35:13 GMT
2004-08-02 05:35:13 GMT
one small doubt. I am able to get one more ARM9 board with 256KB Flash and 128MB RAM. will that work? soppose i have an OS+Application with the image size of 1MB, where is that stored? In Flash? RAM comes in picture only when i need to run the OS? am i right? regards, Puneet ----- Original Message ----- From: "Robert Cragie" <rcc <at> jennic.com> To: "Puneet Goel" <puneetgoel77 <at> yahoo.co.uk> Sent: Friday, July 30, 2004 2:16 PM Subject: RE: [ECOS] Suggestion needed for the support of ecos for my philips ARM board > If it is not listed here, it won't be supported: > > http://ecos.sourceware.org/hardware.html > > However, I would say a good starting point would be the HAL for the the ARM > PID, ARM AEB or ARM Evaluator E7T, as these all use chips based on the(Continue reading)
2 Aug 2004 09:55
答复: [ECOS] Suggestion needed for the support of ecos for my philips ARM board
<Zhang.Sonys <at> INVENTEC-inc.com>
2004-08-02 07:55:56 GMT
2004-08-02 07:55:56 GMT
Why not try run RedBoot in Flash? You can load the eCos + Application with http/tftp or X-modem/Y-modem protocol into RAM. Brs Sonys -----原始邮件----- 发件人: Puneet [mailto:puneetgoel77 <at> yahoo.co.uk] 发送时间: 2004年8月2日 13:35 收件人: ecos-discuss <at> ecos.sourceware.org 主题: Re: [ECOS] Suggestion needed for the support of ecos for my philips ARM board one small doubt. I am able to get one more ARM9 board with 256KB Flash and 128MB RAM. will that work? soppose i have an OS+Application with the image size of 1MB, where is that stored? In Flash? RAM comes in picture only when i need to run the OS? am i right? regards, Puneet(Continue reading)
2 Aug 2004 10:05
Re: memory saving scheme for stacks
Øyvind Harboe <oyvind.harboe <at> zylin.com>
2004-08-02 08:05:42 GMT
2004-08-02 08:05:42 GMT
On Sun, 2004-08-01 at 22:52, Andrew Lunn wrote: > > If you have the ram, then obviously SST threads make no sense. > > It seems to me that nearly everything you have been doing for the last > couple of months has been to do with shoehorning your code into a > system with too little RAM. eCos is meant to be small, but it also has > to be clean, maintainable and efficient. > > It might be time to take a step back and take a look at your problem > from a wider angel. Consider how much time you have spent so far, > consider how much more time you would need to implement SST. Consider > the maintainance of such a system. Its always difficult to get a > stable system when you have extreamly tight memory since unexpected > things will happen in the field causing hard to reporduce bugs. Squeezing more out of the current system must of course be held up against the costs of a redesign. At some point, doing a redesign is cheaper. > Talk to your hardware people and component supply people. It might > turn out cheaper in the long run to put bigger RAMs on the board and > save a huge amount of time and money on the software side of the > project. If they add DRAM(megabytes), word is we'll be switching to uCLinux. Hence the energy barrier(from a high-level perspective) to be crossed is new board layout(which entails more than just the CPU) + switching OS. So far eCos has yielded to my efforts to squeeze a bit more out of the(Continue reading)
2 Aug 2004 11:48
Re: Help! Some runtime problems
Nick Garnett <nickg <at> ecoscentric.com>
2004-08-02 09:48:04 GMT
2004-08-02 09:48:04 GMT
Robert Allen <rba_ny <at> yahoo.com> writes: > Hi guys, > I have a multi-threaded application written in > C++. It compiled well. when I try to run it, this is > what I'm getting -- > > Program received signal SIGTRAP, Trace/breakpoint > trap. > [Switching to Thread 2] > 0x0000ede0 in _exit (n=24) > at > ../../../../../../newlib-1.12.0/newlib/libc/sys/arm/syscalls.c:104 > 104 > ../../../../../../newlib-1.12.0/newlib/libc/sys/arm/syscalls.c: > No such file or directory. > in > ../../../../../../newlib-1.12.0/newlib/libc/sys/arm/syscalls.c > Current language: auto; currently c > > I don't understand this error. can someone please help > me on this. This looks to me like you have built a stand-alone newlib application and not an eCos application. Go back and reread the User Guide. -- -- Nick Garnett eCos Kernel Architect http://www.ecoscentric.com/ The eCos and RedBoot experts(Continue reading)
2 Aug 2004 12:01
Re: about http client
Nick Garnett <nickg <at> ecoscentric.com>
2004-08-02 10:01:39 GMT
2004-08-02 10:01:39 GMT
"Dohun Kim" <hunkim <at> postech.ac.kr> writes: > Dear eCos users, > > Is there anyone who knows a http client library or codes on eCos > or tries to develop? > > I would appreciate if you could answer. > HTTP is a very simple protocol, most people who need to fetch data via HTTP just write it from scratch. There is an HTTP client in redboot, for downloading binaries, which you could use as a starting point. However, most of the code there is concerned with handling the interfaces to RedBoot and the TCP/IP stack, the HTTP protocol handling is the smallest part. -- Nick Garnett eCos Kernel Architect http://www.ecoscentric.com/ The eCos and RedBoot experts -- -- Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss
2 Aug 2004 12:07
Re: HAL startup help.
Nick Garnett <nickg <at> ecoscentric.com>
2004-08-02 10:07:04 GMT
2004-08-02 10:07:04 GMT
Rycerz Roman-G11565 <roman.rycerz <at> motorola.com> writes: > I am hoping someone can help me. I have a rather strange problem that comes and goes for reasons that so far escape me. > While I am not sure what makes this situation appear and disappear, maybe this behavior will ring some bells. > > > When the ecos world is happy, the routine "cyg_hal_invoke_constructors" executes, behaves nicely and executes a list of constructors. > such as > Global_I10100_diag_write_char > Global_I11000_cyg_scheduler_sched_lock > Global_I12000_ZB13cyg_Interrupt15.... > > > When ecos is unhappy "cyg_hal_invoke_constructors" actually executes a list of destructors > > Global_D14000...... > Global_D15000....... > > > Anyone know what might cause this ???? I am sure its something I am doing, but so far I have no clue.... Cannot help you specifically, but in the past when I have seen things like this happening, it has often been an alignment issue. It appears and disappears as changing sizes of text and data change the alignment of later data items. Check that the alignment requirements in your linker script are correct. If you try single stepping through(Continue reading)
RSS Feed