This is the mail archive of the
ecos-discuss@sources.redhat.com
mailing list for the eCos project.
RE: Redboot-GDB
- From: "Michael Anburaj" <embeddedeng at hotmail dot com>
- To: ecos-discuss at sources dot redhat dot com
- Cc: WPD at dtccom dot com, msalter at redhat dot com
- Date: Wed, 25 Jun 2003 23:24:14 +0000
- Subject: RE: [ECOS] Redboot-GDB
- Bcc:
Hi,
an ARM based platform. Ultimately, the bug was in my initialization of the
interrupt controller on my target. IIRC, I didn't mask all of the
interrupts that should have been masked.
As I said in my earlier email, in my initialization code all interrupts are
masked. And the RTC <ecos sys. Timer> interrupt gets unmasked by a call to
Cyg_RealTimeClock::Cyg_RealTimeClock() of
/kernel/current/src/common/clock.cxx ? which in turn calls -->
HAL_CLOCK_INITIALIZE().
http://sources.redhat.com/ml/ecos-discuss/2003-03/msg00212.html for Mark's
response to it.
From Mark?s response, it looks like the RTC interrupt should never get
unmasked in Redboot. Am I right?
If so,
1. should Cyg_RealTimeClock::Cyg_RealTimeClock() never get called in
Redboot? If yes, then how is it getting called in my Redboot <some malloc
init or libc function is calling this>
2. Or should HAL_CLOCK_INITIALIZE() never unmask the RTC interrupt?
Please, advice me in this regard.
Thanks a lot,
-Mike.
_________________________________________________________________
MSN 8 with e-mail virus protection service: 2 months FREE*
http://join.msn.com/?page=features/virus
--
Before posting, please read the FAQ: http://sources.redhat.com/fom/ecos
and search the list archive: http://sources.redhat.com/ml/ecos-discuss