This is the mail archive of the
ecos-discuss@sourceware.org
mailing list for the eCos project.
Re: Can excessive/intensive serial flow cause stack overflow?
- From: Andrew Lunn <andrew at lunn dot ch>
- To: Alexandre <thekyz at gmail dot com>
- Cc: eCos Mailing List <ecos-discuss at ecos dot sourceware dot org>
- Date: Thu, 3 Jul 2008 12:10:11 +0200
- Subject: Re: [ECOS] Can excessive/intensive serial flow cause stack overflow?
- References: <d5aafeec0807030257i26ba319dpe2169e35b6c0f5ff@mail.gmail.com>
On Thu, Jul 03, 2008 at 11:57:50AM +0200, Alexandre wrote:
> Hi all,
>
> Working on a new eCos application & I stumble upon a disturbing problem.
>
> I'm working with eCos CVS on an LPC2106 platform with 2 UARTs.
LPC2106 is an ARM right?
First off, i would enable asserts in the INFRA package. It adds some
CPU overheads, but that might actually help in your situation....
Next put a breakpoint in the abort handler. Once it fires, look at the
stack pointers, program counter etc for the supervisor mode and
interrupt mode registers. That should point you to what is causing the
abort. Also lr - 4 is the address which caused the prefetch abort. r14
is the lr.
Andrew
--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss