This is the mail archive of the
ecos-discuss@sources.redhat.com
mailing list for the eCos project.
Re: AT91 serial port usage
- To: ecos-discuss at sources dot redhat dot com
- Subject: Re: [ECOS] AT91 serial port usage
- From: harri dot siirtola at vtt dot fi
- Date: Tue, 14 Aug 2001 17:09:39 +0300
>> Does this work with the latest AT91 port: having both AT91 serial ports
>> interrupt driven and port 0 used as /dev/ttydiag at the same time? I try to
>> configure with these checked:
>
>Should do. If it doesn't you'll have to say what happens! Preferably after
>a bit of debugging.
After some digging: if I enable "Debug I/O sub-system", I get the following:
Init device '/dev/ser0'
AT91 SERIAL init - dev: FFFD0000.2
Set output buffer - buf: 2071A78 len: 128
Set input buffer - buf: 2071AF8 len:
128)+'٥'ٽ͕ŝ5)QŁMI%1с
'FFFCC000.3
Set output buffer - buf: 2071B78 len: 128
Set input buffer - buf: 2071BF8 len: 128
Init device '/dev/ttydiag'
Init tty channel: 206024C
Init device '/dev/haldiag'
HAL/diag SERIAL init
So there's garbage instead of "Init device /dev/ser1" etc. After this,
printf works though. Should there be a delay between inits?
Another problem is, I can't seem to get port 1 rx interrupts triggering (tx
works ok). With my own experimental port (derived from Carl's port just as
this one) it triggered, I just can't find any significant differences.
Chars appear in USART1_RHR and IMR bits 0 & 1 are set.
>
>Jifl
Thanks for your help,
Harri