Subject: From: Date:

RE: [ECS] CCE3:RX OVERRUN Mark Sekelsky Tue, 24 Aug 1999 04:59:03 -0500

---

My machine is an AMD K6 200 so it is "slower."  Since my last reboot I have
not had this issue.  If history is nay indication it will start again in a
day or two (at which time I will take care of the .wav files)

Mark S

-----Original Message-----
From: Mark Gilmore [mailto:omnip@usit.net]
Sent: Monday, August 23, 1999 3:42 PM
To: ecs-list@netbloc.com
Subject: [ECS] CCE3:RX OVERRUN


Regarding the old "CCE3:RX OVERRUN" error:
When resetting the CPU-XA with ECS, I noticed that
I would get this error every time - BINGO - I COULD
FINALLY REPRODUCE IT!

What triggered it was queing BELL.WAV (click sound)
just prior to requesting a 264-byte packet from the CPU-XA.
This packet was being received during playback, and triggered
an overrun on the UART's 16-byte FIFO (Win did not service
the RX-byte interrupt in time). I know it was a UART overrun
because the RX-byte count is always 16.
What's strange is that I have the related COM port at IRQ3,
and the sound-card at IRQ7. So I would expect COM4 interrupts
to have priority. I must be missing something.

Additional clues:
1) The error does NOT occur on my faster 233MHZ PC
   (only on my 66MHZ). I am curious to know if all
   who are experiencing this problem are using "slower" PCs.
2) The error does NOT occur if I replace BELL.WAV with one
   that I recorded (frequency-related ???). This is a quick/
   dirty "fix". If you do this, also replace ERRBELL.WAV.

Any ideas as to causes and/or solutions ???
Tanx
--
Mark Gilmore
Omnipotence (ECS home automation software)
http://www.usit.com/omnip
omnip@usit.net
423-745-0026

---