This is the mail archive of the ecos-discuss@sourceware.org mailing list for the eCos project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: ISR problem


Hello Bart Veer,

You were right. That was the Ethernet ISR(43). To
solve the problem, I found a very odd way, what I am
doing is that; I am disconnecting ETH cable after
load. Where as the KEYBOARD ISR(33) is not at all
effecting the hole process.

I am having one more doubt, if I am creating two ISR
as given below:

!!!!!!!!!!!!!!!
cyg_interrupt_create(vector1, 5, (cyg_addrword_t)
base,my_serial_ISR, my_serial_DSR, 
		&my_intr_hdlr[index], &my_intr_obj[index]);

cyg_interrupt_create(vector2, 5, (cyg_addrword_t)
base, my_serial_ISR, my_serial_DSR, 
		&my_intr_hdlr[index], &my_intr_obj[index]);

!!!!!!!!!!!!!!!!!!

as u can see I am creating two ISR with same api in
ISR & DSR function, but with two different vector
numbers with same priority, is it allowed or not?
Please give suggestions.

Thanks & regards,
Ram Kumar

--- Bart Veer <bartv@ecoscentric.com> wrote:

> >>>>> "Ram" == ram kumar <ram_ecos@yahoo.co.in>
> writes:
> 
>     Ram> Thanks Bart Veer.
>     Ram> My DSR is working well for COM2, but in
> case of COM1
>     Ram> its not working correctly. On
> initialization of COM1 I
>     Ram> am getting a message. 
> 
>     Ram> !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
>     Ram> hal_arch_default_isr: 33 (data:0)
>     Ram> hal_arch_default_isr: 43 (data:0)
>     Ram> !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
> 
>     Ram> And then every thing stops.But my ISR is
> using vector
>     Ram> 35. Please give suggestions. 
> 
> 33 is the keyboard. 43 is not pre-defined but may be
> getting used for
> ethernet on the PCI bus. There may be some
> interaction with RedBoot's
> channels, but I do not know exactly how those are
> implemented on a PC.
> Alternatively maybe your application is manipulating
> more hardware
> than it should be.
> 
> Also, do make sure that your configuration has
> CYGPKG_IO_SERIAL_I386_PC_SERIAL0 disabled or
> inactive. Having both a
> full-blown serial driver and your application trying
> to manipulate the
> UART and claim the interrupt vector is likely to
> cause confusion.
> 
> Bart
> 
> -- 
> Bart Veer                       eCos Configuration
> Architect
> http://www.ecoscentric.com/     The eCos and RedBoot
> experts
> 
> 


Send instant messages to your online friends http://in.messenger.yahoo.com 


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


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]