This is the mail archive of the ecos-discuss@sources.redhat.com 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]

how does the ctrlc happen when the serial port interrupt(ARM). Thanks


Hi all:
   As far as I know ctrlc is normally support in the by first calling the
"hal_default_isr()" function, but when the "cyg_drv_interrupt_attach()" in
the serial device driver will overwrite the "hal_interrupt_handlers" in
vectors.S. so when install the interrupt handler by
"cyg_drv_interrupt_attach()" for the serial port "hal_default_isr()" will be
replaced by the ISR installed, how and where will be the place to examine
the "0x03" for ctrlc support? Thanks a lot.

Is the following calling path correct? Thanks
(ARM target)

IRQ happens -->
(1). if the interrupt in the hal_interrupt_handlers table entry not get
replaced by calling cyg_xxx_attach() then default as:
hal_default_isr() --> hal_ctrlc_isr( ) --> cyg_hal_plf_serial_isr( ) -->
cyg_hal_user_break( )  this will look for the ctrlc.

(2) if the hal_interrupt_handlers table entry has been replaced by
previously calling cyg_xxx_attach( ) then the calling path will be:
the ISR() of the interrupt when -->

so how is ctrlc supported in  (2)? Thanks a lot


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


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