This is the mail archive of the
ecos-discuss@sources.redhat.com
mailing list for the eCos project.
Re: Port problem
- To: Cristiano Ligieri Pereira <cpereira at ics dot uci dot edu>
- Subject: Re: [ECOS] Port problem
- From: Jesper Skov <jskov at redhat dot com>
- Date: 17 Aug 2001 11:49:47 +0200
- Cc: ecos-discuss at sourceware dot cygnus dot com
- References: <Pine.SOL.4.20.0108162211410.1148-100000@washoe.ics.uci.edu>
>>>>> "Cristiano" == Cristiano Ligieri Pereira <cpereira@ics.uci.edu> writes:
Cristiano> After this I've been trying two things: load a Hello World
Cristiano> eCos application configured to execute on RAM (by means of
Cristiano> GDB/Cygmon) and load RedBoot configured to execute at RAM
Cristiano> as well. For both I load the application at the original
Cristiano> RAM address (since for cygmon this is still the RAM memory
Cristiano> address) and for both I'm executing the code in
Cristiano> PLATFORM_SETUP1, which remaps the memory.
Diddling the MMU when running from RAM is not going to work unless you
are really careful!
Cristiano> how should I do about the serial communication with the
Cristiano> host? Can I reuse the communication already established
Cristiano> with CygMon? Do I need to break it and restart a new
Cristiano> connection?
The problem is probably that the eCos application will try to use
virtual vectors for writing to the serial port: but these may not be
compatible with CygMon.
Running RedBoot from RAM should work though (as it will initialize the
virtual vectors and use its own serial driver).
Jesper