This is the mail archive of the
ecos-discuss@sources.redhat.com
mailing list for the eCos project.
RE: RE: ctrl-c in GDB
- From: "Vikas K. Prasad" <vikas dot prasad at ittiam dot com>
- To: "Nick Garnett" <nickg at ecoscentric dot com>
- Cc: <ecos-discuss at sources dot redhat dot com>,"Vikas K. Prasad" <vikas dot prasad at ittiam dot com>
- Date: Thu, 30 Sep 2004 15:38:25 +0530
- Subject: RE: [ECOS] RE: ctrl-c in GDB
Nick,
We are using a custom board with Excalibur on it.
The serial Rx interrupt is enabled and is working
fine. It is tested by typing the cntl-c on the
HyperTerminal. Redboot prompt etc are absolutely
fine. Is the ^c on HyperTerminal and via the
arm-elf-gdb different?
Regards,
Vikas
-----Original Message-----
From: Nick Garnett [mailto:nickg@ecoscentric.com]
Sent: Thursday, September 30, 2004 3:35 PM
To: Vikas K. Prasad
Cc: ecos-discuss@sources.redhat.com
Subject: Re: [ECOS] RE: ctrl-c in GDB
"Vikas K. Prasad" <vikas.prasad@ittiam.com> writes:
> Nick/Andrew,
>
> Thank you. I built a small program (with eCos) (using the
> standard libs) and downloaded it using redboot (built with
> stubs). Redboot is built @ 0x4000000 and program is loaded
> at 0x8000. The program is simple (only led on off in a
> while loop). I am able to step and debug as shown below
> but ^C does not work. Any clues regarding the port that I
> have done.
Why have you done your own port? What was wrong with the existing
Excalibur platform port?
>
> Now that I have eliminated eCos, (only redboot and a small
> pgm working fine, if left to itself) I hope you can help
> me get closer to the ^c problem.
I don't know why Ctrl-C is not working here. Maybe the HAL serial
device drivers are not enabling receive interrupts correctly. You will
probably have to debug it.
--
Nick Garnett eCos Kernel 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