Date: Sun, 19 Dec 1999 10:03:34 +0200 (IST) From: Eli Zaretskii X-Sender: eliz AT is To: Steve Drake cc: djgpp AT delorie DOT com Subject: Re: djgpp appropriate for embedded system? In-Reply-To: <385ACA26.D9C9FC40@iclinks.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Reply-To: djgpp AT delorie DOT com X-Mailing-List: djgpp AT delorie DOT com X-Unsubscribes-To: listserv AT delorie DOT com Precedence: bulk On Fri, 17 Dec 1999, Steve Drake wrote: > The RAM space is limited. I had heard a rumor that the DPMI system > required by djgpp effectively makes it unuseable with less than > 2Megs of RAM. Any truth to this? I was able to write and execute a > "Hello world" app on a 512K target (the exe was 100k). I used > CWSDPMI.EXE. The fact that it worked would seem to refute the rumor, > but maybe I am missing something. CWSDPMI was tested to run non-trivial applications on a machine with 64KB of free conventional memory and ZERO extended memory. It worked, albeit with a lot of paging to disk. So 512K or 1M should not be a problem. > My target does not have any video/keyboard, so everything must be > done through serial ports (an ethernet option is also available on > some systems). The console is on COM1 which you access using > Hyperterminal or the like. I want to know if a decent remote > debugger exists that can interact with the target over a serial > port. GDB supports remote debugging, but it needs some work to get this operational for DJGPP. The code was done with a very old version of DJGPP, and support for hardware interrupts changed a lot since then. So if you need remote debugging, you will need to make it work again. I think somebody is already working on this aspect of GDB (check DJGPP archives at http://www.delorie.com/djgpp/mail-archives/), so perhaps you could join forces.