This is the mail archive of the
ecos-devel@sources.redhat.com
mailing list for the eCos project.
Re: Porting eCos to the BlackFin processor
- From: Jonathan Larmour <jifl at eCosCentric dot com>
- To: bvermeul at blackstar dot nl
- Cc: ecos-devel at sources dot redhat dot com
- Date: Wed, 10 Sep 2003 23:49:47 +0100
- Subject: Re: Porting eCos to the BlackFin processor
- References: <Pine.LNX.4.44.0309101116190.18178-100000@blackstar.nl>
bvermeul@blackstar.nl wrote:
Hi all,
I'm trying to port eCos to the Analog Devices BlackFin BF533 processor,
but am having some difficulties understanding the implementation needed
for vector.S.
I've read the Architecture HAL porting bit on the web, and do understand
the trampoline function that it has, but not how I am supposed to set the
vectors to the hardware itself.
The Blackfin processor has special purpose registers for the various
exception vectors, which would need to be filled by eCos during startup.
The way I read it, the reset vector needs to be set by the linker?
I'm not entirely sure of that, but don't see where else that would be
handled.
Any pointers to code or documentation would be very much appreciated. At
the moment I'm a little stumped.
Well, there are plenty of other HALs to look at! Which one were you using
as a basis?
The linker script sets an entry point, although that tends to be relevant
only for programs that are loaded to and start from RAM. For stuff that
runs from ROM/Flash i.e. that is the first thing that's loaded, then you
have to use the linker script to ensure the relevant startup code is
linked at the correct memory address. This is done by a combination of the
.ld file supplied by the architecture HAL (generally) and the mlt*.ldi/.h
files in the include/pkgconf subdirectories of platform HALs.
Jifl
--
eCosCentric http://www.eCosCentric.com/ The eCos and RedBoot experts
--["No sense being pessimistic, it wouldn't work anyway"]-- Opinions==mine