This is the mail archive of the
ecos-discuss@sources.redhat.com
mailing list for the eCos project.
RE: i386 flopy load problem.
- To: 'Rolf Manderscheid' <rvm at yottayotta dot com>, jlarmour at cygnus dot co dot uk
- Subject: RE: [ECOS] i386 flopy load problem.
- From: Fabrice Gautier <Fabrice_Gautier at sdesigns dot com>
- Date: Fri, 3 Nov 2000 10:54:12 -0800
- Cc: ecos-discuss at sourceware dot cygnus dot com
> -----Original Message-----
> From: Rolf Manderscheid [mailto:rvm@yottayotta.com]
> Subject: Re: [ECOS] i386 flopy load problem.
> I was under the impression that loading your program from floppy was
> not the normal mode of operation. Instead, you would make a floppy
> with the gdb stubs on it *once* and then use it to download your
> programs. Running this way, you would never run into the space
> limitation imposed by the distributed boot block. Maybe somebody can
> explain to me *exactly* how that is supposed to work.
Actually, you can also write your entire program on the floppy. This is not
what I do, but RedBoot is loaded this way and it is quite big once you have
included the network drivers. Plus I my _start is now at 0x2000 because i
had'nt enough space for the network buffers on the startup stack (which is
still located in front of start which is not very)
> This fix to the loader allows programs up to roughly 640K in size
> (text+data+bss). A simple way to get more space for text and data is
> to move the bss section into extended memory, you only have to change
> the ldi script (diffs below).
For Redboot, i've adopted to load RAM program above 1Meg.
Thanks
--
Fabrice Gautier
fabrice_gautier@sdesigns.com