On Thu, Jul 3, 2008 at 5:24 PM, Andrew Lunn <[EMAIL PROTECTED]> wrote:
> Nope. Look at the code where the asserts are. Interrupts < 16 need to be
> unique.
>
> However, i don't quite get this:
>
> [EMAIL PROTECTED]:~/eCos/anoncvs-clean/packages/hal/arm/lpc2xxx$ grep -r
> CYGNUM_HAL_INTERRUPT_UART *
> var/current/src/hal_diag.c: CYGNUM_HAL_INTERRUPT_UART0,
> var/current/src/hal_diag.c: CYGNUM_HAL_INTERRUPT_UART1,
> var/current/include/hal_var_ints.h:#define CYGNUM_HAL_INTERRUPT_UART0 6
> var/current/include/hal_var_ints.h:#define CYGNUM_HAL_INTERRUPT_UART1 7
>
> So the default setup is they have different interrupt values.
>
> Does your target override the values from the variant package?
>
> Maybe there is something more subtle going on here.
Sorry I should have added a bit more.
As you can see here:
**********************************************************************************************
TRACE: intr.cxx [ 86] Cyg_Interrupt::Cyg_Interrupt()
((vector=6,
priority=4, data=4000077c, isr=000049ec, dsr=00004a3c))
// lots of stuff.....
TRACE: intr.cxx [ 86] Cyg_Interrupt::Cyg_Interrupt()
((vector=7,
priority=4, data=40000860, isr=000049ec, dsr=00004a3c))
TRACE: intr.cxx [ 452] void Cyg_Interrupt::attach()
{{enter
ASSERT FAIL: <1>lpc2xxx_misc.c[472]hal_interrupt_set_level() Priority
already used by another vector
ASSERT FAIL: lpc2xxx_misc.c [ 472] hal_interrupt_set_level()
Priority
already used by another vector
**********************************************************************************************
They do have different vectors, what troubles me is that they have the
same priority, & I can't find any place where I could change that.
--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss
