This is the mail archive of the
ecos-discuss@sourceware.org
mailing list for the eCos project.
Re: Custom vectors.S
- From: Gary Thomas <gary at mlbassoc dot com>
- To: Slide <slide dot o dot mix at gmail dot com>
- Cc: ecos-discuss <ecos-discuss at ecos dot sourceware dot org>
- Date: Tue, 19 Jun 2007 13:51:26 -0600
- Subject: Re: [ECOS] Custom vectors.S
- References: <a623f7d10706191214o273a7a6at7f267413d6597041@mail.gmail.com>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Slide wrote:
> We are hoping to use eCos internally for some embedded work within our
> company, but we have a very specific environment that does not lend
> itself to the generic nature of vectors.S (ARM based processor). Has
> anyone done anything with having their own complete set of bootcode
> that just calls cyg_start? What actually needs to be setup prior to
> calling cyg_start in terms of memory and such?
What do you need that the current framework can't provide?
Most of what's in vectors.S deals with the details of the eCos
interrupt and exception handling. There isn't a whole lot of
"setup" code [past what's already handled by hal_platform_setup.h]
- --
- ------------------------------------------------------------
Gary Thomas | Consulting for the
MLB Associates | Embedded world
- ------------------------------------------------------------
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (GNU/Linux)
Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org
iD8DBQFGeDO9maKbSsQGV8ARAsNxAKCcqRrhDpfRzUWm23y42v6Oc16Z5QCfdCWS
DBbJtfStH9VirZqBR0nXc60=
=8Eks
-----END PGP SIGNATURE-----
--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss