This is the mail archive of the
ecos-discuss@sources.redhat.com
mailing list for the eCos project.
Re: Clock/interrupt latency
- From: Jonathan Larmour <jifl at eCosCentric dot com>
- To: Daniel Lidsten <Daniel dot Lidsten at combitechsystems dot com>
- Cc: Andrew Lunn <andrew dot lunn at ascom dot ch>,eCos Discussion <ecos-discuss at sources dot redhat dot com>
- Date: Tue, 02 Sep 2003 03:51:52 +0100
- Subject: Re: [ECOS] Clock/interrupt latency
- References: <004B1D7A5257174C9044A1B7BD0E60ED232DAE@ratatosk.combitechsystems.com>
Daniel Lidsten wrote:
I am running eCos from RAM using an ICE debugger through a BDM
interface.
It's possible that the ICE could be interfering with the operation. More
importantly if your console is via ethernet (e.g. if you loaded via
RedBoot/RAM) it's even more likely as there are net packets to deal with.
Is the printing really going out the serial port, or is there some special
way it goes out via some ICE channel?
Jifl
--
eCosCentric http://www.eCosCentric.com/ The eCos and RedBoot experts
--["No sense being pessimistic, it wouldn't work anyway"]-- Opinions==mine
--
Before posting, please read the FAQ: http://sources.redhat.com/fom/ecos
and search the list archive: http://sources.redhat.com/ml/ecos-discuss