* [ECOS] ROM/RAM calling interface
@ 2000-06-30 6:27 Jesper Skov
0 siblings, 0 replies; only message in thread
From: Jesper Skov @ 2000-06-30 6:27 UTC (permalink / raw)
To: ecos-discuss
Hi,
With the next CVS snapshot you'll find the beginning of a conversion
of the HALs to support a new ROM/RAM calling interface. There's a
partial description of this interface here:
http://sourceware.cygnus.com/ecos/docs-latest/porting/hal-calling-if.html
If you want to know more, you'll have to consult the sources. For
reference, see the PowerPC and SH HALs which have already been
converted (except for the FADS HAL which is only partially done).
Now you're probably all wondering what this is all about. The most
apparent improvements will be that the default eCos ROM monitor (aka
eCos GDB stubs) will be able to provide asynchronous breakpoints and
thread-debugging without any stub code in the RAM startup application.
A few targets have had this ability for a long time, but now all
targets are going to get it.
It'll still be a while before all supported eCos targets has this
support, but the old workaround of including stubs in the RAM startup
application will continue to work.
Jesper
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2000-06-30 6:27 UTC | newest]
Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2000-06-30 6:27 [ECOS] ROM/RAM calling interface Jesper Skov
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).