public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Fabrice Gautier <Fabrice_Gautier@sdesigns.com>
To: 'Rolf Manderscheid' <rvm@yottayotta.com>, jlarmour@cygnus.co.uk
Cc: ecos-discuss@sourceware.cygnus.com
Subject: RE: [ECOS] i386 flopy load problem.
Date: Fri, 03 Nov 2000 10:54:00 -0000	[thread overview]
Message-ID: <5AF611D83988D4118ACF00E0B1040054055803@mr-intranet.sdesigns.net> (raw)

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

             reply	other threads:[~2000-11-03 10:54 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-11-03 10:54 Fabrice Gautier [this message]
     [not found] <200011162118.NAA18216@cygnus.com>
2000-11-17  3:48 ` Bart Veer
  -- strict thread matches above, loose matches on Subject: below --
2000-11-16  9:13 Leandro Vieira
2000-11-16  9:29 ` Robert Swindells
2000-11-16 13:18 ` Robert Swindells
2000-11-02 22:01 Rolf Manderscheid
2000-11-02 22:13 ` Jonathan Larmour
2000-11-02 20:09 Fabrice Gautier
2000-11-01 21:10 Fabrice Gautier
2000-11-02  9:21 ` Jonathan Larmour

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=5AF611D83988D4118ACF00E0B1040054055803@mr-intranet.sdesigns.net \
    --to=fabrice_gautier@sdesigns.com \
    --cc=ecos-discuss@sourceware.cygnus.com \
    --cc=jlarmour@cygnus.co.uk \
    --cc=rvm@yottayotta.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).