Re: [ECOS] problem about interrupt end

[Michael Pederson <michael dot pederson at freescale dot com>]

Jiang, I would be most appreciative if you could elaborate for me the
problem you were seeing with diag_printf.  I have also been seeing some
stack corruption that only appears when it is used.

jiang jet wrote:
> 
> hi, I have resolved that problem:)
> it's caused by diag_printf:)
> thanks again
> jet
> 
>> From: Nick Garnett <nickg@ecoscentric.com>
>> To: "jiang jet" <jetjiang@hotmail.com>
>> CC: ecos-discuss@ecos.sourceware.org
>> Subject: Re: [ECOS] problem about interrupt end
>> Date: 29 Nov 2006 11:24:34 +0000
>>
>> "jiang jet" <jetjiang@hotmail.com> writes:
>>
>> > I think i have excluded the reason of repeating interrupt causing this
>> > problem...
>> > I prolong the timer to a very big number..so I can see for the first
>> > timer interrput the breakdown occurs...
>> > since the board and cpu is designed by ourself, I doubt if the
>> > assembly code for processing the interrupt needed to be modified(I
>> > refer to the code process
>> > :__defualt_intterrupt_vsr-->hal_interrupt_handlers-->isr--here code
>> > crashed))???is it possible?
>>
>> In that case it looks like memory corruption from some other
>> source. Perhaps thread stack overflow. If the board is your own design
>> then check that RAM address decode is being handled correctly and not
>> wrapping unexpectedly.
>>
>> -- 
>> Nick Garnett                                     eCos Kernel Architect
>> http://www.ecoscentric.com                The eCos and RedBoot experts

-- 
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss