This is the mail archive of the
ecos-discuss@sources.redhat.com
mailing list for the eCos project.
FW: Serial device driver problem.
- To: "'David Airlie'" <David dot Airlie at parthus dot com>
- Subject: [ECOS] FW: [ECOS] Serial device driver problem.
- From: "Dennis Ehlin (ECS)" <Dennis dot Ehlin at ecs dot ericsson dot se>
- Date: Wed, 30 May 2001 12:47:17 +0200
- Cc: ecos-discuss at sources dot redhat dot com
I have a printout in the DSR routine, which prints a sign for every call to the DSR
and it seems like I only get the sign when a char is sent to the UART.
So I think that that part is working ok.
If I didn't clear the interrupt i would get lots of signs...
>are you sure you are (or the 16x5x) is clearing the interrupt correctly on
>your target? if not you will exit the ISR, enter the DSR, exit the DSR
>enter the ISR... and never go back to the scheduler..
>
>> Hi,
>>
>> I'm trying write a serial device to my ppc target, i'm using the generic 16x5x uart code.
>> I have the serial interrupts working and so on...
>>
>> When i do a serial_read (located serial.c) everything seems to work ok, and i get to the
>> cyg_drv_cond_wait(&cbuf->wait) line and it stops there to wait for the cbuf->wait signal. ok.
>>
>> Then i generate a serial receive interrupt and the serial_rcv_char function is called,
>> which sends the cbuf->wait signal with the line cyg_drv_cond_signal(&cbuf->wait).
>>
>> But nothing happends?, the cyg_drv_cond_wait(&cbuf->wait) never continues, as if it never gets the
>> signal.
>>
>> I suppose there's alot of things that can go wrong, but I dont have a clue of what is happening there.
>> Does anyone know of something that could cause this ?
>>
>> (I use the serial_echo test to test this)
>>
//Dennis