This is the mail archive of the
ecos-discuss@sourceware.org
mailing list for the eCos project.
Re: ISR problem
- From: Bart Veer <bartv at ecoscentric dot com>
- To: ram_ecos at yahoo dot co dot in
- Cc: ecos-discuss at ecos dot sourceware dot org
- Date: Tue, 3 Jan 2006 15:46:37 +0000 (GMT)
- Subject: Re: [ECOS] ISR problem
- References: <20060103115716.33095.qmail@web8412.mail.in.yahoo.com>
>>>>> "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
--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss