Re: [ECOS] LPC2XXX: Spurious Interrupts Issue

["wang cui" <iucgnaw at msn dot com>]

> Thanks, I brief look at the patch. You fix the LPC2XX vector table.  
> ...
I raised discrssion about this issue serval months ago:
http://sources.redhat.com/ml/ecos-discuss/2006-08/msg00225.html
I think Gary's advice is a good solution, and I just havn't done it yet. So 
still leave this piece of ugly code here. :-)

As I need burn the image into off-chip flash, so the ARM_VECTOR_0x14 should 
be set correctly without rely on burner.
Of cource, your suggestion of do it with a script in "make" process is 
good, but how about Redboot(I don't think modify Redboot's make process is 
resonable)? And other newbies may be very hard to catch this 
problem(because they can't find any info from CVS except search maillist).

So I suggest to solve it in Gary's way. We add a CDL interface in ARM arch 
package to allow user configure ARM_VECTOR_0x14, then add a CDL 
implemention in LPC2XXX's variant package.

What is your opinion? Hope we can solve this issue.

> I did talk about unexpected interrupts that what occur on the 
> virtual
> debug channel.
> ...
As for the spurious interrupt:
Because RAM resource on my targets is limited, I rarely use GDB to debug 
application(use JTAG instead). So I can't provide more info for your 
reference.
But I do face spurious interrupt in my ROM application when use embedded 
UARTs, I suspect it is a bug of LPC2XXX.

I think what I done in my patch is reasonable.
In the current CVS's implemention, application hangs even if we set 
CYGIMP_HAL_COMMON_INTERRUPTS_IGNORE_SPURIOUS. I thinks it's not what we 
want, so I make this modification, and it works. I am not sure whether it 
is absolutly correct, but it is fine for me. :-)

_________________________________________________________________
免费下载 MSN Explorer:   http://explorer.msn.com/lccn/  


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