This is the mail archive of the
ecos-discuss@sources.redhat.com
mailing list for the eCos project.
Re: Ctrl-c support in ISR
- From: Gary Thomas <gary at mlbassoc dot com>
- To: Robert Cragie <rcc at jennic dot com>
- Cc: "ECOS [2]" <ecos-discuss at ecos dot sourceware dot org>
- Date: Fri, 30 Jan 2004 08:39:29 -0700
- Subject: Re: [ECOS] Ctrl-c support in ISR
- Organization: MLB Associates
- References: <NMEDLDELHPEFHOMFIJBHKEABDBAA.rcc@jennic.com>
On Fri, 2004-01-30 at 08:35, Robert Cragie wrote:
> I am using a slightly modified version of the OpenCores CVS version of the
> port for the OpenRISC and I'm trying to get proper ctrl-c debugging support
> working. Currently, it will only intercept a ctrl-c and cause a breakpoint
> if characters are being sent to GDB over the serial port. Taking a cursory
> look at the code confirms that interrupts are not enabled for the UART (in
> cyg_hal_plf_serial_init_channel()), but there does seem to be an ISR
> installed via CYGACC_COMM_IF_DBG_ISR_SET(*comm, cyg_hal_plf_serial_isr). I'm
> wondering if anyone could help in describing the steps I need to take to get
> a ctrl-c intercepted in the ISR and cause a breakpoint as the virtual comms
> stuff does seem a bit arcane.
For the debug port, the interrupts are controlled by the cyg_hal_plf_serial_control()
function. That function performs various operations on the port, in particular
enabling and disabling interrupts.
Look at how it's done on other ports, e.g.
hal/powerpc/mpc8xxx/current/src/quicc2_diag.c
--
Gary Thomas <gary@mlbassoc.com>
MLB Associates
--
Before posting, please read the FAQ: http://sources.redhat.com/fom/ecos
and search the list archive: http://sources.redhat.com/ml/ecos-discuss